Graph modelling of a refactoring process for Product Line Architecture design

Losavio, Francisca; Ordaz, Óscar; Lévy, Nicole; Baiotto, Anthony

doi:10.1109/clei.2013.6670632

Cited by 6 publications

(10 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…(Bastarrica, Rivas, & Rossel, 2007) (Sánchez, Loughran, Fuentes, & Garcia, 2009) (Brito, Rubira, & de Lemos, 2009) (Losavio, Ordaz, Levy, & Baiotto, 2013)), activity diagram (e.g. (Abu-Matar & Gomaa, 2011), (Losavio et al, 2013)) and sequence diagram (e.g. (Laser, Rodrigues, Domingues, Oliveira, & Zorzo, 2015)).…”

Section: Rq1: What Approaches Have Been Proposed To Represent Variabimentioning

confidence: 99%

Representing Variability in Software Architecture: A Systematic Literature Review

Haider

Woods²,

Bashroush³

2018

IJSECS

View full text Add to dashboard Cite

Variability in software-intensive systems is the ability of a software artefact (e.g., a system, subsystem, or component) to be extended, customised or configured for deployment in a specific context. Software Architecture is a high-level description of a software-intensive system that abstracts the system implementation details allowing the architect to view the system as a whole. Although variability in software architecture is recognised as a challenge in multiple domains, there has been no formal consensus on how variability should be captured or represented. The objective of this research was to provide a snapshot of the state-of-the-art on representing variability in software architecture while assessing the nature of the different approaches. To achieve this objective, a Systematic Literature Review (SLR) was conducted covering literature produced from January 1991 until June 2016. Then, grounded theory was used to conduct the analysis and draw conclusions from data, minimising threats to validity. In this paper, we report on the findings from the study.

show abstract

Section: Rq1: What Approaches Have Been Proposed To Represent Variabimentioning

confidence: 99%

Representing Variability in Software Architecture: A Systematic Literature Review

Haider

Woods²,

Bashroush³

2018

IJSECS

View full text Add to dashboard Cite

show abstract

“…Moreover, existing architectural methods and evaluation techniques for single-systems are reengineered and not specifically designed for SPL [6,7]; in general NFRs are not considered as deeply as they should, and they drive the whole architectural design process [5,6]. The goal of this work is to propose a bottom-up design process to build the SPL RA from existing product, inspired in [8,28,33]. Our process is based on a graph structure to model the product architecture represented by a connected graph or valid architectural configuration (P, R), where P are the components, and the symmetric relation R are the connectors.…”

Section: Introductionmentioning

confidence: 99%

“…An initial candidate architecture (CA) is produced automatically by the union of the components of the architectural configurations of each given product and preserving the connections; the common core is the set of common components present in each products' architecture, the others are considered variant components. CA is then completed with new variant components from the Softgoals Interdependency Graph (SIG) model [12,13] and with an Extended Quality Model (EQM) [8,9], to satisfy quality properties with architectural solutions; finally, RA is obtained grouping CA variants with similar tasks into variation points. The terminology of Pohl et al [2] is followed for the variability modeling.…”

Section: Introductionmentioning

confidence: 99%

Quality-based bottom-up design of reference architecture applied to Healthcare Integrated Information Systems

Losavio

Ordaz

Esteller

2015

2015 IEEE 9th International Conference on Research Challenges in Information Science (RCIS)

Self Cite

View full text Add to dashboard Cite

Software Product Line (SPL) is a set of softwareintensive systems, sharing a common, managed set of features that satisfy the specific needs of a particular market segment or domain. Reference Architecture (RA) is the main asset shared by all SPL products; it covers commonality and variability of the SPL family of products or systems and it is used as a template to produce new products. We propose a semi-automatic bottom-up refactoring process to build RA considering the logic view (static aspects) of architectures of existing products in a domain, represented by a connected graph or valid architectural configuration. A candidate architecture (CA) is obtained automatically and manually completed by introducing new variants to satisfy quality properties. RA is finally built by grouping into variation points CA variants accomplishing similar tasks. We consider functional and non-functional variability modeling of components and connectors. The quality properties to be satisfied are specified by the ISO/IEC 25010 quality model, using scenarios of available architectural solutions for each quality property that can be traced to the original component requiring it; our approach combines quality standards with goaloriented techniques to consider non-functional variability, which is still an open research issue in SPL. The complete RA design process is applied to the domain of Integrated Healthcare Information Systems.Keywords-software product line, reference architecture, bottom-up design, non-functional requirements, quality model.

show abstract

“…To cope with this problem, many adaptations of features models can be found in the literature to consider also NFR [7] [25]. In our approach, FS are derived directly by instantiating RA, which has been constructed by a bottomup (extractive) semiautomatic process [12] [13], by refactoring architectures of existing products on the market. The bottom-up approach is claimed to be faster, less expansive, and more practical for industrial usage than classic SPL top-down approaches; however their limitation is that the number of existing products can be small [4].…”

Section: Introductionmentioning

confidence: 99%

“…The bottom-up approach is claimed to be faster, less expansive, and more practical for industrial usage than classic SPL top-down approaches; however their limitation is that the number of existing products can be small [4]. In our case, domain knowledge has been captured from the available documentation on three widely used existing products and it is imbedded into RA, which has been built considering explicitly quality properties related to FR, capturing also the overall domain quality [12] [13]. However, if our initial baseline or candidate architecture obtained automatically from the union of the architectural configurations of the existing products considered, is found limited due to the bottom-up construction, it could be extended with new components, by studying future products that can be built for the SPL.…”

Section: Introductionmentioning

confidence: 99%

Ontological approach to derive product configurations from a Software Product Line Reference Architecture

Losavio

Ordaz²,

Jean

2016

Ciencia Y Tecnología

Self Cite

View full text Add to dashboard Cite

Software Product Lines (SPL) based on reuse, claim to improve evolution, time to market and decrease software development costs. Concrete software products or systems, members of the SPL family, are derived by instantiating a generic Reference Architecture (RA), holding common and variant components. The construction of RA is a complex and costly task, as well as its usage for product derivation, due to the huge number of variants, essentially caused by non functional requirements variability. In consequence, the selection of an RA instance or Feasible Solution (FS), meeting RA constraints and customer requirements, is not straightforward. In this work RA is built by a bottom-up process from existing products; RA and its instances are represented by a non-directed connected graph. The HIS-RA Ontology also represents RA and captures Healthcare Integrated Information Systems (HIS) domain knowledge. Moreover, FS must be connected (the induced graph by FS in RA has no isolated components), consistent (it verifies consistency rules among FS components), and working (it meets domain functional (FR) and non functional (NFR) requirements). The main goal of this paper is to define a semiautomatic process (FFSP), to derive consistency rules using the HIS-RA Ontology built-in reasoning capabilities, to construct consistent, connected and working FS. Software quality is considered by FFSP in the traceability between FR and NFR, and it is specified by ISO/IEC 25010, to guarantee RA evolution and the overall concrete product configuration quality. FFSP is validated on a HIS domain a case study.

show abstract

Graph modelling of a refactoring process for Product Line Architecture design

Cited by 6 publications

References 22 publications

Representing Variability in Software Architecture: A Systematic Literature Review

Representing Variability in Software Architecture: A Systematic Literature Review

Quality-based bottom-up design of reference architecture applied to Healthcare Integrated Information Systems

Ontological approach to derive product configurations from a Software Product Line Reference Architecture

Contact Info

Product

Resources

About