The introduction of a software product line may pose a great organizational challenge in the domain of high- integrity systems. Project and technical managers within an organization need to be assured that the reusable assets of a product line are reliable and trustworthy, particularly when project teams do not have full control over the development of these assets. In this paper we report on our experience with the establishment of a software product line for an aerospace Engine Monitoring Unit (EMU). Specifically, we report on challenges encountered with the configuration management and certification of EMU products derived from the product line. These two areas are still to be addressed adequately by the product line community as they are central for the management of product line assets across different projects within an organization.
[1]
Nancy G. Leveson,et al.
Safeware: System Safety and Computers
,
1995
.
[2]
R. Bell,et al.
IEC 61508: functional safety of electrical/electronic/ programme electronic safety-related systems: overview
,
1999
.
[3]
Irem Y. Tumer,et al.
A SURVEY OF AIRCRAFT ENGINE HEALTH MONITORING SYSTEMS
,
1999
.
[4]
Felix Redmill.
Safety Integrity Levels — theory and problems
,
2000
.
[5]
Paul Clements,et al.
Software product lines - practices and patterns
,
2001,
SEI series in software engineering.
[6]
Nancy G. Leveson,et al.
Making embedded software reuse practical and safe
,
2004,
SIGSOFT '04/FSE-12.