One of the remaining challenges in product line engineering is how to establish the quality of the reusable assets so that we can be confident that they can be configured and composed reliably. This is desirable, both to avoid having to completely re-test each product and to avoid integration faults only being detected late in product development. One of the diversity mechanisms of Philips’ high-end TV product line is the selection and com position of sub-systems, so different sub-system variants must integrate reli ably if the aims of the product line are to be realized. An earlier study of in tegration testing obligations in Philips products concluded that certain design policies must be imposed if integration testing is to be feasible, but it did not describe how relevant policies could be identified at the earliest stages of de sign. This paper addresses how a set of architectural rules were established for the TV product line through a root-cause analysis of problem reports, and packaged so that developers can recognize when they should be applied. The approach builds on other work on the impact of design choices on non-func-tional requirements to ensure that all quality attributes are addressed.
[1]
Santiago Comella-Dorda,et al.
Volume II: Technical Concepts of Component-Based Software Engineering
,
2000
.
[2]
H. B. M. Jonkers.
ISpec: Towards Practical and Sound Interface Specifications
,
2000,
IFM.
[3]
Alan Burns,et al.
Guide for the use of the Ada Ravenscar Profile in high integrity systems
,
2004,
ALET.
[4]
Ivica Crnkovic,et al.
Building Reliable Component-Based Software Systems
,
2002
.
[5]
Daniel Gross,et al.
From Non-Functional Requirements to Design through Patterns
,
2001,
Requirements Engineering.