The operational versus the conventional approach to software development

ABSTRACT

The conventional approach to software development is being challenged by new ideas, many of which can be organized into an alternative decision structure called the “operational” approach. The operational approach is explained and compared to the conventional one.

REFERENCES

• 1: Mack Alford, Software requirements in the 80's, Proceedings of the ACM 1980 annual conference, p.342-349, January 1980 [doi>10.1145/800176.809989]
• 2: John Backus, Can programming be liberated from the von Neumann style?: a functional style and its algebra of programs, Communications of the ACM, v.21 n.8, p.613-641, Aug. 1978 [doi>10.1145/359576.359579]
• 3: Balzer, R. Personal communication, April 1982.
• 4: Robert M. Balzer , Neil M. Goldman , David S. Wile, Operational specification as the basis for rapid prototyping, ACM SIGSOFT Software Engineering Notes, v.7 n.5, p.3-16, December 1982
• 5: Balzer, R. and Goldman, N. Principles of good software specification and their implications for specification language. Specifications of Reliable Software Conference, Cambridge, MA (April 1979), 58-67.
• 6: F. L. Bauer , M. Broy , R. Gnatz , W. Hesse , B. Krieg-Brückner , H. Partsch , P. Pepper , H. Wössner, Towards a wide spectrum language to support program specification and program development, ACM SIGPLAN Notices, v.13 n.12, p.15-24, December 1978 [doi>10.1145/954587.954588]
• 7: Bauer, F.L. et al. Programming in a wide spectrum language: A collection of examples. Sci. Comput. Program 1. (October 1981-, 78- 114.
• 8: Bruce I. Blum, The life cycle: a debate over alternate models, ACM SIGSOFT Software Engineering Notes, v.7 n.4, p.18-20, October 1982 [doi>10.1145/1005950.1005953]
• 9: Britton. K.H. and Parnas, D.L. A-7E software module guide. Naval Research Laboratory Memorandum Report 4702, Washington, D.C. (December 1981).
• 10: John Cameron, JSP and JSD: The Jackson Approach to Software Development, IEEE Computer Society Press, Los Alamitos, CA, 1989
• 11: Clements, P.C. Function specifications for the A-7E function driver module. Naval Research Laboratory Memorandum Report 4658, Washington, D.C. (November 1981).
• 12: Clements, P.C. Interface specifications for the A-7E shared services module. Naval Research Laboratory Memorandum Report 4863, Washington, D.C. (September 1982).
• 13: Darlington, J. An experimental program transformation and synthesis system. Artif. IntelL 16 (March 1981), 1-46.
• 14: Neil M. Goldman , David S. Wile, A Relational Data Base Foundation for Process Specification, Proceedings of the 1st International Conference on the Entity-Relationship Approach to Systems Analysis and Design, p.413-432, January 1980
• 15: Heninger, K.L. Specifying software requirements for complex systems: New techniques and their application. IEEE Trans. Softw. Eng. SE-6 (January 1980), 2-13.
• 16: Heninger, K.L. et al. Software requirements for the A-7E aircraft. Naval Research Laboratory Memorandum Report. 3876, Washington, D.C. (November 1978).
• 17: Hester, S.D., Pamas, D.L. and Utter, D.F. Using documentation as a software design medium. Bell Sys. Tech. J. 60, (October 1981), 1941- 1977.
• 18: M. A. Jackson, Principles of Program Design, Academic Press, Inc., Orlando, FL, 1975
• 19: M. A Jackson, System development (Prentice-Hall International series in computer science), Prentice-Hall, Inc., Upper Saddle River, NJ, 1983
• 20: Donald E. Knuth, Structured Programming with go to Statements, ACM Computing Surveys (CSUR), v.6 n.4, p.261-301, Dec. 1974 [doi>10.1145/356635.356640]
• 21: London, P. and Feather, M. Implementing specification freedoms. Sei. Comput. Program. 2 (November 1982), 91-131.
• 22: Michael Jackson Systems Ltd. Jackson System Development (course manual), 1982.
• 23: McCracken, D.D. and Jackson, M.A. A minority dissenting position. Systems Analysis and Design--A Foundation for the 19gO's, William W. Cotterman et al., eds., Elsevier North-Holland, New York, 1981, 551- 553.
• 24: Parker, R.A. et al. Abstract interface specifications for the A-7E device interface module. Naval Research Laboratory Memorandum Report. 4385, Washington, D.C. (November 1980).
• 25: D. L. Parnas, On the criteria to be used in decomposing systems into modules, Communications of the ACM, v.15 n.12, p.1053-1058, Dec. 1972 [doi>10.1145/361598.361623]
• 26: Parnas, D.L. The use of precise specifications in the development of software. IFIP Congress, Toronto, Ontario, August 1977, 861-867.
• 27: Parnas, D.L. Designing software for ease of extension and contraction. IEEE Trans. Softw. Eng. SE-5 (March 1979), 128-138.
• 28: Parnas, D.L. et al. Interface specifications for the SCR (A-7E) extended computer module. Naval Research Laboratory Memorandum Report 4843, Washington. D.C. (January 1983).
• 29: Swartout, W. GIST English Generator. Proc. National Conf. Artif. Intell., Pittsburgh, PA (August 1982), 404-409.
• 30: William Swartout , Robert Balzer, On the inevitable intertwining of specification and implementation, Communications of the ACM, v.25 n.7, p.438-440, July 1982 [doi>10.1145/358557.358572]
• 31: TRW Defense and Space Systems Group. Distributed computing design system/DCDS description. Tech. Rep. CDRL A004, Huntsville, AB, (August 1981).
• 32: D. A. Turner, The semantic elegance of applicative languages, Proceedings of the 1981 conference on Functional programming languages and computer architecture, p.85-92, October 18-22, 1981, Portsmouth, New Hampshire, United States [doi>10.1145/800223.806766]
• 33: Philip Wadler, Applicative style programming, program transformation, and list operators, Proceedings of the 1981 conference on Functional programming languages and computer architecture, p.25-32, October 18-22, 1981, Portsmouth, New Hampshire, United States [doi>10.1145/800223.806759]
• 34: Weyuker, E.J. On testing nontestable programs. The Comput. J. 25, 4, (1982), 465-470.
• 35: Niklaus Wirth, On the Composition of Well-Structured Programs, ACM Computing Surveys (CSUR), v.6 n.4, p.247-259, Dec. 1974 [doi>10.1145/356635.356639]
• 36: Yeh, R.T. et al. Software requirements: New directions and perspectives. Software Engineering Handbook, C.V. Ramamoorthy and C.R. Vick, eds., Van Nostrand Reinhold, New York, to appear.
• 37: Zave, P. The anatomy of a proc136s-control system. Submitted for publication, May 1982.
• 38: Zave. P. A distributed alternative to finite-state-machine specifications. Submitted for publication, December 1982.
• 39: Zave, P. An operational approach to requirements specification for embedded systems. IEEE Trans. Softw. Eng. SE-8 (May 1982), 250-269.
• 40: Pamela Zave, Testing incomplete specifications of distributed systems, Proceedings of the first ACM SIGACT-SIGOPS symposium on Principles of distributed computing, p.42-48, August 18-20, 1982, Ottawa, Canada [doi>10.1145/800220.806680]
• 41: Zave, P. Case study: The PAISLey approach applied to its own software tools. Submitted for publication, June 1983.
• 42: Pamela Zave , Raymond T. Yeh, Executable requirements for embedded systems, Proceedings of the 5th international conference on Software engineering, p.295-304, March 09-12, 1981, San Diego, California, United States

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.1 Requirements/Specifications
          Subjects: Methodologies (e.g., object-oriented, structured)

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.2 Design Tools and Techniques
          Subjects: Top-down programming**
      D.2.4 Software/Program Verification
          Subjects: Validation
      D.2.9 Management
          Subjects: Productivity; Life cycle
      D.2.m Miscellaneous
          Subjects: Rapid prototyping**

  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.3 Software Management
          Subjects: Software development

General Terms:
Design, Documentation, Management, Performance, Theory

Keywords:
software development methods