Using patterns to model variability in product families

Keepence, B.; Mannion, Mike

doi:10.1109/52.776957

Cited by 84 publications

(55 citation statements)

References 10 publications

(1 reference statement)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The method for requirements authoring and management (MRAM) proposed by Keepance and Mannion uses discriminants to structure requirements [20]. Discriminants describe how one product is different from another product variant.…”

Section: Related Workmentioning

confidence: 99%

Feature Interaction and Dependencies: Modeling Features for Reengineering a Legacy Product Line

Ferber

Haag

Savolainen

2002

Software Product Lines

View full text Add to dashboard Cite

Abstract. Reengineering a legacy product line has been addressed very little by current product line research activities. This paper introduces a method to investigate feature dependencies and interactions, which restricts the variants that can be derived from the legacy product line assets. Reorganizing the product line assets with respect to new requirements requires more knowledge than what is easily provided by the classical feature-modeling approaches. Hence, adding all the feature dependencies and interactions into the feature tree results in unreadable and unmanageable feature models that fail to achieve their original goals. We therefore propose two complementary views to represent the feature model. One view shows the hierarchical refinement of features similar to common featuremodeling approaches in a feature tree. The second view describes what kind of dependencies and interactions there are between various features. We show two examples of feature dependencies and interactions in the context of an engine-control software product line, and we demonstrate how our approach helps to define correct product configurations from product line variants.

show abstract

Section: Related Workmentioning

confidence: 99%

Feature Interaction and Dependencies: Modeling Features for Reengineering a Legacy Product Line

Ferber

Haag

Savolainen

2002

Software Product Lines

View full text Add to dashboard Cite

show abstract

“…Keepence and Mannion [5] defined three patterns of class structure design. These patterns are very similar to the mandatory, alternative, and optional feature properties in the feature oriented domain analysis.…”

Section: Related Workmentioning

confidence: 99%

A Method for Efficient Extensibility Improvements in Embedded Software Evolution

Sasaki

Yoshioka²,

Tahara³

et al. 2015

JSW

View full text Add to dashboard Cite

Lightweight development processes like Agile have emerged in response to rapidly changing market requirements. However, software evolution processes including Agile are inadequate for software in embedded systems, as software undergoes frequent refactoring, targeting only immediate requirements. As a result, maintainability decreases because the system is not designed to respond to changes in the associated hardware. In this paper, we propose a method for improving extensibility. We also propose a technique for detecting and suggesting extension design patterns automatically. Our approach is based on analyses of the call graph and inheritance structure of source code to identify a layer structure that is specific to embedded software. These techniques provide us with objective and quantitative information about extensibility. We applied the proposed method to an actual product's code continuously and could verify an improvement in the system's extensibility.

show abstract

“…In [Keepence & Mannion, 1999], authors have developed a method for building product family models using a set of predefined patterns to model family variations. The method starts by analyzing existing user requirements from systems within the product family and identifying the discriminants.…”

Section: Single Multiple and Option Patternsmentioning

confidence: 99%

“…Section 2.3). Up to our knowledge, there are two main sets of patterns that allow modeling variability in product lines: (1) single, multiple, and option patterns [Keepence & Mannion, 1999], and (2) patterns for evolving event-based systems [Tragatschnig et al, 2013].…”

Section: Software Variability Modeling Patternsmentioning

confidence: 99%

“…Class A does not assume that Class B exists, and therefore can be reused whether or not Class B is reused. The option pattern can also be applied to "related-to" and "aggregation" associations [Keepence & Mannion, 1999]. The single, multiple, and option patterns have been put into practice for modeling product families in the spacecraft mission-planning domain.…”

mentioning

confidence: 99%

See 1 more Smart Citation

Enhancing Variability Modeling in Process-Aware Information Systems through Change Patterns

Esteras¹

View full text Add to dashboard Cite

Using patterns to model variability in product families

Abstract: previous to that, he spent seven years as a systems engineer in the European space industry, working on ground and control systems. His interests are in converged networks, product-line engineering, and requirements engineering.

Cited by 84 publications

References 10 publications

Feature Interaction and Dependencies: Modeling Features for Reengineering a Legacy Product Line

Feature Interaction and Dependencies: Modeling Features for Reengineering a Legacy Product Line

A Method for Efficient Extensibility Improvements in Embedded Software Evolution

Enhancing Variability Modeling in Process-Aware Information Systems through Change Patterns

Contact Info

Product

Resources

About