The Rational Unified Process: an introduction
The Rational Unified Process: an introduction
Software product-line engineering: a family-based software development process
Software product-line engineering: a family-based software development process
Component-based product line development: the KobrA approach
Proceedings of the first conference on Software product lines : experience and research directions: experience and research directions
Component-based product line engineering with UML
Component-based product line engineering with UML
Designing Software Product Lines with UML: From Use Cases to Pattern-Based Software Architectures
Designing Software Product Lines with UML: From Use Cases to Pattern-Based Software Architectures
Software Product Line Engineering: Foundations, Principles and Techniques
Software Product Line Engineering: Foundations, Principles and Techniques
A systematic mapping study of software product lines testing
Information and Software Technology
Six years of systematic literature reviews in software engineering: An updated tertiary study
Information and Software Technology
Extending the RiPLE-DE process with quality attribute variability realization
Proceedings of the joint ACM SIGSOFT conference -- QoSA and ACM SIGSOFT symposium -- ISARCS on Quality of software architectures -- QoSA and architecting critical systems -- ISARCS
A systematic review of quality attributes and measures for software product lines
Software Quality Control
Evidence of software inspection on feature specification for software product lines
Journal of Systems and Software
Hi-index | 0.00 |
Software Product Lines are growing as a systematic way for achieving reuse in software companies. It involves three processes: domain engineering, application engineeringand management. In domain engineering, assets that will be reused by products are developed, composing the core assets. In this context, the product line architecture, also called Domain Specific Software Architecture(DSSA), is an essential member in the collection of core assets. A good DSSA increases the probability of the success of applications that will be instantiated from it. In order to design a good DSSA, a process should be followed to manage domain's variability and commonality. On the other hand, companies that are moving from single system development to software product lines need systematic activities for taking advantage of existing assets to develop a DSSA. Thus, this paper presents a systematic review on domain design approaches, which can be useful for companies to understand the current scenario, and to choose a more suitable one or adapt them for their needs.