The previous chapter provides a general discussion of the different stages of specification in the software development process. It was assumed that the discrete steps of the development process have been well-defined. That is, the activities, deliverables, reviews, and analysis procedures associated with each step have already been established. It was suggested that a specification of the products and processes can be added to each step of such a well-defined development process. This chapter addresses specific issues that should be considered, activities that should be initiated, and the roles that are to be assumed when specifications are formal due to the integration of formal methods into the existing software life cycle process for a given project.
KeywordsFormal Method Specification Language Software Development Process Generate Test Case Bibliographic Note
Unable to display preview. Download preview PDF.
- D. Craigen, S. Kromodimoeljo, I. Meisels, B. Pase, and M. Saaltnik, “EVES: An Overview,” VDM’91: Formal Software Development Methods; published as S. Prehn and W.S. Toetenel (Eds.), Lecture Notes in Computer Science, Vol. 551, Springer-Verlag, Noordwijkerhout, The Netherlands, October 1991, pp. 389–405.Google Scholar
- J. Dick and A. Faivre, “Automating the Generation and Sequencing of Test Cases from Model-based Specifications,” FME93: Industrial-Strength Formal Methods, Formal Methods Europe; published as J.C.P. Woodcock and P.G. Larsen (Eds.), Lecture Notes in Computer Science, Vol. 670, Springer-Verlag, April 1993, pp. 268–284.Google Scholar
- R.W. Floyd, “Assigning Meaning to Programs,” Mathematical Aspects of Computer Science, American Mathematical Society, Providence, RI, 1967.Google Scholar
- Formal Methods Specification and Verification Guidebook for Software and Computer Systems: Volume I Planning and Technology Insertion, NASA Report NASA-GB-002–95, Release 1.0, July 1995.Google Scholar
- C.B. Jones, Systematic Software Development Using VDM(second edition), Prentice-Hall International (UK), 1990.Google Scholar
- M. Kapor, “A Software Design Manifesto,” in T. Winograd (Ed.), Bringing Design to Software, ACM Press, New York, NY, 1996, pp. 1–9.Google Scholar
- S. Owre, J.M. Rushby, and N. Shankar, “PVS: A Prototype Verification System,” in D. Kapur (Ed.), Proceedings of the Eleventh International Conference on Automated Deduction (CADE), Saratoga, NY, June 1992; published as Lecture Notes in Artificial Intelligence, Vol. 607, Springer-Verlag, New York, NY, pp. 748–752.Google Scholar
- J. Rumbaugh, M. Blaha, W. Pramerlani, F. Eddy, and W. Lorenson, Object-oriented Modeling and Design, Prentice-Hall, Englewood Cliffs, NJ, 1991.Google Scholar
- T. Winograd, Bringing Design to Software, ACM Press, New York, NY, 1996.Google Scholar