Abstract
The paper addresses the impact of a product line approach to the reliability of embedded systems. After discussing the risks, we identify two measures which are desirable for a reliability-oriented application of the product line technology: First, an evaluation method which makes it possible to predict the reliability of design alternatives during the architecting phase and, second, analysis and design guidelines for a systematic analysis and architectural realization of domain-specific reliability requirements. For both of these issues, a methodical solution is proposed and discussed.
There are more specific definitions of reliability (cf. [10]) but this one suffices for our purposes.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
L. Bass, P. Clements, and R. Kazman. Software Architecture in Practice. Addison-Wesley, 1998.
J. Bosch and P. Molin. Software architecture design: Evaluation and transformation. In Proceedings of the 1999 IEEE Engineering of Computer Based Systems Symposium (ECBS99), December 1999.
B. P. Douglass. Doing Hard Time: Developing Real-time Systems with UML, Objects, Frameworks, and Patterns. Object Technology Series. Addison-Wesley, 1999.
N. E. Fenton. A critique of software defect prediction models. IEEE Transactions on Software Engineering, 25(3):675–689, May/June 1999.
IEC. International Standard 812: Analysis techniques for dependability-procedure for Failure Mode and Effect Analysis (FMEA).International Electrotechnical Commission, Geneva, 1985.
IEC. International Standard 61025: Fault Tree Analysis (FTA). International Electrotechnical Commission, Geneva, 1990.
IEC. International Standard 61078: Analysis techniques for dependability-Reliability Block Diagram method. International Electrotechnical Commission, Geneva, 1991.
Rick Kazman, Len Bass, Gregory Abowd, and Paul Clements. Scenario-based analysis of software architecture. IEEE Software, 13(6):47–45, November 1996.
Rick Kazman, Mark Klein, and Paul Clements. ATAM: Method for architecture evaluation. Technical Report CMU/SEI-2000-TR-004, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, USA, August 2000.
J.-C. Laprie and K. Kanoun. Software reliability and system reliability. In M.R. Lyu, editor, Handbook of Software Reliability Engineering. McGraw-Hill, New York, 1995.
B. Randell. Systems structure for software fault tolerance. IEEE Transactions on Software Engineering, l(2):220–232, June 1975.
J. Weber and S. Kowalewski. Specification of subsystems and components in IT-based automotive electronics. In Proc. 7th Intern. Conference Associazione Tecnica dell’Automobile (ATA’01), Florence, 23–25 May 2001, 2001. CD-ROM.
Jianjun Zhao. On assessing the complexity of software architectures. In Proc. 3rd Int. Software Architecture Workshop (ISAW3), ACM SIGSOFT, pages 163–166. ACM Press, November 1998.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2002 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Auerswald, M., Herrmann, M., Kowalewski, S., Schulte-Coerne, V. (2002). Reliability-Oriented Product Line Engineering of Embedded Systems. In: van der Linden, F. (eds) Software Product-Family Engineering. PFE 2001. Lecture Notes in Computer Science, vol 2290. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-47833-7_10
Download citation
DOI: https://doi.org/10.1007/3-540-47833-7_10
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-43659-1
Online ISBN: 978-3-540-47833-1
eBook Packages: Springer Book Archive