Eila Niemelä
Abstract
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.
- 1 Bachmann, F., Bass, L., Chastek, G., Donohoe, P., Peruzzi, F. The Architecture Based Design Method. CMU/SEI-2000-TR-0001. Carnegie Mellon University, Software Engineering Institute, 2000.Google Scholar
- 2 Bosch, J. Design and use of software architectures. Adopting and evolving a product line approach. Addison-Wesley, Harlow, 2000. Google ScholarDigital Library
- 3 Cohen. L. Quality Function Deployment: how to make QFD work for you. Addison Wesley, Reading, MA, 1995.Google Scholar
- 4 DeBaud, JM., Schmid, K. A Systematic Approach to Derive the Scope of Software Product Lines. In Proceedings of Int. Conf. on Software Engineering, ICSE'99, (Los Angeles, CA, May 1999), 34-43. Google ScholarDigital Library
- 5 Dobrica, L., Niemela, E. Product line architecture analysis. Submitted for 4-volume books on Software Architectures, Components, and Frameworks. Fayad, M., Garlan, D. (eds.), 2001.Google Scholar
- 6 Kalaoja, J., Niemela, E., Perunka, H. Feature Modelling of Component-Based Embedded Software. Proceedings of 8 th IEEE International Workshop on Software Technology and Engineering Practice incorporating Computer Aided Software Engineering. STEP 1997. IEEE Computer Society, Los Alamitos, CA, (London UK, July 1997), 444-451. Google ScholarDigital Library
- 7 Mayer, M. H., Lehnerd, A. P. The power of product platforms. Building value and cost leadership. The Free Press, New York, 1997.Google Scholar
- 8 Niemela, E., Kuikka, S, Vilkuna, K., Ahonen, J., Lampola, M., Forssel, M., Korhonen, R., Seppanen, V., Venta, O. Industrial software components. Development concerns and strategic initiatives. Technology survey 89/2000. Technology Development Center Tekes, (in Finnish).Google Scholar
- 9 Robertson, D., Ulrich, K. Planning for product platforms. Sloan Management Review 39, 4 (Summer 1998), 19-31.Google Scholar
- 10 Schmid, K. Scoping software product line. An analysis of an emerging technology. In Proceedings of Software Product Line. Experience and research directions. Donohoe, P. (ed.), Kluwer Academic Publishers, Massachusetts, 2000, 513-532. Google ScholarDigital Library
- 11 Wiles, E. Economic models of software reuse: A survey, comparison and partial validation. Technical Report UWA- DCS-99-032, Department of Computer Science, University of Wales, UK, (April 1999).Google Scholar
Index Terms
- Product line software engineering of embedded systems
Recommendations
Product line software engineering of embedded systems
SSR '01: Proceedings of the 2001 symposium on Software reusability: putting software reuse in contextIn 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 ...
A Pattern-Based Modeling Approach for Software Product Line Engineering
HICSS '13: Proceedings of the 2013 46th Hawaii International Conference on System SciencesThis paper addresses the problem of variability in software product line (SPL) engineering by first considering different SPL model-based approaches and in particular the tradeoff between the development effort in domain engineering vs. application ...
Using Documentation for Product Line Scoping
Product line scoping is the process of determining which of an organization's products, features, and domains would find systematic reuse economically useful. Scoping is generally the first phase in product line engineering. For a decade, it has been ...
Comments