Product line software engineering of embedded systems

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.

REFERENCES

• 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.
• 2: Jan Bosch, Design and use of software architectures: adopting and evolving a product-line approach, ACM Press/Addison-Wesley Publishing Co., New York, NY, 2000
• 3: Cohen. L. Quality Function Deployment: how to make QFD work for you. Addison Wesley, Reading, MA, 1995.
• 4: Jean-Marc DeBaud , Klaus Schmid, A systematic approach to derive the scope of software product lines, Proceedings of the 21st international conference on Software engineering, p.34-43, May 16-22, 1999, Los Angeles, California, United States [doi>10.1145/302405.302409]
• 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.
• 6: Jarmo Kalaoja , Eila Niemelä , Harri Perunka, Feature Modelling of Component-Based Embedded Software, Proceedings of the 8th International Workshop on Software Technology and Engineering Practice (STEP '97) (including CASE '97), p.444, July 14-18, 1997
• 7: Mayer, M. H., Lehnerd, A. P. The power of product platforms. Building value and cost leadership. The Free Press, New York, 1997.
• 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).
• 9: Robertson, D., Ulrich, K. Planning for product platforms. Sloan Management Review 39, 4 (Summer 1998), 19-31.
• 10: Klaus Schmid, 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, p.513-532, November 2000, Denver, Colorado, United States
• 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).

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING

Additional Classification:
  C. Computer Systems Organization
  C.3 SPECIAL-PURPOSE AND APPLICATION-BASED SYSTEMS
      Subjects: Real-time and embedded systems

  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.11 Software Architectures
            Subjects: Domain-specific architectures
  D.4 OPERATING SYSTEMS
      D.4.7 Organization and Design
          Subjects: Real-time systems and embedded systems

  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.3 Software Management
          Subjects: Software development

General Terms:
Design, Measurement, Performance, Theory

Keywords:
domain engineering, product features, product line architecture, quality attributes