Expression and Usage of the Variability in the Software Product Lines

Salicki, Serge; Farcet, Nicolas

doi:10.1007/3-540-47833-7_27

Cited by 10 publications

(8 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Pohl [20] uses the graphical notation used by Halmans and himself [19] to represent variability in use case diagrams. Salicki and Farcet [21] talk about variation points and additionally in decision models.…”

Section: Related Workmentioning

confidence: 99%

On the refinement of use case models with variability support

Azevedo

Machado

Bragança³

et al. 2011

Innovations Syst Softw Eng

View full text Add to dashboard Cite

Modeling software product lines shall imply modeling from different perspectives with different modeling artifacts such as use case diagrams, component diagrams, class diagrams, activity diagrams, sequence diagrams and others. In this paper, we elaborate on use cases for modeling product lines and we explore them from the perspective of variability by working with the unified modeling language (UML) «extend» relationship. We also explore them from the perspective of detail by (functionally) refining use cases with «extend» relationships between them. This paper's intent is to provide for comprehension about use case modeling with functional refinement when variability is present.

show abstract

Section: Related Workmentioning

confidence: 99%

On the refinement of use case models with variability support

Azevedo

Machado

Bragança³

et al. 2011

Innovations Syst Softw Eng

View full text Add to dashboard Cite

show abstract

“…There are several unrelated works in this area for example: [2][3][4][5][6][7], in consequence, we have identified the need of a shared set of common concepts. Even more, in our analysis of the requirements management models, we have found that no single model covers in full extent the current needs of system family engineering (SFE).…”

Section: Related Workmentioning

confidence: 99%

“…Even more, in our analysis of the requirements management models, we have found that no single model covers in full extent the current needs of system family engineering (SFE). Thus, the work presented in this document takes as inputs the published metamodels provided, among others, by: − ALCATEL-SPLIT (Alcatel Software Product Line Integrated Technology) [ 8]; whose key issue in the management of product line requirements is the capability to distinguish if a certain requirement is optional, alternative or parameterized for a certain product [ 4]. − The Helsinki University of Technology HUT model [ 9] provides a different view of goals, features and constraints.…”

Section: Related Workmentioning

confidence: 99%

A Meta-model for Requirements Engineering in System Family Context for Software Process Improvement Using CMMI

Cerón

Dueñas

Serrano

et al. 2005

Product Focused Software Process Improvement

View full text Add to dashboard Cite

Abstract. Software industries are pursuing the development of software intensive systems with a greater degree of re-use, reduction of costs, and shorter time to market. One of the successful approaches taken is based on the development of sets of similar systems where development efforts are shared. This approach is known as System Families. This article discusses an important issue in system family engineering activities: requirements modelling in system family context. The requirements must contain both the common and variable parts. Also, functional and non-functional aspects have to be considered in system family approach. Besides, an organization framework must be taken into account for requirements management. Some meta-models for these issues in system family are proposed and discussed. Based on the proposed model, a process for requirements management and development according to CMMI practices has been created.

show abstract

“…Asset variation points discussed in [16] deal with expressing variability in models of product lines [3]. A variation point is identified by several characteristics (e.g., point reference, and context, use and rationale of the variation point) that uniquely identify that point in the product lines.…”

Section: Related Workmentioning

confidence: 99%

Managing the quality of software product line architectures through reusable model transformations

Kavimandan

Gokhale

Karsai

et al. 2011

Proceedings of the Joint ACM SIGSOFT Conference -- QoSA and ACM SIGSOFT Symposium -- ISARCS on Quality of Software Architecture

View full text Add to dashboard Cite

In model-driven engineering of applications, the quality of the software architecture is realized and preserved in the successive stages of its lifecycle through model transformations. However, limited support for reuse in contemporary model transformation techniques forces developers of product line architectures to reinvent transformation rules for every variant of the product line, which can adversely impact developer productivity and in turn degrade the quality of the resulting software architecture for the variant. To overcome these challenges, this paper presents the MTS (Modeltransformation Templatization and Specialization) generative transformation process, which promotes reuse in model transformations through parameterization and specialization of transformation rules. MTS defines two higher order transformations to capture the variability in transformation rules and to specialize them across product variants. The core idea behind MTS is realized within a graphical model transformation tool in a way that is minimally intrusive to the underlying tool's implementation. The paper uses two product line case studies to evaluate MTS in terms of reduction in efforts to define model transformation rules as new variants are added to the product line, and the overhead in executing the higher order transformations. These metrics provide an indirect measure of how potential degradation in the quality of software architectures of product lines caused due to lack of reuse can be alleviated by MTS.

show abstract

Expression and Usage of the Variability in the Software Product Lines

Cited by 10 publications

References 2 publications

On the refinement of use case models with variability support

On the refinement of use case models with variability support

A Meta-model for Requirements Engineering in System Family Context for Software Process Improvement Using CMMI

Managing the quality of software product line architectures through reusable model transformations

Contact Info

Product

Resources

About