Testing Formal Specifications to Detect Design Errors

IEEE Transactions on Software Engineering

Volumn SE-11, Issue 1, 1985, Pages 32-43

  Kemmerer, Richard A ^a  

^a UNIVERSITY OF CALIFORNIA   (United States)

Author keywords

Design and development; formal verification; reliable; requirements; software; specification; testing

Indexed keywords

FORMAL SPECIFICATIONS; SOFTWARE DESIGN;

COMPUTER SOFTWARE;

EID: 0021852765     PISSN: 00985589     EISSN: None     Source Type: Journal    
DOI: 10.1109/TSE.1985.231535     Document Type: Article

References (7)

1. [1] D. I. Good, “The proof of a distributed system in Gypsy,” Inst. Comput. Sci., Univ. Texas at Austin, Austin, TX, Tech. Rep. 30, Sept. 1982.
2. [2] R. Locasso, J. Scheid, V. Schorre, and P. Eggert, The Ina Jo Specification Language Reference Manual, System Development Corp., Santa Monica, CA, SDC document TM-6889/000/01, Nov. 1980.
3. [3] L. Robinson, The HDM Handbook, Vol. I : Foundations of HDM, Comput. Sci. Lab., SRI International, Menlo Park, CA, June, 1979.
4. [4] AFFIRM Reference Manual, D. Thompson and R. Erickson, Eds., Univ. Southern California Information Sciences Inst., Marina Del Rey, CA, Feb. 1981.
5. [4] C. A. R. Hoare, “Proof of correctness of data representations,” Acta Inform., vol. 1, pp. 271–281, 1972.
6. [5] J. Guttag, E. Horowitz, and D. Musser, “Abstract data types and software validation,” Commun. ACM, vol. 21, pp. 1048–1064, Dec. 1978.
7. [7] R. Kemmerer, “Status report on SDC's formal development methodology,” in Proc. 2nd Verification Workshop, Gaithersburg, MD, Apr. 1981.