REARM: A Reuse-Based Economic Model for Software Reference Architectures

Model and Data Engineering

Ameller

et al. 2016

Self Cite

Abstract. Adapting software systems at run-time is a key issue, especially when these systems consist of components used as intermediary for human-computer interaction. In this sense, model transformation techniques have a widespread acceptance as a mechanism for adapting and evolving the software architecture of such systems. However, existing model transformations often focus on functional requirements, and quality attributes are only manually considered after the transformations are done. This paper aims to improve the quality of adaptations and evolutions in component-based software systems by taking into account quality attributes within the model transformation process. To this end, we present a quality-aware transformation process using software architecture metrics to select among many alternative model transformations. Such metrics evaluate the quality attributes of an architecture. We validate the presented quality-aware transformation process in ENIA, a geographic information system whose user interfaces are based on coarsegrained components and need to be adapted at run-time.

Section: Step 2: Measuring Qas and Constraints At Run-timementioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Exploring Quality-Aware Architectural Transformations at Run-Time: The ENIA Case

Criado

Model and Data Engineering

Ameller

et al. 2016

Self Cite

“… (B9) Elaboration of the organization mission, vision and strategy [2].  (D1) The need for an initial investment [6].  (D2) Inefficient instantiation for the organization's systems [5].…”

Section: Benefits and Drawbacks Of Ras From The Literaturementioning

confidence: 99%

“…As in [1], we refer to the definition of RA as stated by Bass et al: "a reference model mapped onto software elements and the data flows between them". RAs have become widely studied and used in research and practice [1], as they are claimed to increase speed, reduce operational expenses and improve quality in software systems development mainly due to reuse [6]. Nonetheless, limited evidence exists to support these claims [7].…”

Section: Introductionmentioning

confidence: 99%

Benefits and Drawbacks of Reference Architectures

Ayala

Franch

et al. 2013

Software Architecture

Self Cite

Abstract. Reference architectures (RA) have been studied to create a consistent notion of what constitutes them as well as their benefits and drawbacks. However, few empirical studies have been conducted to provide evidence that support the claims made. To increase this evidence, this paper investigates the actual industrial practice of using RAs. The study consists of a survey with 28 stakeholders from everis, a multinational consulting company based in Spain. We report the findings and contextualize them with previous research.

“…Although the adoption of an RA might have plenty of benefits for an organization, it also implies several challenges, such as the need for an initial investment (Martínez-Fernández et al 2013b) and getting real evidence for driving its design and use (Angelov et al 2013). Currently, organizations have little support for dealing with these two challenges.…”

Section: Research Problemmentioning

confidence: 99%

Towards guidelines for building a business case and gathering evidence of software reference architectures in industry

Ayala

Franch

et al. 2014

J Softw Eng Res Dev

Self Cite

Background: Software reference architectures are becoming widely adopted by organizations that need to support the design and maintenance of software applications of a shared domain. For organizations that plan to adopt this architecture-centric approach, it becomes fundamental to know the return on investment and to understand how software reference architectures are designed, maintained, and used. Unfortunately, there is little evidence-based support to help organizations with these challenges. Methods: We have conducted action research in an industry-academia collaboration between the GESSI research group and everis, a multinational IT consulting firm based in Spain. Results:The results from such collaboration are being packaged in order to create guidelines that could be used in similar contexts as the one of everis. The main result of this paper is the construction of empirically-grounded guidelines that support organizations to decide on the adoption of software reference architectures and to gather evidence to improve RA-related practices. Conclusions: The created guidelines could be used by other organizations outside of our industry-academia collaboration. With this goal in mind, we describe the guidelines in detail for their use.