Skip to main content
SpringerLink
Log in

Design Guidelines for Reliability, Maintainability, and Software Quality

  • Chapter
Reliability Engineering

  • 509 Accesses

Abstract

Reliability, maintainability, and software quality have to be built into complex equipment and system during the design and development phase. This has to be supported by analytical investigations (Chapters 2, 4, and 6) as well as by design guidelines. Adherence to such guidelines limits the influence of those aspects which can invalidate the models assumed for analytical investigations, and contributes greatly to build in reliability, maintainability, and software quality. This chapter gives a comprehensive list of design guidelines for reliability, maintainability, and software quality of complex equipment and systems, harmonized with industry’s needs [1.2 (1996)].

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Log in via an institution

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 74.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

Design Guidelines for Reliability

  1. Boxleitner W., “Electrostatic Discharge” in Electronic Equip., 1989, IEEE Press, Piscataway NJ. [5.2] Catrysse J., “PCB system design under EMC constraints”, Proc. 11th Int. Zurich EMC Symposium, 1995, pp. 47–58.

    Google Scholar 

  2. Deutsch A., “Electrical characteristics of interconnections for high-performance systems”, Proc. IEEE,86(1998)2, pp. 315–355.

    Google Scholar 

  3. Gallo A.A., Munamarty R., “Popcorning: A failure mechanism in plastic-encapsulated microcircuits”, IEEE Trans. Rel.,44(1995)3, pp. 362–67.

    Google Scholar 

  4. Gardner J.R., “The appropriateness of plastic encapsulated microcircuits in a specific wooden-round application”, IEEE Trans. Rel.,45(1996)1, pp. 10–17.

    Google Scholar 

  5. Goedbloed J.J., Electromagnetic Compatibility, 1992, Prentice Hall, New York.

    Google Scholar 

  6. Haseloff E., Was nicht im Datenblatt steht,1992, Appl.-Bericht EB 192, Texas Instruments, Freising, “Entwicklungsrichtlinien für schnelle Logikschaltungen und Systemen”, Proc. ETH/IEEE Conf. on Design Rules for Rel., EMC, Maint., Soft. Qual.,1993, ETH Zurich, Rel. Lab., pp. 5.1–17.

    Google Scholar 

  7. Hellström S., ESD-The Scourge of Electronics, 1998, Springer, Berlin.

    Book  Google Scholar 

  8. Hirschi W., “EMV gerechte Auslegung elektron. Geräte”, Bull. SEV/VSE,83(1992)11, pp. 25–29. [5.10] IEEE Trans. Rel. Special issue on: Design for reliability, 40(1991)3 and 44(1995)2, Plastic encaps. microcircuits, 42(1993)4.

    Google Scholar 

  9. IEEE Std 1100–1992: IEEE Recom. Practice for Powering and Grounding Sensitive El. Equip. [5.12] Mannone P., “ Careful design methods to prevent CMOS latch-up”, EDN,Jan. 26, 1984, 6 pp. [5.13] MIL-HDBK-338: Electronic Reliability Design Handbook,Vol. I Ed. A 1988, Vol. II 1984. [5.14] IPC, ANSIIIPC-SM-782: Surface Mount Land Patterns (Config. and Design Rules),1987.

    Google Scholar 

  10. Pecht M.G., Palmer M., Naft J., “Thermal reliability management in PCB design”, Proc. Ann. Rel. Maint. Symp., 1987, pp. 312–315.

    Google Scholar 

  11. RAC, SOAR-6: ESD Control in the Manuf. Envir, 1986, TR-82–172: Thermal Guide for Rel. Eng., 1982, VZAP: ESD Susceptibility Data, 1991.

    Google Scholar 

  12. Sergent J., Krum Al, Thermal Management Handbook, 1998, McGraw-Hill, New York.

    Google Scholar 

  13. Solberg V., Design Guidelines for Surface Mount and Fine Pitch Technology, 1996, McGraw-Hill, New York.

    Google Scholar 

  14. Vinson J.E., Liou J.J., “Electrostatic discharge in semiconductor devices: Protection techniques”, Proc. IEEE,88(2000)12, pp. 1878–1900.

    Google Scholar 

  15. White D.R.J., EMI Control in the Design of Printed Circuit Boards and Backplanes, 1982, Interf. Control Tech., Gainesville VI.

    Google Scholar 

Design Guidelines for Maintainability

  1. Abramovici M. et al., Digital System Testing and Testable Design, 1990, Computer Scient. Press, New York.

    Google Scholar 

  2. Bennetts R.G., Design of Testable Logic Circuits, 1984, Addison-Wesley, London.

    Google Scholar 

  3. Benso A. et al, “An on-line BIST RAM architecture with self-repair capabilities”, IEEE Trans. Rel.,51(2002)1, pp. 123–128.

    Google Scholar 

  4. DoD, AMCP-706–132: Engineering Design Handbook - Maintenance Engineering Tech., 1975, -133: Engineering Design Handbook - Maintainability Eng. Theory and Practice, 1975.

    Google Scholar 

  5. Lala P.K., Fault Tolerant Fault Testable Hardware Design,1985, Prentice-Hall, Engl. Cliffs NJ. [5.26] Maunder C., The Board Designer’s Guide to Testable Logic Circuits, 1992,Addison-Wesley, Read. MA, A universal framework for manag. Built-In Test, Proc. Int. Test Conf,Paris 1995, 8 pp.

    Google Scholar 

  6. Richards D.W., Klion J., “Smart BIT–an approach to better system-level built-in test”, Proc. Ann. Rel. Maint. Symp., 1987, pp. 31–34.

    Google Scholar 

  7. Robinson G., Deshayes J., “Interconnect testing of boards with partial boundary-scan”, Proc. Int. Test Conf,1990, paper 27.3.

    Google Scholar 

  8. Smith D.J. and Babb A.H., Maintainability Engineering, 1973, Pitman, London.

    Google Scholar 

  9. Ye N., “The presentation of knowledge and state-information for system fault diagnosis”, IEEE Trans. Rel.,45(1996)4, pp. 638–645.

    Google Scholar 

Software Quality

  1. ACM Special issues on: Software Testing, Commun. of the ACM,31(1988)6, Software Quality, Commun. of the ACM,36(1993)11.

    Google Scholar 

  2. Aggarwal K.K. et al., “An integrated measure of software maintainability”, Proc. Ann. Rel. Maint. Symp., 2002, pp. 235–241.

    Google Scholar 

  3. Arlat J., Karama K., Laprie J.C., “Dependability modeling and evaluation of software fault-tolerant systems”, IEEE Trans. Comp.,39(1990)4, pp. 504–513.

    Google Scholar 

  4. Avresky D. et al, “Fault injection for formal testing of fault tolerance”, IEEE Trans. Rel.,45(1996)3, pp. 443–455.

    Google Scholar 

  5. Braude E.J., (Ed.), Software Engineering: Selected Readings,2000, IEEE Press, Piscataway NJ. [5.36] Brocklehurst S. et al., “Recalibrating software reliability models”, IEEE Trans. Soft. Eng.,16(1990)4, pp. 458–469.

    Google Scholar 

  6. BWB, Software-Entwicklungsstandard der BWB - Vorgehensmodell,1991.

    Google Scholar 

  7. Chen M-H, et al., “Effect of testing techniques on software rel. estimates using a time domain model”, IEEE Trans. Rel.,44(1995)1, pp. 97–103.

    Google Scholar 

  8. Chillareg R., “What is software failure?”, IEEE Trans. Rel.,45(1996)3, pp. 354–355.

    Google Scholar 

  9. ESA PSS-05–04: Guide to the Software Architect,1992, -05: Detailed Design and Prod.,1992, -08: Project Management,1994, -09: Configuration Manag.,1992, -11: Quality Assurance,1993.

    Google Scholar 

  10. Fakhre-Zakeri I., Slud E., “Mixture models for reliability of software with imperfect debugging”, IEEE Trans. Rel.,44(1995)1, pp. 104–113.

    Google Scholar 

  11. Deconick G. et al., “The EFTOS approach to dependability in embedded supercomputing”, IEEE Trans. Rel.,51(2002)1, pp. 76–90.

    Google Scholar 

  12. Deriennic H., Le Gall G., “Use of failure-intensity models in the software-validation phase for telecommunications”, IEEE Trans. Rel.,44(1995)4, pp. 658–665.

    Google Scholar 

  13. Fenton N., Littlewood B., Software Reliability and Metries, 1991, Elsevier, London.

    Google Scholar 

  14. Grady R.,“Practical results from measur. soft. quality”, Commun. of the ACM,36(1993) t 1,pp.62–68. [5.46] Hagwood C., et al., “Reliability of conformance tests”, IEEE Trans. Rel.,50(2001)2, pp. 204–208. [5.47] Herrmann D.S., Peercy D.E., “The bridge between hardware, software, and system safety and reliability”, Proc. Ann. Rel. Maint. Symp.,1999, pp. 396–402.

    Google Scholar 

  15. Hou R-H, et al., “Optimal release policy for hypergeometric distribution software-reliability growth model”, IEEE Trans. Rel.,45(1996)4, pp. 646–651.

    Google Scholar 

  16. Huang C-Y, Kuo S-Y., “Analysis of incorporating logistic testing-effort function into software reliability modeling”, IEEE Trans. Rel.,51(2002)3, pp. 261–270.

    Google Scholar 

  17. IEC 60300–3–6 (1997): Depend. Manag. – Software Aspects of Dependability, 61713 (2000): Software Depend. through the Software Life–Cycle Process – Appl. Guide, IEC/ISO 12207 (1995): Inf. Tech. – Software Life–Cycle Proc., 12227 (1995): Inf. Technol. – Software Progr. Languages.

    Google Scholar 

  18. IEEE Trans. Rel. Special issue on: Fault-tolerant software, 42(1993)2, Software reliability engineering, 43(1994)4, 45(1996)4, 49(2000)1. See also [A2.8].

    Google Scholar 

  19. Keene S.J. et al.,“Developing reliable software”, Proc. Ann. Rel. Maint. Symp.,1996, pp.143–46. [5.53] Kline M.B., “Software and Hardware RM - what are the differences?”, Proc. Ann. Rel. Maint. Symp.,1980, pp. 179–184.

    Google Scholar 

  20. Kumar R. et al., “Neural-network techniques for software-quality evaluation”, Proc. Ann. Rel. Maint. Symp., 1998, pp. 155–160.

    Google Scholar 

  21. Lanning D.L., Khoshgoftaar T.M., “Fault severity in models of fault-correction activity”, “An empirical model of enhancement-induced defect activity in software”, “The impact of software enhancement on software reliability”, IEEE Trans. Rel.,44(1995)4, pp. 666–682.

    Google Scholar 

  22. Le Traon Y. et al., “Efficient object-oriented integration and regression testing”, IEEE Trans. Rel.,49(2000)1, pp. 12–25.

    Google Scholar 

  23. Leveson N.G.,, “Software safety in computer-controlled systems”, Computer,(1984)2, pp. 48–55, “Software safety: why, what, and how”, ACM Computing Surveys,18(1986)2, pp. 125–163.

    Google Scholar 

  24. Littlewood B., Strigini L., “The risk of software”. Scient. Amer., 1992, pp. 38–43, “Validation of ultrahigh dependability for software-based syst”, Commun. of the ACM, 36(1993)11, pp. 69–80, L.ttlewood B., “Evaluation of software reliability - achievements and limitations”, Proc. ETH/IEEE Int. Symp. on Rel. Eng. 2’000, ETH Zurich, Rel. Lab., Oct. 17, 1996, 22 pp.

    Google Scholar 

  25. Lloyd C. et al., “Estimating the number of faults: Efficiency of removal, recapture, and seeding”, IEEE Trans. Rel.,48(1999)4, pp. 369–376.

    Google Scholar 

  26. Musa J.D., lannino A., Okumoto K., Software Reliability: Measurement, Prediction, Application,1987, McGraw-Hill, New York, Musa J.D., “An overview of software rel. engineering” and “The operational profile”, in Özekici S., Ed.: Reliability and Maintenance of Complex Systems,1996, Springer, Berlin, pp. 319–332 and 333–344.

    Google Scholar 

  27. Oh N. et al.,“Control-flow checking by softw. signatures”, IEEE Trans. Rel.,51(2002)1, pp.111–22. [5.62] Parnas D.L et al., “Evaluation of safety-critical software”, Commun. of the ACM,33(1990)6, pp. 636–48.

    Google Scholar 

  28. Pflegger S.L., “Measuring software reliability”, IEEE Spectrum, Aug. 1992, pp. 56–60.

    Google Scholar 

  29. Reifer D.J., Software Failure Modes and Effects Anal.“, IEEE Trans. Rel.,28(1979)3, pp. 247–49.

    Google Scholar 

  30. SAQ, 10300: Software Qualitätssich. and CASE,1995, 10301: HDBK Beschaffung von Software, 1996, 10302: HDBK für Audits im Soft.-Bereich, 1996, 10303: Grundlagen zum Umgang mit Software Problemen,1997.

    Google Scholar 

  31. Schneidewind N.F., “Reliability modeling for safety-critical software”, IEEE Trans. Rel.,46(1997)1, pp. 88–98.

    Google Scholar 

  32. Singpurwalla N.D., “The failure rate of software: does it exist?”, IEEE Trans. Rel., 44(1995)3, pp. 463–69, -, Soyer R., “Assessing the reliability of software: An overview”, in Ozekici S., Ed.: Reliability and Maintenance of Complex Systems, 1996, Springer, Berlin, pp. 345–367.

    Google Scholar 

  33. Stankovic J.A., “A serious problem for next-generation system”, Computer,21(1988)10, pp. 10–19. [5.69] Teng X., Pham H., “A software-reliability growth model for n-version programming systems”, IEEE Trans. Rel.,51(2002)3, pp. 311–321.

    Google Scholar 

  34. Wallace D. et al, “An analysis of selected software safety Std.”, IEEE AES Mag., 1992, pp. 3–14.

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Arrigo-Mosciano, I-50018, Scandicci (FI), Tuscany, Italy

    Prof. Dr. Alessandro Birolini (Ingénieur et penseur, PhD, Professor Emeritus of Reliability Engineering)

  2. Swiss Federal Institute of Technology, Zürich, Switzerland

    Prof. Dr. Alessandro Birolini (Ingénieur et penseur, PhD, Professor Emeritus of Reliability Engineering)

Authors
  1. Prof. Dr. Alessandro Birolini
    View author publications

    You can also search for this author in PubMed Google Scholar

Rights and permissions

Reprints and permissions

Copyright information

© 2004 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Birolini, A. (2004). Design Guidelines for Reliability, Maintainability, and Software Quality. In: Reliability Engineering. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-662-05409-3_5

Download citation

  • DOI: https://doi.org/10.1007/978-3-662-05409-3_5

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-662-05411-6

  • Online ISBN: 978-3-662-05409-3

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics

Search

Navigation