Formal specifications of software hold the promise to eliminate ambiguity from requirements and enable formal analysis of specifications, by introducing mathematical formalism from the outset of the lifecycle. However, these formalisms are geared towards functional specifications ignoring the user interface.
Unable to display preview. Download preview PDF.
- Roger Duke, Paul King, Gordon Rose, and Graeme Smith. The Object-Z Specification Language, Version 1. Technical Report No. 91-1, Software Verification Research Centre, The University of Queensland, Queensland 4072, Australia.Google Scholar
- Hartmut Ehrig. Martin Große-Rhode and Andreas Heise. Specification techniques for concurrent and distributed systems. Technical Report, Bericht-Nr. 92/5, Technische Universität Berlin, Fachbereich 20, Informatik, Franklinstaße 28/29, D-1000 Berlin 10, Germany, 1992.Google Scholar
- Gerald Estrin et al. SARA (system architects apprentice): Modeling, analysis, and simulation support for design of concurrent systems. IEEE Transactions on Software Engineering, SE-(12)2, February, 1986.Google Scholar
- Yadran Eterovic. Executable Specifications of Multi-application Multi-user Interlaces. Ph.D. Thesis. University of California, Los Angeles, Computer Science Department, July, 1992.Google Scholar
- John V. Guttag, James J. Horning, and Jeanette M. Wing. The Larch family of specification languages. IEEE Software, pp. 24-36, September, 1985.Google Scholar
- I.J. Hayes and C.B. Jones. Specifications are not (necessarily) executable. Software Engineering Journal, pages 330-338, November 1989.Google Scholar
- Lynn S. Marshall. Formally describing interactive systems. In Cliff B. Jones and R.C. Shaw, Eds., Case Studies in Systematic Software Development. Series in Computer Science. Prentice-Hall International, London, 1990.Google Scholar
- H.D Mills, R.C. Linger and A.R. Ilevner. Principles of Information systems Analysis and Design. Academic Press, San Diego, 1986.Google Scholar
- H.D Mills, R.C. Linger and A.R. Hevner. Box structured information systems. IBM Systems Journal, (26)4, 1987.Google Scholar
- J.E. Odom. Using box structures for definition of requirements specifications. IBM Systems Journal, (29)1, 1990.Google Scholar
- James L. Peterson. Petri Net Theory and the Modeling of Systems. Prentice-Hall, Englewood Cliffs, N.J., 1981.Google Scholar
- J.M. Spivey. The Z Notation: A Reference Manual. Second Edition. Series in Computer Science. Prentice-Hall International, New York, 1992.Google Scholar
- Pablo A. Straub and Hugo A. Espinoza. Integrating the Graph Model of Behavior and Z. Technical Report, Department of Computer Science, Catholic University of Chile, P.O. Box, Santiago 22, Chile, September 1993.Google Scholar
- Mary Katharine Vernon. Performance-Oriented Design of Distributed Systems Technical Report, Computer Science Department, Los Angeles, University of California, August, 1983.Google Scholar