Abstract
For the purposes of this paper, software verification can be defined as the methods used to ensure that a program meets its specifications and that the documentation correctly represents both program and specification. From the definition, it is obvious that it is impossible to do verification without a specification. This may seem like a simple point, but it is surprising the number of projects I have seen where there was no written specification of what the program was supposed to do. Let there be no confusion. If you do not have a precise, written specification of what the program is supposed to do, it is impossible to verify program operation.
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
Miller, G.A., “The Magical Number Seven”. Psychological Review 63, (1956).
Brooks, F.P., The Mythical Man Month. Addison Wesley, Reading, Mass. (1975). See also Datamation (1974), 45–52.
Shooman, M.L. and Bolsky, M.L., “Types, Distribution, and Test and Correction Times for Programming Errors”. SIGPLAN Notices 10, 6, (June 1975), 347–357.
Caine, S.H. and Gordon, E.K., “PDL — A Tool for Software Design”. Proc. 1975 NCC. AFIPS Press, Montvale, N.J., 271–276.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 1976 Springer-Verlag New York Inc.
About this chapter
Cite this chapter
Bredt, T.H. (1976). What the Software Engineer should Know about Program Verification. In: Wasserman, A.I., Freeman, P. (eds) Software Engineering Education. Springer, New York, NY. https://doi.org/10.1007/978-1-4612-9898-4_7
Download citation
DOI: https://doi.org/10.1007/978-1-4612-9898-4_7
Publisher Name: Springer, New York, NY
Print ISBN: 978-0-387-90216-6
Online ISBN: 978-1-4612-9898-4
eBook Packages: Springer Book Archive