Software architecture in practice
Software architecture in practice
Architectural structures and views
ISAW '98 Proceedings of the third international workshop on Software architecture
A systematic approach to derive the scope of software product lines
Proceedings of the 21st international conference on Software engineering
Aspect-oriented analysis for product line architecture
Proceedings of the first conference on Software product lines : experience and research directions: experience and research directions
Architectural Design for Evolution by Analyzing Requirements on Quality Attributes
APSEC '01 Proceedings of the Eighth Asia-Pacific on Software Engineering Conference
Product derivation in software product families: a case study
Journal of Systems and Software - Special issue: The new context for software engineering education and training
Proceedings of the 13th International Software Product Line Conference
REV '09 Proceedings of the 2009 Fourth International Workshop on Requirements Engineering Visualization
Journal of Systems and Software
Proceedings of the 16th International Software Product Line Conference - Volume 1
Performance variability in software product lines: a case study in the telecommunication domain
Proceedings of the 17th International Software Product Line Conference
Hi-index | 0.00 |
It is indispensable for strategic product line development to define the proper scope of the product line. Once the scope has been defined, we examine the corresponding product line architecture to realize systematic reuse for the product line. Therefore, in defining the scope, we have to decide whether or not it is appropriate to share the same architecture for the products in the product line. The appropriateness of sharing the same architecture among multiple products has to be examined from two points of view. One is from the point of view of the individual optimality (i.e., whether it is good for each product to use the shared architecture), and the other is from the point of view of the whole optimality (i.e., whether it is good for the product line as a whole to share the architecture). In this paper, we propose a method for product line scoping. We consider scoping as a decision-making activity in which we evaluate multiple candidates for the scope and then select the proper one after examining the appropriateness from the two points of view. In order to demonstrate its applicability, we applied the method to the actual problem picked up from Japanese ITS (Intelligent Transport Systems) projects.