Product line software engineering of embedded systems

Eila Niemelä, Tuomas Ihme

Research output: Contribution to journalArticleScientificpeer-review

11 Citations (Scopus)

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.
Original languageEnglish
Pages (from-to)118-125
Number of pages8
JournalACM SIGSOFT Software Engineering Notes
Volume26
Issue number3
DOIs
Publication statusPublished - 2001
MoE publication typeA1 Journal article-refereed
Event2001 Symposium on Software Reusability SSR '01 - Toronto, Canada
Duration: 18 May 200120 May 2001

Fingerprint

Embedded systems
Software engineering
Industry
Embedded software
Personnel

Keywords

  • reuse
  • domain engineering
  • product line architecture
  • product features
  • quality attributes
  • software engineering

Cite this

Niemelä, Eila ; Ihme, Tuomas. / Product line software engineering of embedded systems. In: ACM SIGSOFT Software Engineering Notes. 2001 ; Vol. 26, No. 3. pp. 118-125.
@article{9bf1e4930a884f0098037471d65db080,
title = "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.",
keywords = "reuse, domain engineering, product line architecture, product features, quality attributes, software engineering",
author = "Eila Niemel{\"a} and Tuomas Ihme",
year = "2001",
doi = "10.1145/375212.375271",
language = "English",
volume = "26",
pages = "118--125",
journal = "ACM SIGSOFT Software Engineering Notes",
issn = "0163-5948",
publisher = "Association for Computing Machinery ACM",
number = "3",

}

Product line software engineering of embedded systems. / Niemelä, Eila; Ihme, Tuomas.

In: ACM SIGSOFT Software Engineering Notes, Vol. 26, No. 3, 2001, p. 118-125.

Research output: Contribution to journalArticleScientificpeer-review

TY - JOUR

T1 - Product line software engineering of embedded systems

AU - Niemelä, Eila

AU - Ihme, Tuomas

PY - 2001

Y1 - 2001

N2 - 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.

AB - 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.

KW - reuse

KW - domain engineering

KW - product line architecture

KW - product features

KW - quality attributes

KW - software engineering

U2 - 10.1145/375212.375271

DO - 10.1145/375212.375271

M3 - Article

VL - 26

SP - 118

EP - 125

JO - ACM SIGSOFT Software Engineering Notes

JF - ACM SIGSOFT Software Engineering Notes

SN - 0163-5948

IS - 3

ER -