A systematic approach to derive the scope of software product lines
Proceedings of the 21st international conference on Software engineering
Design and use of software architectures: adopting and evolving a product-line approach
Design and use of software architectures: adopting and evolving a product-line approach
Scoping software product lines: an analysis of an emerging technology
Proceedings of the first conference on Software product lines : experience and research directions: experience and research directions
Feature Modelling of Component-Based Embedded Software
STEP '97 Proceedings of the 8th International Workshop on Software Technology and Engineering Practice (STEP '97) (including CASE '97)
PROFES '02 Proceedings of the 4th International Conference on Product Focused Software Process Improvement
Product line variability support by FORM and Mecano model integration
ACM SIGSOFT Software Engineering Notes
Maintainability and reusability issues in CORBA-based systems
Proceedings of the 43rd annual Southeast regional conference - Volume 2
Capturing quality requirements of product family architecture
Information and Software Technology
Strategies of product family architecture development
SPLC'05 Proceedings of the 9th international conference on Software Product Lines
| Hi-index | 0.00 |
In order to be able to determine whether the product line approach is suitable, a company needs to analyse its business drivers, commonality of existing products, domain knowledge owned by the engineering staff, and quality of the representations of existing software artefacts. In this paper we present evaluation criteria for the development of a product line and give an overview of the current state of practices in the embedded software area. Evaluation criteria are divided into three classes. Business drivers of a product line are defined by analysing product assortment and business manners. Domains and personnel are considered in the analysis of the preconditions and targets of a product line. In the development of core assets, elements that affect assets engineering are considered as well as the mechanisms needed in their maintenance. A product line architecture that brings about a balance between sub- domains and their most important properties is an investment that must be looked after. However, the subdomains need flexibility to use, change and manage their own technologies, and evolve separately, but in a controlled way.