This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Software Requirements Analysis for Real-Time Process-Control Systems
March 1991 (vol. 17 no. 3)
pp. 241-258

A set of criteria is defined to help find errors in, software requirements specifications. Only analysis criteria that examine the behavioral description of the computer are considered. The behavior of the software is described in terms of observable phenomena external to the software. Particular attention is focused on the properties of robustness and lack of ambiguity. The criteria are defined using an abstract state-machine model for generality. Using these criteria, analysis procedures can be defined for particular state-machine modeling languages to provide semantic analysis of real-time process-control software requirements.

[1] New York Times(Science Times Section), July 29, 1986.
[2] M. W. Alford, "A requirements engineering methodology for real-time processing requirements,"IEEE Trans. Software Eng., vol. SE- 3, no. 1, pp. 60-68, Jan. 1977.
[3] D. Bahn, "Reliance on computers," inProc. Forum Risks to the Public in Computer Systems, P. G. Neumann, moderator, ACM Committee Computers and Public Policy, vol. 6, issue 40, Mar. 9, 1988.
[4] R. M. Balzer, D. Cohen, M. S. Feather, N. M. Goldman, W. Swartout, and D.S. Wile, "Operational specification as the basis for specification validation," inTheory and Practice of Software Technology, D. Ferrari, M. Bolognani, and J. Goguen, Eds. Amsterdam, The Netherlands: North-Holland, 1983, pp. 21-49.
[5] B. W. Boehm, R. L. McClean, and D. B. Urfig, "Some experiences with automated aids to the design of large-scale reliable software,"IEEE Trans. Software Eng., vol. SE-1, no. 2, Feb. 1975.
[6] B. W. Boehm,Software Engineering Economics. Englewood Cliffs, NJ: Prentice-Hall, 1981.
[7] F. Cristian, "Correct and robust programs,"IEEE Trans. Software Eng., vol. SE-10, no. 2, pp. 163-174, Mar. 1984.
[8] A. Endres, "An analysis of errors and their causes in system programs,"IEEE Trans. Software Eng., vol. SE-1, no. 6, pp. 140-149, June 1975.
[9] J.D. Foley and A. Van Dam,Fundamentals of Interactive Computer Graphics(The System Programming Series). Reading, MA: Addison-Wesley, 1982.
[10] F.R. Frola and C.O. Miller, "System safety in aircraft management," Logistics Management Inst., Washington, DC, Tech. Rep., Jan. 1984.
[11] D. Harel, "Statecharts: A visual formalism for complex systems,"Sci. Comput. Program., vol. 8, pp. 231-274, 1987.
[12] K.L. Heninger, "Specifying software requirements for complex systems: New techniques and their applications,"IEEE Trans. Software Eng., vol. SE-6, no. 1, pp. 2-12, Jan. 1980.
[13] J. E. Hopcroft and J. D. Ullman,Introduction to Automata Theory, Languages, and Computation. Reading, MA: Addison-Wesley, 1979.
[14] M. S. Jaffe, "Completeness, robustness, and safety in real-time software requirements and specifications," Ph.D. dissertation, Univ. California, Irvine, 1988.
[15] F. Jahanian and A. K. Mok, "A graph-theoretic approach for timing analysis and its implementation,"IEEE Trans. Comput., vol. 36, pp. 961-975, Aug. 1987.
[16] T. Kletz, "Wise after the event,"Contr. Instrum., vol. 20, no. 10, Oct. 1988.
[17] H. Kopetz and A. Damm, "MARS: Concepts and design of the second prototype," Tech. Univ. Vienna, Austria, Tech. Rep. 4/87, Jan. 1987.
[18] H. Kopetz and W. Merker, "The architecture of Mars," inProc. Int. Symp. Fault Tolerant Computing Systems, June 1985, pp. 274-279.
[19] J. Lamb, "The everyday risks of playing it safe,"New Scientist, Sept. 8, 1988.
[20] Leveson, N.G., "Software Safety: What, Why, and How,"ACM Computing Surveys, Vol. 18, No. 2, June 1986, pp. 125-163.
[21] N.G. Leveson and J.L. Stolzy, "Safety analysis of ada programs using fault trees,"IEEE Trans. Rel., vol. R-32, no. 5, pp. 479-484, Dec, 1983.
[22] N.G. Leveson and J.L. Stolzy, "Safety analysis using Petri nets,"IEEE Trans. Software Eng., vol. SE-13, no. 3, pp. 386-397, Mar. 1987.
[23] E.I. Lowe,Computer Control in Process Industries. London: Peregrinus, 1971.
[24] P. G. Neumann, "Some computer-related disasters and other egregious horrors,"ACM Software Eng. Notes, vol. 10, no. 1, pp. 6-7, Jan. 1985.
[25] D. Purdue, "Australian ATMs . . . Forum on risks to the public in computer systems,"ACM Committee Computers and Public Policy, P. G. Neumann, moderator; vol. 5, issue 3, June 18, 1987.
[26] Refine User's Guide, Reasoning Systems Inc., Palo Alto, CA, June 1989.
[27] P. Zave, "An operational approach to requirements specifications for embedded systems,"IEEE Trans. Software Eng., vol. SE-8, no. 3, pp. 250-269, May 1982.

Index Terms:
real-time process-control systems; software requirements specifications; observable phenomena; robustness; ambiguity; abstract state-machine model; semantic analysis; software requirements; formal specification; process computer control; real-time systems
Citation:
M.S. Jaffe, N.G. Leveson, M.P.E. Heimdahl, B.E. Melhart, "Software Requirements Analysis for Real-Time Process-Control Systems," IEEE Transactions on Software Engineering, vol. 17, no. 3, pp. 241-258, March 1991, doi:10.1109/32.75414
Usage of this product signifies your acceptance of the Terms of Use.