Commonality and variability in software engineering

Coplien, James O.; Hoffman, Daniel; Weiss, David M.

doi:10.1109/52.730836

Cited by 290 publications

(166 citation statements)

References 10 publications

Supporting

Mentioning

158

Contrasting

Unclassified

Order By: Relevance

“…Type (ii) has grown into today's componentbased software engineering (CBSE) approaches such as [16,18,43]. All types of approach involve a domain engineering activity that captures the requirements that all family instances must share -the commonalities -and the requirements that vary between instances -the variabilities [14] -into a generic, reusable software resource. This is followed by an application engineering activity that uses this resource to generate the specific instance systems as necessary.…”

Section: Related Work In Contextmentioning

confidence: 99%

Rigorous engineering of product-line requirements: A case study in failure management

Snook

Poppleton

Johnson³

2008

Information and Software Technology

View full text Add to dashboard Cite

We consider the failure detection and management function for engine control systems as an application domain where product line engineering is indicated. The need to develop a generic requirement set -for subsequent system instantiation -is complicated by the addition of the high levels of verification demanded by this safety-critical domain, subject to avionics industry standards. We present our case study experience in this area as a candidate method for the engineering, validation and verification of generic requirements using domain engineering and Formal Methods techniques and tools. For a defined class of systems, the case study produces a generic requirement set in UML and an example system instance. Domain analysis and engineering produce a validated model which is integrated with the formal specification/ verification method B by the use of our UML-B profile. The formal verification both of the generic requirement set, and of a simple system instance, is demonstrated using our U2B, ProB and prototype Requirements Manager tools. This work is a demonstrator for a tool-supported method which will be an output of EU project RODIN 1 . The use of existing and prototype formal verification and support tools is discussed. The method, developed in application to this novel combination of product line, failure management and safety-critical engineering, is evaluated and considered to be applicable to a wide range of domains.

show abstract

Section: Related Work In Contextmentioning

confidence: 99%

Rigorous engineering of product-line requirements: A case study in failure management

Snook

Poppleton

Johnson³

2008

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“…Scope, Commonality, and Variability (SCV) analysis [Coplien99] is related work on domain engineering that focuses on identifying common and variable properties of an application domain. SCV uses this information to guide decisions about where and how to address possible variability and where the more "static" implementation strategies could be used.…”

Section: Related Workmentioning

confidence: 99%

“…Ideally, distributed systems are developed as product-line architectures [SAIP] that can be specialized in accordance with customer needs, hardware/software platform characteristics, and different quality of service (QoS) requirements. To minimize the impact of modifications, which is needed for specializing product-line architectures, architects and developers need to decouple the stable parts of their system from the variable parts [Coplien99].…”

Section: Introductionmentioning

confidence: 99%

Concern-Based Composition and Reuse of Distributed Systems

Nechypurenko

Lü

Deng

et al. 2004

Software Reuse: Methods, Techniques, and Tools

View full text Add to dashboard Cite

Abstract. Successful reusable software for large-scale distributed systems often must operate in multiple contexts, e.g., due to (1) integration with other systems using different technologies and platforms, (2) constant fine tuning needed to satisfy changing customer needs, and (3) evolving market conditions resulting from new laws and regulations. This situation causes vexing challenges for developers of reusable software, who must manage the variation between these contexts without overcomplicating their solutions and exceeding project time and effort constraints. This paper provides three contributions to R&D efforts that address these challenges. First, it motivates the use of a concern-based approach to enhance the level of abstraction at which component-based distributed systems are developed and reused to (1) improve software quality and developer productivity, and (2) localize variability aspects to simplify substitution of reusable component implementations. Second, we present our experience dealing with different domain-and middleware-specific variability gained applying model-based component middleware software technologies to develop an Inventory Tracking System that manages the flow of goods in warehouses. Third, we present a concern-based research strategy aimed at effectively managing the variability caused by the presence of multiple middleware platforms and technologies. Our experience to date shows that using model-based software tools and component middleware as the core elements of software composition and reuse -in conjunction with concern-based commonality and variability analysis -helps reduce development complexity, improve system maintainability and reuse, and increase developer productivity.

show abstract

“…Variability and commonality in a product family can be expressed and managed using feature models. In [2] it is stated that inspecting commonality and variability in a systematic way during the domain analysis supports product family identification.…”

Section: Introductionmentioning

confidence: 99%

Feature Modeling and Automated Analysis for a Digital Television Product Family

Gönül¹,

Oğuztüzün²,

Karataş³

2014

IJCEE

View full text Add to dashboard Cite

Abstract-This paper presents a feature modeling endeavour for a television set product family by a major consumer electronics company. This work consists of three stages. First, a feature model is constructed, based on the analysis of the product family requirements. The constructed model is supplemented with a feature glossary. FeatureIDE is used as the model editor. Feature attributes, not supported by FeatureIDE, are represented in the basic feature model by using additional features. Second, the feature model in XML is converted into the schema of the analysis tool, using a custom parser developed for this purpose. Third, the model is analyzed by well-known analysis operations. FAMA is used as the analysis tool. Performance results are obtained. Finally, lessons learned from the whole effort are discussed.Index Terms-Feature modeling, extended feature model, software product lines, commonality, variability, variability management.

show abstract

Commonality and variability in software engineering

Cited by 290 publications

References 10 publications

Rigorous engineering of product-line requirements: A case study in failure management

Rigorous engineering of product-line requirements: A case study in failure management

Concern-Based Composition and Reuse of Distributed Systems

Feature Modeling and Automated Analysis for a Digital Television Product Family

Contact Info

Product

Resources

About