The UML «extend» Relationship as Support for Software Variability

Azevedo, Sofia; Machado, Ricardo J.; Bragança, Alexandre; Ribeiro, Hugo

doi:10.1007/978-3-642-15579-6_39

Cited by 5 publications

(12 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Also the «extend» relationship is needed to formalize at an early stage (the use case modeling) where variation will occur when instantiating the product line (Bosch et al [40] mention the need for describing variability within different modeling levels such as the requirements one). Figure 1 illustrates the variability types we consider and propose to be applicable in the context of use cases [1]. Use cases can be non-option or option.…”

Section: Related Workmentioning

confidence: 99%

“…Alternatives [1] represent supplementary functionality (or supplementary behavioral increments) since they are not essential for a product without variability to function. It shall be noted that alternatives are no longer supplementary when product line members are instantiated from the product line.…”

Section: The «Extend» Relationshipmentioning

confidence: 99%

“…a family of software products that have been developed with explicit concern about variability (and consequently commonality) during the development process (see [1] for basic references on variability). This paper envisions use cases according to the perspectives of detail and variability.…”

mentioning

confidence: 99%

See 2 more Smart Citations

On the refinement of use case models with variability support

Azevedo

Machado

Bragança³

et al. 2011

Innovations Syst Softw Eng

Self Cite

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%

Section: The «Extend» Relationshipmentioning

confidence: 99%

See 1 more Smart Citation

On the refinement of use case models with variability support

Azevedo

Machado

Bragança³

et al. 2011

Innovations Syst Softw Eng

Self Cite

View full text Add to dashboard Cite

show abstract

“…[20], and Junior, E.A.O., Itana MS Gimenes, and José C. Maldonado [6] use stereotypes to model variability in use case diagram. To model variability in use case diagram, Azevedo, S., et al [21] extend the existing relations and many stereotypes. Braganca, A., and Ricardo Jorge Machado [22] extend the UML use case meta-model to remove all ambiguities.…”

Section: Related Workmentioning

confidence: 99%

An Incremental Approach to Manage Variability in Software Product Line Requirements

Zamanifard¹,

Khosravi²,

Sabouri³

2015

IJCEE

View full text Add to dashboard Cite

Abstract:In software product line engineering, systematic variability management must be applied to all stages of the development lifecycle and every artifact produced. This is not an easy task for the artifacts describing system requirements, as they are usually less structured and formal compared to design and implementation models. In this paper, we overhead in documenting the requirements present an incremental and modular method to capture variability in system requirements described as use cases. Following the well-known technique of delta-oriented programming, our method captures commonalities among the requirements in terms of a core model and applies the optional extensions or changes to the core model expressed in terms of delta modules. The method also addresses cross-cutting changes that span several use cases. We have also developed an integrated web-based toolset to effectively manage the requirements models, facilitating product derivation at virtually no cost. We have applied the proposed approach to a real-world case study which shows an acceptable overhead in documenting the requirements and results in considerable saving in generating documents for the specific products as well as enabling traceability of features into requirements. The incremental characteristic of our method makes it also suitable for handling variability in time, by enabling the analysts to specify requirements changes in a modular way.

show abstract

“…As Halmans and Pohl [2] stated, textual representation has shortcomings: variation points are not explicit, variability constraints (e.g., number of variants that can be selected for a variation point) cannot be easily represented, and variants are hard to identify. There are several approaches [2] [9] [10] proposing extensions to use case diagrams to overcome these shortcomings. Nevertheless, these extensions are usually not sufficient to express all variabilities at the required level of granularity.…”

Section: Introductionmentioning

confidence: 99%

Applying product line Use case modeling in an industrial automotive embedded system: Lessons learned and a refined approach

Hajri

Göknil

Briand

et al. 2015

2015 ACM/IEEE 18th International Conference on Model Driven Engineering Languages and Systems (MODELS)

View full text Add to dashboard Cite

Abstract-In this paper, we propose, apply, and assess Product line Use case modeling Method (PUM), an approach that supports modeling variability at different levels of granularity in use cases and domain models. Our motivation is that, in many software development environments, use case modeling drives interactions among stakeholders and, therefore, use cases and domain models are common practice for requirements elicitation and analysis. In PUM, we integrate and adapt existing product line extensions for use cases and introduce some template extensions for use case specifications. Variability is captured in use case diagrams while it is reflected at a greater level of detail in use case specifications. Variability in domain concepts is captured in domain models. PUM is supported by a tool relying on Natural Language Processing (NLP). We successfully applied PUM to an industrial automotive embedded system and report lessons learned and results from structured interviews with experienced engineers.

show abstract

The UML «extend» Relationship as Support for Software Variability

Cited by 5 publications

References 6 publications

On the refinement of use case models with variability support

On the refinement of use case models with variability support

An Incremental Approach to Manage Variability in Software Product Line Requirements

Applying product line Use case modeling in an industrial automotive embedded system: Lessons learned and a refined approach

Contact Info

Product

Resources

About