Abstract
The industry of software-intensive systems is facing today both economical and technical challenges. On one hand, shrinking budgets and sharp competition require to reduce significantly development and maintenance costs, shorten lead time, and improve predictability. On the other hand, the size and complexity of systems have dramatically increased in the past few years and have brought considerable technological problems. In order to face these issues, major changes are required regarding the way software products are developed.
A promising approach, which is gaining wide acceptance, is to replace traditional development models by product-line development. Traditional life cycle models have originally been conceived under the assumption that they apply to the development of individual software products, inhibiting the sharing of common assets between projects. Product-line development is based on a different approach, which naturally promotes and supports software reuse. In a productline approach, products addressing a same domain are regarded as a whole and developed as members of a product family.
More precisely, a software product-line is a collection of products sharing a common set of features that address the specific needs of a given business area
The development of core assets is generally termed as domain engineering. The development of new products from the set of reusable assets is generally called application engineering. The whole process is allowed by an adequate organization and a coordinated management.
There is a number of specific practices that are needed to develop and exploit the core assets in a product-line. These practices are not always mature and most of the time only emerging in the context of one-shot developments, that is the developments of single products with no reuse in mind. The levels of reusability and adaptability required by the product-line approach bring additional complexity and formidable challenges with regard to the current technology. Such complexity is today almost not dealt with, and requires significant improvements for the current state-of-the-art in software engineering.
The SEI (Software Engineering Institute) has listed the essential practices required to produce core assets and products in a product-line and to manage the process at multiple level [1].
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
P. Clements and L. Northrop. A framework for software product-line practice-version 1.0. Technical report, Software Engineering Institute, September 1998.
Thomson-CSF (France), Robert Bosch Gmbh (Germany), Ericsson (Sweden), and the European Software Institute (Spain). Praise project (product-line realisation and assessment in industrial settings). ESPRIT Project 28651, 1999. (http://www.esi.es/Projects/Reuse/Praise).
E. Gamma, R. Johnson, R. Helm, and J. Vlissides. Design patterns: Elements of reusable object-oriented software. Addison Wesley, 1995.
European Software Institute. Product-line architectures and technologies to manage them. Technical report, European Software Institute, 1998.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 1999 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Lalanda, P., Bosch, J., Lerchundi, R., Cherki, S. (1999). Object Technology for Product-Line Architectures. In: Moreira, A. (eds) Object-Oriented Technology ECOOP’99 Workshop Reader. ECOOP 1999. Lecture Notes in Computer Science, vol 1743. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-46589-8_11
Download citation
DOI: https://doi.org/10.1007/3-540-46589-8_11
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-66954-8
Online ISBN: 978-3-540-46589-8
eBook Packages: Springer Book Archive