Graphic summary
  • Show / hide key
  • Information


Scientific and technological production
  •  

1 to 33 of 33 results
  • Non-Functional Requirements as drivers of Software Architecture Design  Open access

     Ameller, David
    Defense's date: 2014-01-23
    Universitat Politècnica de Catalunya
    Theses

    Read the abstract Read the abstract Access to the full text Access to the full text Open in new window  Share Reference managers Reference managers Open in new window

    En las últimas décadas, la ingeniería de software se ha convertido en un área importante de investigación. Como investigadores, debemos identificar un problema, una necesidad o un hueco en algún tema de investigación, una vez identificado hacemos un esfuerzo para producir nuevas técnicas, métodos y herramientas que esperamos contribuyan a mejorar el problema detectado. En la esta tesis el problema identificado fue la necesidad de dar soporte a los requerimientos no funcionales en el diseño de la arquitectura de software donde estos requisitos actúan como los impulsores en la toma de decisiones arquitectonicas .Esta tesis se inició con la idea de usar una disciplina relativamente nueva en la ingeniería de software, el desarrollo dirigido por modelos, ya que era un buen lugar para proponer una solución para el problema detectado. Planteamos nuestra visión de cómo los requisitos no funcionales se pueden integrar en el desarrollo dirigido por modelos y cómo esta integración tendría un impacto en las actividades de diseño arquitectónico.Cuando empezamos a producir nuestras técnicas, métodos y herramientas para el desarrollo dirigido por modelos nos dimos cuenta de que había un hueco importante en relación con el conocimiento arquitectónico y que debía resolverse previamente al problema inicial. Gran parte del conocimiento de cómo los requisitos no funcionales afectan al diseño de la arquitectura de software está oculta. Esta situación provocó un giro en esta tesis: ¿que necesitábamos para entender arquitectos?, ¿cómo piensan y cómo se toman las decisiones arquitectónicas?, ¿cuál es el papel de los requisitos no funcionales en el proceso de toma de decisiones de arquitectura?, y ¿en qué medida son los requisitos no funcionales importantes en este proceso? Todas estas preguntas necesitaban una respuesta, una respuesta que sólo los arquitectos podían proporcionar. En consecuencia, decidimos conducir varios estudios empíricos para responder a estas preguntas.Al mismo tiempo, nos pusimos a trabajar en una forma de representar este conocimiento, una ontología de arquitectura de software que integra los requisitos no funcionales. Usando como base esta ontología, se diseñó un método para ayudar a los arquitectos en el proceso de toma de decisiones de arquitectura y una herramienta que actúa como una prueba de concepto de ambos, la ontología y el método.En resumen, esta tesis explora cómo los requisitos no funcionales están integrados en las prácticas de diseño de arquitectura de software y propone formas para mejorar su integración y facilitar el trabajo de los arquitectos proporcionando los medios para ayudarles en el proceso de toma de decisiones de arquitectura.

    In the last decades, software engineering has become an important area of research. As researchers, we try to identify a problem, a need, or a hole in some research topic, once identified we make an effort to produce new techniques, methods, and tools that hopefully will help to improve the detected issue. In the present thesis the identified issue was the need of supporting non-functional requirements in the software architecture design where these requirements are the drivers of the architectural decision-making. This thesis started with the idea that a relatively new software engineering discipline, model-driven development, was a good place to propose a solution for the detected issue. We envisioned how non-functional requirements can be integrated in model-driven development and how this integration will impact in the architectural design activities. When we started to produce our techniques, methods, and tools for model-driven development we found out that there was a bigger hole in the web of knowledge than what we had initially foreseen. Much of the evidence of how non-functional requirements affect the software architecture design is hidden. This situation caused a turn in this thesis: we needed to understand architects, how they think and how they make the architectural decisions, what is the role of non-functional requirements in the architectural decision-making process, and to what extent are the non-functional requirements important in this process. All these questions needed an answer, an answer that only architects could provide. In consequence we opted to drove several empirical studies to answer these questions. In parallel, we started to work in a way of representing this knowledge, an ontology for software architecture that integrates non-functional requirements. Using this ontology as basis, we designed a method to assist architects in the architectural decision-making process and a tool that acted as a proof of concept of both, the ontology and the method. In summary, this thesis explores how non-functional requirements are currently integrated in the software architecture design practices, and proposes ways to improve this integration and facilitate the work of architects by providing means to assist them in the architectural decision-making process.

  • Access to the full text
    Protocol for a SLR on software ecosystems: technical report  Open access

     Franco Bedoya, Oscar Hernan; Ameller, David; Costal Costa, Maria Dolors; Franch Gutierrez, Javier
    Date: 2014-05-19
    Report

    Read the abstract Read the abstract Access to the full text Access to the full text Open in new window  Share Reference managers Reference managers Open in new window

    Open Source Software (OSS) and Ecosystems (SECO) are two emergent research areas in software engineering. We are interested on the published works that join these two topics, to do it we used a well-known technique called Systematic Literature Review (SLR).

    Open Source Software (OSS) and Ecosystems (SECO) are two emergent research areas in software engineering. We are interested on the published works that join these two topics, to do it we used a well-known technique called Systematic Literature Review (SLR).

  • Non-functional requirements in architectural decision-making

     Ameller, David; Ayala Martinez, Claudia Patricia; Cabot, Jordi; Franch Gutierrez, Javier
    IEEE software
    Date of publication: 2013-04-01
    Journal article

    Read the abstract Read the abstract View View Open in new window  Share Reference managers Reference managers Open in new window

    A survey of software architects addressed how they face non-functional requirements from an engineering perspective and how these requirements influence decision making

    A survey of software architects addressed how they face non-functional requirements from an engineering perspective and how these requirements influence decision making.

  • The three-layer architectural pattern applied to plug-in-based architectures : the Eclipse case

     Ameller, David; Collell, Oriol; Franch Gutierrez, Javier
    Software. Practice and experience
    Date of publication: 2013-04-01
    Journal article

    Read the abstract Read the abstract View View Open in new window  Share Reference managers Reference managers Open in new window

    The process of designing a software architecture using different kinds of components is often challenging. Different designs support some quality attributes while damaging others; therefore, trade-off analysis is needed to make informed decisions. Moreover, analysis made in theory needs to be complemented with observations in practice, especially when using a particular set of technologies to implement the system. In this paper, we present a particular instance of this problem. We study how the Three-Layer architectural pattern may be developed using plug-ins. We compare two extreme alternatives according to several representative scenarios and their impact in some quality attributes. Then, we apply this theoretical knowledge to a case study, the implementation of a plug-in-based tool for managing architectural knowledge using Eclipse. We report some unexpected difficulties found that forced us to adapt the theoretical solution into an operative architecture.

    The process of designing a software architecture using different kinds of components is often challenging. Different designs support some quality attributes while damaging others; therefore, trade-off analysis is needed to make informed decisions. Moreover, analysis made in theory needs to be complemented with observations in practice, especially when using a particular set of technologies to implement the system. In this paper, we present a particular instance of this problem. We study how the Three-Layer architectural pattern may be developed using plug-ins. We compare two extreme alternatives according to several representative scenarios and their impact in some quality attributes. Then, we apply this theoretical knowledge to a case study, the implementation of a plug-in-based tool for managing architectural knowledge using Eclipse. We report some unexpected difficulties found that forced us to adapt the theoretical solution into an operative architecture.

  • Access to the full text
    The role of quality attributes in service-based systems architecting : a survey  Open access

     Ameller, David; Galster, Matthias; Avgeriou, Paris; Franch Gutierrez, Javier
    European Congress on Software Architecture
    Presentation's date: 2013-07-10
    Presentation of work at congresses

    Read the abstract Read the abstract Access to the full text Access to the full text Open in new window  Share Reference managers Reference managers Open in new window

    Quality attributes (QA) play a fundamental role when architecting software systems. However, in contrast to QA in traditional software systems, the role of QA when architecting service-based systems (SBS) has not yet been studied in depth. Thus, we conducted a descriptive survey to explore how QA are treated during the architecting of SBS. Data were collected using an online questionnaire targeted at participants with architecting experience. Our survey shows that QA and functional requirements of SBS are mostly considered equally important. Also, QA are usually treated explicitly rather than implicitly. Furthermore, dependability and performance appear to be the most important QA in the context of SBS. Our results partially show that general findings on QA also apply to the domain of SBS. On the other hand, we did not find a confirmation that QA are primary drivers for the architecting of SBS, or that certain application domains would focus on particular QA.

    Quality attributes (QA) play a fundamental role when architecting software systems. However, in contrast to QA in traditional software systems, the role of QA when architecting service-based systems (SBS) has not yet been studied in depth. Thus, we conducted a descriptive survey to explore how QA are treated during the architecting of SBS. Data were collected using an online questionnaire targeted at participants with architecting experience. Our survey shows that QA and functional requirements of SBS are mostly considered equally important. Also, QA are usually treated explicitly rather than implicitly. Furthermore, dependability and performance appear to be the most important QA in the context of SBS. Our results partially show that general findings on QA also apply to the domain of SBS. On the other hand, we did not find a confirmation that QA are primary drivers for the architecting of SBS, or that certain application domains would focus on particular QA.

  • A framework for software reference architecture analysis and review

     Martinez Fernandez, Silverio Juan; Ayala Martinez, Claudia Patricia; Franch Gutierrez, Javier; Martins Marques, Helena; Ameller, David
    Experimental Software Engineering Latin American Workshop
    Presentation's date: 2013-04-11
    Presentation of work at congresses

    Read the abstract Read the abstract View View Open in new window  Share Reference managers Reference managers Open in new window

    Tight time-to-market needs pushes software companies and IT consulting firms to continuously look for techniques to improve their IT services in general, and the design of software architectures in particular. The use of soft-ware reference architectures allows IT consulting firms reusing architectural knowledge and components in a systematic way. In return, IT consulting firms face the need to analyze the return on investment in software reference architectures for organizations, and to review these reference architectures in order to ensure their quality and incremental improvement. Little support exists to help IT consulting firms to face these challenges. In this paper we present an empirical framework aimed to support the analysis and review of software reference architectures and their use in IT projects by harvesting relevant evidence from the wide spectrum of involved stakeholders.

  • Quark: a method to assist software architects in architectural decision-making

     Ameller, David; Franch Gutierrez, Javier
    Ibero-American Conference on Software Engineering
    Presentation's date: 2013-04-11
    Presentation of work at congresses

    Read the abstract Read the abstract View View Open in new window  Share Reference managers Reference managers Open in new window

    Quality attributes (QAs) and constraints are among the principal drivers of architectural decision-making. QAs are improved or damaged by architectural decisions (ADs), while constraints directly include or exclude parts of the architecture (e.g., logical components or technologies). We may determine the impact of a AD, or which parts of the architecture are aected by a constraint, but at the end it is hard to know if we are respecting the quality requirements (requirements over the QAs) and the imposed constraints with all the ADs made. In the usual approach, architects use their own experience to produce software architectures that comply with the expected quality requirements and imposed constraints, but at the end, especially for crucial decisions, the architect has to deal with complex trade-os between QAs and juggle with possible incompatibilities raised by the imposed constraints.

    Quality attributes (QAs) and constraints are among the principal drivers of architectural decision-making. QAs are improved or dam- aged by architectural decisions (ADs), while constraints directly include or exclude parts of the architecture (e.g., logical components or technologies). We may determine the impact of a AD, or which parts of the architecture are a ected by a constraint, but at the end it is hard to know if we are respecting the quality requirements (requirements over the QAs) and the imposed constraints with all the ADs made. In the usual approach, architects use their own experience to produce software architectures that comply with the expected quality requirements and imposed constraints, but at the end, especially for crucial decisions, the architect has to deal with complex trade-o s between QAs and juggle with possible incompatibilities raised by the imposed constraints. In this paper we present Quark, a method to assist software architects in architectural decision-making, and the conceptualization of the relationship between QRs and ADs de ned in Arteon, an ontology to represent and manage architectural knowledge. Finally, we also give an insight into the Quark and Arteon implementation, the ArchiTech tool.

  • Access to the full text
    Managing risk in open source software adoption  Open access

     Franch Gutierrez, Javier; Susi, Angelo; Annosi, Maria Carmela; Ayala Martinez, Claudia Patricia; Glott, Ruediger; Gross, Daniel; Kenett, Ron; Mancinelli, Fabio; Ramsany, Pop; Thomas, Cedric; Ameller, David; Bannier, Stijn; Bergida, Nili; Blumenfeld, Yehuda; Bouzereau, Olivier; Costal Costa, Maria Dolors; Dominguez, Manuel; Haaland, Kirsten; Lopez Cuesta, Lidia; Mourandini, Mirko; Sienna, Alberto
    International Joint Conference on Software Technologies
    Presentation's date: 2013-07-30
    Presentation of work at congresses

    Read the abstract Read the abstract Access to the full text Access to the full text Open in new window  Share Reference managers Reference managers Open in new window

    By 2016 an estimated 95% of all commercial software packages will include Open Source Software (OSS). This extended adoption is yet not avoiding failure rates in OSS projects to be as high as 50%. Inadequate risk management has been identified among the top mistakes to avoid when implementing OSS-based solutions. Understanding, managing and mitigating OSS adoption risks is therefore crucial to avoid potentially significant adverse impact on the business. In this position paper we portray a short report of work in progress on risk management in OSS adoption processes. We present a risk-aware technical decision-making management platform integrated in a business-oriented decision-making framework, which together support placing technical OSS adoption decisions into organizational, business strategy as well as the broader OSS community context. The platform will be validated against a collection of use cases coming from different types of organizations: big companies, SMEs, public administration, consolidated OSS communities and emergent small OSS products.

    By 2016 an estimated 95% of all commercial software packages will include Open Source Software (OSS). This extended adoption is yet not avoiding failure rates in OSS projects to be as high as 50%. Inadequate risk management has been identified among the top mistakes to avoid when implementing OSS-based solutions. Understanding, managing and mitigating OSS adoption risks is therefore crucial to avoid potentially significant adverse impact on the business. In this position paper we portray a short report of work in progress on risk management in OSS adoption processes. We present a risk-aware technical decision-making management platform integrated in a business-oriented decision-making framework, which together support placing technical OSS adoption decisions into organizational, business strategy as well as the broader OSS community context. The platform will be validated against a collection of use cases coming from different types of organizations: big companies, SMEs, public administration, consolidated OSS communities and emergent small OSS products.

  • Best Paper Award ESELAW'13

     Martinez Fernandez, Silverio Juan; Ameller, David; Franch Gutierrez, Javier
    Award or recognition

     Share

  • Best Paper Award CIbSE'13

     Ameller, David; Franch Gutierrez, Javier
    Award or recognition

    View View Open in new window  Share

  • Access to the full text
    Bridging the gap among academics and practitioners in non-functional requirements management: some reflections and proposals for the future  Open access

     Franch Gutierrez, Javier; Ameller, David; Ayala Martinez, Claudia Patricia; Cabot, Jordi
    Date of publication: 2012
    Book chapter

    Read the abstract Read the abstract Access to the full text Access to the full text Open in new window  Share Reference managers Reference managers Open in new window

    The software engineering community has paid a lot of attention to the study of non-functional requirements (NFRs). Along time, framing NFRs into an articulated framework has become an elusive target. As a consequence, prac-titioners usually integrate NFRs in the different system life-cycle activities in an ad-hoc manner. In this work, we summarise the results of a recent empirical study involving 13 software architects from the Spanish. These results serve as the basis for discussion about possible ways to bridge the gap between academics and practitioners in the management of NFRs

    The software engineering community has paid a lot of attention to the study of non-functional requirements (NFRs). Along time, framing NFRs into an articulated framework has become an elusive target. As a consequence, prac-titioners usually integrate NFRs in the different system life-cycle activities in an ad-hoc manner. In this work, we summarise the results of a recent empirical study involving 13 software architects from the Spanish. These results serve as the basis for discussion about possible ways to bridge the gap between academics and practitioners in the management of NFRs.

    Postprint (author’s final draft)

  • Managing Risk and Costs in Open Source Software Adoption

     Ayala Martinez, Claudia Patricia; Costal Costa, Maria Dolors; Lopez Cuesta, Lidia; Ameller, David; Oriol Hilari, Marc; Franco, Oscar Hernán; Alier Forment, Marc; Casañ Guerrero, Maria Jose; Galanis ., Nikolaos; Mayol Sarroca, Enric; Franch Gutierrez, Javier
    Participation in a competitive project

     Share

  • Access to the full text
    Linking quality attributes and constraints with architectural decisions  Open access

     Ameller, David; Franch Gutierrez, Javier
    Date: 2012-06-22
    Report

    Read the abstract Read the abstract Access to the full text Access to the full text Open in new window  Share Reference managers Reference managers Open in new window

    Quality attributes and constraints are among the principal drivers in architectural decision making processes. Quality attributes are improved or damaged by architectural decisions, while constraints directly include or exclude parts of the architecture (e.g., logical components or technologies). We may determine the impact of an architectural decision in the software quality, or which parts of the architecture are a ected by a constraint, but the hard problem is to know if we are respecting the quality requirements (requirements over the quality attributes) and the imposed constraints with all the architectural decisions made. Currently, the most usual approach is that architects use their own experience to produce software architectures that comply with the expected quality requirements and imposed constraints, but at the end, especially for crucial decisions, the architect has to deal with complex tradeo s between quality attributes and juggle with possible incompatibilities raised by the imposed constraints. To facilitate this task and make architect's decision making processes more reliable and e ective, in this paper we present the Quark method to guide the architects in the software architecture design. Quark relies on a specialized ontology, Arteon, which is in charge of managing the architectural knowledge. The decisional part of Arteon is also presented in this paper.

  • Access to the full text
    Non-functional requirements in software architecture practice  Open access

     Ameller, David; Ayala Martinez, Claudia Patricia; Cabot, Jordi; Franch Gutierrez, Javier
    Date: 2012-03-16
    Report

    Read the abstract Read the abstract Access to the full text Access to the full text Open in new window  Share Reference managers Reference managers Open in new window

    Dealing with non-functional requirements (NFRs) has posed a challenge onto software engineers for many years. Over the years, many methods and techniques have been proposed to improve their elicitation, documentation, and validation. Knowing more about the state of the practice on these topics may benefit both practitioners’ and researchers’ daily work. A few empirical studies have been conducted in the past, but none under the perspective of software architects, in spite of the great influence that NFRs have on daily architects’ practices. This paper presents some of the findings of an empirical study based on 13 interviews with software architects. It addresses questions such as: who decides the NFRs, what types of NFRs matter to architects, how are NFRs documented, and how are NFRs validated. The results are contextualized with existing previous work.

  • Access to the full text
    Conducting empirical studies on reference architectures in IT consulting firms  Open access

     Martinez Fernandez, Silverio Juan; Ameller, David; Ayala Martinez, Claudia Patricia; Franch Gutierrez, Javier; Terradellas Fernandez, Xavier
    Date: 2012-04-17
    Report

    Read the abstract Read the abstract Access to the full text Access to the full text Open in new window  Share Reference managers Reference managers Open in new window

    Tight time-to-market needs pushes IT consulting firms (ITCFs) to continuously look for techniques to improve their IT services in general, and the design of software architectures in particular. The use of reference architectures allows ITCFs reusing architectural knowledge and components in a systematic way. In return, ITCFs face the need to assess these reference architectures in order to ensure their quality, return on investment and incremental improvement. Little support exists to help ITCFs to face this challenge. In this work-in-progress paper we present an empirical framework aimed to assess ITCFs’ reference architectures and their use in IT projects by harvesting relevant evidence from the wide spectrum of involved stakeholders. We are currently applying this framework in an ITCF and we report the issues found so far.

  • How do software architects consider non-functional requirements: an exploratory study

     Ameller, David; Ayala Martinez, Claudia Patricia; Cabot, Jordi; Franch Gutierrez, Javier
    IEEE International Requirements Engineering Conference
    Presentation's date: 2012-10-27
    Presentation of work at congresses

    Read the abstract Read the abstract View View Open in new window  Share Reference managers Reference managers Open in new window

    Dealing with non-functional requirements (NFRs) has posed a challenge onto software engineers for many years. Over the years, many methods and techniques have been proposed to improve their elicitation, documentation, and validation. Knowing more about the state of the practice on these topics may benefit both practitioners' and researchers' daily work. A few empirical studies have been conducted in the past, but none under the perspective of software architects, in spite of the great influence that NFRs have on daily architects' practices. This paper presents some of the findings of an empirical study based on 13 interviews with software architects. It addresses questions such as: who decides the NFRs, what types of NFRs matter to architects, how are NFRs documented, and how are NFRs validated. The results are contextualized with existing previous work.

  • Access to the full text
    ArchiTech: tool support for NFR-guided architectural decision-making  Open access

     Ameller, David; Collell, Oriol; Franch Gutierrez, Javier
    IEEE International Requirements Engineering Conference
    Presentation's date: 2012-10-27
    Presentation of work at congresses

    Read the abstract Read the abstract Access to the full text Access to the full text Open in new window  Share Reference managers Reference managers Open in new window

    Researchers from requirements engineering and software architecture had emphasized the importance of NonFunctional Requirements and their influence in the architectural design process. To improve this process we have designed a tool, ArchiTech, which aims to support architects during the design process by suggesting alternative architectural decisions that can improve some types of non-functional requirements in a particular project, and facilitate the reuse of architectural knowledge shared between projects of the same architectural domain (e.g., web-based applications).

    Postprint (author’s final draft)

  • Architecture Quality Revisited

     Buschmann, Frank; Ameller, David; Ayala Martinez, Claudia Patricia; Cabot, Jordi; Franch Gutierrez, Javier
    IEEE software
    Date of publication: 2012-08
    Journal article

    View View Open in new window  Share Reference managers Reference managers Open in new window

  • Producción de software orientado a servicios basada en requisitos: la parte no funcional

     Carvallo Vega, Juan Pablo; Quer, Carme; Marco Gomez, Jordi; Costal Costa, Maria Dolors; Botella Lopez, Pere; Ayala Martinez, Claudia Patricia; Burgues Illa, Xavier; Ameller, David; Lopez Cuesta, Lidia; Cares, Carlos; Oriol Hilari, Marc; Palomares Bonache, Cristina; Ribó Balust, Josep M.; colomer collell, daniel; Collell, Oriol; Martinez Fernandez, Silverio Juan; Franch Gutierrez, Javier
    Participation in a competitive project

     Share

  • Access to the full text
    Ontology-based architectural knowledge representation: structural elements module  Open access

     Ameller, David; Franch Gutierrez, Javier
    International Conference on Advanced Information Systems Engineering
    Presentation of work at congresses

    Read the abstract Read the abstract Access to the full text Access to the full text Open in new window  Share Reference managers Reference managers Open in new window

    In the last years, Architectural Knowledge (AK) has emerged as a discipline for making explicit architects' knowledge and architectural decision-making processes. As a consolidated formalism for the representation of conceptual knowledge, ontologies have already been proposed for AK representation. Aligning with this trend, we are currently developing an ontology for AK representation named Arteon. The ontology is articulated in four modules and in this paper we focus on one of them, the structural module, that de nes the elements necessary to build a software architecture. Therefore, we clarify the concepts of architectural view, framework and element, show their relationships, its accurate definition is required to drive architectural design in a prescribed way.

  • Ingeniería de requisitos orientada a servicios: características, retos y un marco metodológico

     Ruiz, Marcela; Ameller, David; España, Sergio; Botella Lopez, Pere; Franch Gutierrez, Javier; Pastor, Oscar
    Jornadas de Ciencia e Ingeniería de Servicios
    Presentation's date: 2011-09
    Presentation of work at congresses

    Read the abstract Read the abstract View View Open in new window  Share Reference managers Reference managers Open in new window

    La ciencia de los servicios es, más que una nueva disciplina, un enfoque interdisciplinar para el estudio, diseño, e implementación de sistemas orientado a servicios, que actúa como paraguas que cubre todos los aspectos de computación utilizados (es decir, especificación y diseño orientado a servicios, arquitecturas orientada a servicios, servicios web, etc.), siendo actualmente una de las áreas de investigación más activas en el ámbito de la informática. La provisión de servicios y la innovación de los mismos están basadas sobre todo en las tecnologías de información. Este artículo presenta un análisis de las características esenciales e inherentes a la orientación a servicios. En base a este análisis, se identifican carencias en los métodos y herramientas de ingeniería de requisitos actuales que dificultan su aplicación al paradigma orientado a servicios. Estas carencias contribuyen a trazar un plan de trabajo con los retos que la Ingeniería de Requisitos Orientada a Servicios (IROS) deberá enfrentar los próximos años. Por último, se ofrece un marco de IROS con el potencial para dar solución a los retos encontrados. Este marco enfatiza, además, la importancia de la reutilización de métodos y conocimiento existentes mediante una estrategia de macromodelado, así como la aplicabilidad de las aproximaciones de desarrollo dirigido por modelos.

  • Reconciling the 3-layer architectural style with the Eclipse plug-in-based architecture

     Ameller, David; Collell, Oriol; Franch Gutierrez, Javier
    International Conference on Software Engineering
    Presentation's date: 2011-05-28
    Presentation of work at congresses

    Read the abstract Read the abstract View View Open in new window  Share Reference managers Reference managers Open in new window

    Software architecture construction is the result of a complex decision-making process, in which competing alternatives need to be compared. For example, deciding between a web-based application or a plug-in-based application has a signi cant impact on the architecture, therefore in order to make the right choice all possible tradeo s between them must be considered. Decisions need to be made in all architectural views, from the logical view in which architectural styles are chosen, to the development view in which types of modules are decided, to the deployment view where physical allocation is determined. In this paper we analyze the interactions between a 3-layer architecture at the logical view, and a plug-in-based development view implemented in Eclipse, focusing on the diffculties we overcome in a research project in order to make it work.

  • Access to the full text
    Dealing with non-functional requirements in model-driven development  Open access

     Ameller, David; Franch Gutierrez, Javier; Cabot, Jordi
    Date: 2010-04-22
    Report

    Read the abstract Read the abstract Access to the full text Access to the full text Open in new window  Share Reference managers Reference managers Open in new window

    The impact of non-functional requirements (NFRs) over software systems has been widely documented. Consequently, cost-effective software production method shall provide means to integrate this type of requirements into the development process. In this vision paper we analyze this assumption over a particular type of software production paradigm: model-driven development (MDD). We report first the current state of MDD approaches with respect to NFRs and remark that, in general, NFRs are not addressed in MDD methods and processes, and we discuss the effects of this situation. Next, we outline a general framework that integrates NFRs into the core of the MDD process and provide a detailed comparison among all the MDD approaches considered. Last, we identify some research issues related to this framework.

  • How do software architects consider non-functional requirements: a survey

     Ameller, David; Franch Gutierrez, Javier
    International Working Conference on Requirements Engineering: Foundation for Software Quality
    Presentation's date: 2010-07-01
    Presentation of work at congresses

    Read the abstract Read the abstract View View Open in new window  Share Reference managers Reference managers Open in new window

    Abstract. [Context and motivation] Non-functional requirements (NFRs) play a fundamental role when software architects need to make informed decisions. Criteria like efficiency or integrity determine up to a great extent the final form that the logical, development and deployment architectural views take. [Question/problem] Continuous evidence is needed about the current industrial practices of software architects concerning NFRs: how do they consider them, and what are the most influential types in their daily work. [Principal ideas/results] We ran a web survey addressed to software architects about these issues. We got 60 responses that give some light to the questions above. [Contribution] Some empirical data has been gathered from industry. The results of this survey may serve as input for researchers in order to decide in which types of NFRs may be necessary to invest more research effort.

  • Access to the full text
    Dealing with non-functional requirements in model-driven development  Open access

     Ameller, David; Franch Gutierrez, Javier; Cabot, Jordi
    IEEE International Requirements Engineering Conference
    Presentation's date: 2010-09-23
    Presentation of work at congresses

    Read the abstract Read the abstract Access to the full text Access to the full text Open in new window  Share Reference managers Reference managers Open in new window

    The impact of non-functional requirements (NFRs)over software systems has been widely documented. Consequently, cost-effective software production method shall provide means to integrate this type of requirements into the development process. In this vision paper we analyze this assumption over a particular type of software production paradigm: model-driven development (MDD). We report first the current state of MDD approaches with respect to NFRs and remark that, in general, NFRs are not addressed in MDD methods and processes, and we discuss the effects of this situation. Next, we outline a general framework that integrates NFRs into the core of the MDD process and provide a detailed comparison among all the MDD approaches considered. Last, we identify some research issues related to this framework.

  • Access to the full text
    Usage of architectural styles and technologies in IT companies and organizations  Open access

     Ameller, David; Franch Gutierrez, Javier
    Empirical Assessment in Software Architecture
    Presentation's date: 2009-09-14
    Presentation of work at congresses

    Read the abstract Read the abstract Access to the full text Access to the full text Open in new window  Share Reference managers Reference managers Open in new window

    As in many other software engineering activities, Non-Functional Requirements (NFR) are fundamental in the process of selection of the architectural style and the technologies for developing a software system. To know more about this issue, we are currently driving a survey to find out which architectural styles and technologies are being in use in IT companies and organizations, and their relation to types of NFR. We want to apply this knowledge to Model-Driven Software Development (MDSD), and in fact we are currently developing a framework that considers NFR in the MDSD process.

    Postprint (author’s final draft)

  • Access to the full text
    Definición de una ontología para el proceso de DSDM considerando requisitos no-funcionales  Open access

     Ameller, David; Franch Gutierrez, Javier
    Workshop on DSDM
    Presentation's date: 2009-08-08
    Presentation of work at congresses

    Read the abstract Read the abstract Access to the full text Access to the full text Open in new window  Share Reference managers Reference managers Open in new window

    La consideración de los requisitos no-funcionales (RNF) en el proceso de desarrollo de software dirigido por modelos (DSDM) impacta en la educción del estilo arquitectónico del sistema software resultante, así como en la selección de las tecnologías más apropiadas para su implementación. A partir de un análisis de dicho impacto, en este trabajo se enumeran, definen y relacionan los conceptos fundamentales que emergen en el tratamiento de los RNF en el proceso de DSDM, y se ilustra su rol en el proceso mediante un escenarios de uso.

  • Assigning Treatments to Responsibilities in Software Architectures

     Ameller, David; Franch Gutierrez, Javier
    Date of publication: 2008-02-28
    Book chapter

     Share Reference managers Reference managers Open in new window

  • Service Level Agreement Monitor (SALMon)

     Ameller, David; Franch Gutierrez, Javier
    Date of publication: 2008-02
    Book chapter

     Share Reference managers Reference managers Open in new window

  • Access to the full text
    Monitoring adaptable SOA systems using SALMon  Open access

     Oriol Hilari, Marc; Marco Gomez, Jordi; Franch Gutierrez, Javier; Ameller, David
    Workshop on Monitoring, Adaptation and Beyond (MONA+)
    Presentation's date: 2008-12
    Presentation of work at congresses

    Read the abstract Read the abstract Access to the full text Access to the full text Open in new window  Share Reference managers Reference managers Open in new window

    Adaptability is a key feature of Service-Oriented-Architecture (SOA) Systems. These systems must evolve themselves in order to ensure their initial requirement as well as to satisfy arising new ones. In SOA Systems there are a lot of dependencies between services, but each service is an independent element of the system. In this situation it is necessary not only ensuring that the system fulfils its requirements but also that every system satisfies its own requirements, and dynamically adapting the system when some of them cannot be ensured. In this paper we propose a SOA system, named Service Level Agreement Monitor (SALMon), for monitoring and adapting SOA Systems at run time. SALMon is based on monitoring the services for detecting Service Level Agreement (SLA) violations. The SALMon architecture is composed of three types of components: Monitors, which are composed of measure instruments themselves; the Analyzer, which checks the SLA rules; and the Decision Maker that performs corrective actions to satisfy SLA rules again. These three types of components are mostly technology-independent and the act as service inside of a SOA system making our architecture very scalable and comfortable for its purpose.

  • Service Level Agreement Monitor (SALMon)

     Ameller, David; Franch Gutierrez, Javier
    International Conference on COTS-Based Software Systems
    Presentation of work at congresses

     Share Reference managers Reference managers Open in new window

  • Asignación de Tratamientos a Responsabilidades en el contexto del Diseño Arquitectónico Dirigido por Modelos

     Ameller, David; Franch Gutierrez, Javier
    XII Jornadas de Ingeniería del Software y Bases de Datos (JISBD 2007)
    Presentation's date: 2007-09-11
    Presentation of work at congresses

     Share Reference managers Reference managers Open in new window

  • Assigning Treatments to Responsibilities in Software Architectures

     Ameller, David; Franch Gutierrez, Javier
    33rd EUROMICRO-SEAA 2007 Conference on Software Engineering and Advanced Applications
    Presentation of work at congresses

     Share Reference managers Reference managers Open in new window