Integrated-specifications analysis

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.

[1]  David Harel,et al.  Statecharts: A Visual Formalism for Complex Systems , 1987, Sci. Comput. Program..

[2]  James J. Horning,et al.  The Larch Family of Specification Languages , 1985, IEEE Software.

[3]  Cliff B. Jones,et al.  Specifications are not (necessarily) executable , 1989 .

[4]  Mary K. Vernon,et al.  SARA (System ARchitects Apprentice): Modeling, analysis, and simulation support for design of concurrent systems , 1986, IEEE Transactions on Software Engineering.

[5]  Jan A. Bergstra,et al.  Algebraic specification , 1989 .

[6]  Alan R. Hevner,et al.  Principles of Information Systems Analysis and Design , 1986 .

[7]  Cliff B. Jones,et al.  Case studies in systematic software development , 1990 .

[8]  John E. Odom.  Using Box Structures for Definition of Requirements Specifications , 1990, IBM Syst. J..

[9]  Martín Abadi,et al.  Composing specifications , 1989, TOPL.

[10]  Alan R. Hevner,et al.  Box Structured Information Systems , 1987, IBM Syst. J..

[11]  J. Michael Spivey,et al.  The Z notation - a reference manual , 1992, Prentice Hall International Series in Computer Science.

[12]  Graeme Smith,et al.  The object-Z specification language: version 1 , 1991 .

[13]  James Lyle Peterson,et al.  Petri net theory and the modeling of systems , 1981 .

[14]  Mary Katharine Vernon.  Performance-oriented design of distributed systems , 1983 .

[15]  C. A. R. Hoare,et al.  Communicating sequential processes , 1978, CACM.

[16]  Cliff B. Jones,et al.  Systematic software development using VDM , 1986, Prentice Hall International Series in Computer Science.