Specifying Software Requirements for Complex Systems: New Techniques and Their Application

IEEE Transactions on Software Engineering

Volumn SE-6, Issue 1, 1980, Pages 2-13

  Heninger, Kathryn L ^a  

^a NAVAL RESEARCH LABORATORY   (United States)

Author keywords

Documentation techniques; functional specifications; real time software; requirements; requirements definition; software requirements; specifications

Indexed keywords

AIRCRAFT, MILITARY - COMPUTER APPLICATIONS;

COMPUTER PROGRAMMING;

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

References (22)

1. P. Brinch Hansen, Operating Systems Principles, Englewood Cliffs, NJ: Prentice-Hall, 1973.
2. E. W. Dijkstra, “CoOperating sequential processes,” in Programming Languages, F. Genuys, Ed. New York: Academic, 1968, pp. 43–112.
3. E. W. Dijkstra, A Discipline of Programming, Englewood Cliffs, NJ: Prentice-Hall, 1977.
4. J. V. Guttag, “Abstract data types and the development of data structures,” Commun. Ass. Comput. Mach., vol. 20, pp. 396–404, June 1976.
5. K. Heninger, J. Kallander, D. L. Parnas, and J. Shore, Software Requirements for the A-7E Aircraft, Naval Res. Lab., Washington, DC, Memo Rep. 3876, Nov. 27, 1978.
6. C. A. R. Hoare, “Monitors: An operating system structuring concept,” Commun. Ass. Comput. Mach., vol. 17, pp. 549–557, Oct. 1974.
7. J. Howard, “Proving monitors,” Commun. Ass. Comput. Mach., vol. 19, pp. 273–279, May 1976.
8. R. Lipton, On Synchronization Primitive Systems, Ph.D. dissertation, Carnegie-Mellon Univ., Pittsburgh, PA, 1973.
9. B. Liskov and S. Zilles, “Specification techniques for data abstractions,” IEEE Trans. Software Eng., vol. SE-1, pp. 7–19, Mar. 1975.
10. B. Liskov and V. Berzins, “An appraisal of program specifications,” in Proc. Conf. on Research Directions in Software Technology, Oct. 10-12, 1977, pp. 13.1-13.24.
11. D. L. Parnas, “Information distribution aspects of design methodology,” in Proc. Int. Fed. Inform. Processing Congr., Aug. 1971, vol. TA-3.
12. D. L. Parnas, “On the criteria to be used in decomposing systems into modules,” Commun. Ass. Comput. Mach., vol. 15, pp. 1053–1058, Dec. 1972.
13. D. L. Parnas and G. Handzel, More on Specification Techniques for Software Modules, Fachbereich Informatik, Technische Hochschule Darmstadt, Darmstadt, W. Germany, 1975.
14. D. L. Parnas and H. Wurges, “Response to undesired events in software systems,” in Proc. 2nd Int. Conf. Software Eng., 1976, pp. 437–446.
15. D. L. Parnas, Use of Abstract Interfaces in the Development of Software for Embedded Computer Systems, Naval Res. Lab., Washington, DC, Rep. 8047, 1977.
16. D. L. Parnas, “The use of precise specifications in the development of software,” in Proc. Int. Fed. Inform. Processing Congr., 1977.
17. D. L. Parnas, “Designing software for ease of extension and contraction,” in Proc. 3rd Int. Conf. Software Eng., May 1978.
18. D. L. Parnas and K. Heninger, “Implementing processes in HAS,” in Software Engineering Principles, Naval Res. Lab., Washington, DC, course notes, 1978, Document HAS.9.
19. D. L. Parnas, “Desired system behavior in undesired situations,” in Software Engineering Principles, Naval Res. Lab., Washington, DC, course notes, 1978, Document UE.l.
20. O. Roubine and L. Robinson, SPECIAL Reference Manual, Stanford Res. Inst., Menlo Park, CA, SRI Tech. Rep. CSL-45, SRI project 4828, 3rd ed., 1977.
21. A. C. Shaw, The Logical Design of Operating Systems, Englewood Cliffs, NJ: Prentice-Hall, 1974.
22. D. M. Weiss, The MUDD Report: A Case Study of Navy Software Development Practices, Naval Res. Lab., Washington, DC, Rep. 7909, 1975.