Abstract
In this paper we begin by examining the “certification” of a consumer product, a baby walker, that is product-focused, i.e., the certification process requires the performance of precisely defined tests on the product with measurable outcomes. We then review current practices in software certification and contrast the software regime’s process-oriented approach to certification with the product-oriented approach typically used in other engineering disciplines. We make the case that product-focused certification is required to produce reliable software intensive systems. These techniques will have to be domain and even product specific to succeed.
Supported by the Natural Sciences and Engineering Research Council of Canada.
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.
References
ASTM Standard F977: Standard Consumer Safety Specification for Infant Walkers. ASTM International, West Conshohocken, PA, USA (2000)
Regulatory Review and Recommendation Regarding Baby Walkers Pursuant to the Hazardous Products Act. Health Canada (April 2004)
General Principles of Software Validation; Final Guidance for Industry and FDA Staff. U.S. Dept. of Health and Human Services: FDA (January 2002)
Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices; Guidance for Industry and FDA staff. U.S. Dept. of Health and Human Services: FDA (May 2005)
http://www.sei.cmu.edu/cmmi/ (March 2009)
Common Criteria for Information Technology Security Evaluation: Part 1: Introduction and general model, Version 3.1, Revision 1 (2006)
Common Criteria for Information Technology Security Evaluation: Evaluation methodology, Version 3.1, Revision 2 (2007)
Parnas, D.: The use of precise specifications in the development of software. In: IFIP Congress, pp. 861–867 (1977)
Heninger, K.L.: Specifying software requirements for complex systems: New techniques and their applications. IEEE Trans. on Soft. Engineering 6(1), 2–13 (1980)
Parnas, D.: Using Mathematical Models in the Inspection of Critical Software. In: Applications of Formal Methods, pp. 17–31. Prentice-Hall, Englewood Cliffs (1995)
Leveson, N.G., Heimdahl, M.P.E., Hildreth, H., Reese, J.D.: Requirements specification for process-control systems. IEEE Transactions on Software Engineering 20(9), 684–707 (1994)
Heimdahl, M.P.E., Leveson, N.G.: Completeness and consistency in hierarchical state-based requirements. IEEE Trans. on Soft. Eng. 22(6), 363–377 (1996)
Heitmeyer, C., Kirby Jr., J., Labaw, B., Archer, M., Bharadwaj, R.: Using abstraction and model checking to detect safety violations in requirements specifications. IEEE Transactions on Software Engineering 24(11), 927–948 (1998)
Crow, J., Di Vito, B.L.: Formalizing Space Shuttle software requirements: Four case studies. ACM Trans. on Soft. Eng. and Methodology 7(3), 296–332 (1998)
Archinoff, G.H., Hohendorf, R.J., Wassyng, A., Quigley, B., Borsch, M.R.: Verification of the shutdown system software at the Darlington nuclear generating station. In: International Conference on Control and Instrumentation in Nuclear Installations, Glasgow, UK, The Institution of Nuclear Engineers (May 1990)
Parnas, D.L., Asmis, G.J.K., Madey, J.: Assessment of safety-critical software in nuclear power plants. Nuclear Safety 32(2), 189–198 (1991)
Wassyng, A., Lawford, M.: Lessons learned from a successful implementation of formal methods in an industrial project. In: Araki, K., Gnesi, S., Mandrioli, D. (eds.) FME 2003. LNCS, vol. 2805, pp. 133–153. Springer, Heidelberg (2003)
Joannou, P., et al.: Standard for Software Engineering of Safety Critical Software. CANDU Computer Systems Engineering Centre of Excellence Standard CE-1001-STD Rev. 1 (January 1995)
Janicki, R., Wassyng, A.: Tabular representations in relational documents. Fundamenta Informaticae 68, 1–28 (2005)
Wassyng, A., Lawford, M.: Software tools for safety-critical software development. Software Tools for Technology Transfer (STTT) 8(4-5), 337–354 (2006)
McDougall, J., Viola, M., Moum, G.: Tabular representation of mathematical functions for the specification and verification of safety critical software. In: SAFECOMP 1994, pp. 21–30. Instrument Society of America, Anaheim (1994)
Wassyng, A., et al.: Choosing a methodology for developing system requirements. Ontario Hydro/AECL SD-2 Study Report (November 1990)
Easterbrook, S., Lutz, R., Covington, R., Kelly, J., Ampo, Y., Hamilton, D.: Experiences using lightweight formal methods for requirements modeling. IEEE Transactions on Software Engineering 24(1), 4–14 (1998)
Heitmeyer, C., Kirby, J., Labaw, B., Bharadwaj, R.: SCR*: A toolset for specifying and analyzing software requirements. In: Y. Vardi, M. (ed.) CAV 1998. LNCS, vol. 1427, pp. 526–531. Springer, Heidelberg (1998)
Shankar, N., Owre, S., Rushby, J.M.: PVS Tutorial. In: Computer Science Laboratory, SRI International, Menlo Park, CA (February 1993)
Rueß, H., Shankar, N., Srivas, M.K.: Modular verification of SRT division. Formal Methods in Systems Design 14(1), 45–73 (1999)
Parnas, D., Clements, P.: A rational design process: How and why to fake it. IEEE Trans. Software Engineering 12(2), 251–257 (1986)
Koen, B.: Definition of the Engineering Method. ASEE (1985)
Haeberer, A.M., Maibaum, T.S.E.: Scientific rigour, an answer to a pragmatic question: A linguistic framework for software engineering. In: ICSE 2001 Proceedings, pp. 463–472. IEEE Computer Society, Washington (2001)
Maibaum, T.: Mathematical foundations of software engineering: a roadmap. In: ICSE 2000 Proceedings, pp. 161–172. ACM, New York (2000)
Maibaum, T.: Knowing what requirements specifications specify. In: PRISE 2004, Conference on the PRInciples of Software Engineering, Technical Report, University of Buenos aires, keynote address in memory of Armando Haeberer (2004)
Vincenti, W.G.: What Engineers Know and How They Know It: Analytical Studies from Aeronautical History. The Johns Hopkins University Press, Baltimore (1993)
Carnap, R.: Empiricism, semantics, and ontology. Revue Internationale de Philosophie 11, 208–228 (1950)
Carnap, R.: The Methodological Character of Theoretical Concepts. In: Minnesota Studies in the Philosophy of Science, vol. II, pp. 33–76. U. of Minnesota Press (1956)
Carnap, R.: Introduction to the Philosophy of Science. Dover Publications, New York (1995)
Rogers, G.: The Nature of Engineering. The Macmillan Press Ltd., Basingstoke (1983)
Hempel, C.: Aspects of Scientific Explanation and Other Essays in the Philosophy of Science. The Free Press, New York (1965)
Hatcliff, J., Heimdahl, M., Lawford, M., Maibaum, T., Wassyng, A., Wurden, F.: A software certification consortium and its top 9 hurdles. In: Proceedings of SafeCert 2008. ENTCS (2008) (to appear)
Arney, D., Jetley, R., Jones, P., Lee, I., Sokolsky, O.: Formal methods based development of a PCA infusion pump reference model: Generic infusion pump (GIP) project, pp. 23–33 (June 2007)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2010 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Wassyng, A., Maibaum, T., Lawford, M. (2010). On Software Certification: We Need Product-Focused Approaches. In: Choppy, C., Sokolsky, O. (eds) Foundations of Computer Software. Future Trends and Techniques for Development. Monterey Workshop 2008. Lecture Notes in Computer Science, vol 6028. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-12566-9_13
Download citation
DOI: https://doi.org/10.1007/978-3-642-12566-9_13
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-12565-2
Online ISBN: 978-3-642-12566-9
eBook Packages: Computer ScienceComputer Science (R0)