Completeness, robustness, and safety in real-time software requirements specification

This paper presents an approach to providing a rigorous basis for ascertaining whether or not a given set of software requirements is internally complete, i.e., closed with respect to questions and inferences that can be made on the basis of information included in the specification. Emphasis is placed on aspects of software requirements specifications that previously have not been adequately handled, including timing abstractions, safety, and robustness.

[1]  Robert Balzer,et al.  On the inevitable intertwining of specification and implementation , 1982, CACM.

[2]  Aloysius K. Mok,et al.  Safety analysis of timing properties in real-time systems , 1986, IEEE Transactions on Software Engineering.

[3]  Hermann Kopetz,et al.  Clock Synchronization in Distributed Real-Time Systems , 1987, IEEE Transactions on Computers.

[4]  Nancy G. Leveson,et al.  Safety Analysis Using Petri Nets , 1987, IEEE Transactions on Software Engineering.

[5]  Barry W. Boehm,et al.  Some experience with automated aids to the design of large-scale reliable software , 1975, IEEE Transactions on Software Engineering.

[6]  C. V. Ramamoorthy,et al.  Software requirements and specifications: status and perspectives , 1978 .

[7]  Peter G. Neumann,et al.  Some Computer-Related Disasters and Other Egregious Horrors , 1986, IEEE Aerospace and Electronic Systems Magazine.

[8]  Nancy G. Leveson,et al.  Analyzing Software Safety , 1983, IEEE Transactions on Software Engineering.

[9]  M.S. Jaffe,et al.  Completeness, Robustness, And Safety In Real-time Software Requirements Specification , 1989, 11th International Conference on Software Engineering.

[10]  David Lorge Parnas,et al.  A rational design process: How and why to fake it , 1986, IEEE Transactions on Software Engineering.

[11]  James D. Foley,et al.  Fundamentals of interactive computer graphics , 1982 .

[12]  Gruia-Catalin Roman,et al.  A taxonomy of current issues in requirements engineering , 1985, Computer.

[13]  Nancy G Leveson,et al.  Software safety: why, what, and how , 1986, CSUR.