The operational versus the conventional approach to software development

Communications of the ACM

Volumn 27, Issue 2, 1984, Pages 104-118

  Zave, Pamela ^a  

^a LUCENT TECHNOLOGIES   (United States)

Author keywords

software development methods

Indexed keywords

COMPUTER SOFTWARE;

EID: 0021371582     PISSN: 00010782     EISSN: 15577317     Source Type: Journal    
DOI: 10.1145/69610.357982     Document Type: Article

References (43)

1. Alford, M. Software requirements in the 80s: From alchemy to science. Proc. ACM ‘80. Nashville. TN (October 1980).
2. Backus, J. Can programming be liberated from the von Neumann style? A functional style and its algebra of programs. Commun. ACM 21 (August 1978), 613-641.
3. Balzer, R. Personal communication, April 1982.
4. Balzer, R.M. Goldman, N.M. and Wile. D.S. Operational specification as the basis for rapid prototyping. ACM SIGSOFT Soflw. Eng. Notes 7, (December 1982), 3-16.
5. Balzer, R. and Goldman, N. Principles of good softwrare specification and their implications for specification language. Specifications of Reliable Software Conference. Cambridge. MA (April 1979), 58-67.
6. Bauer. F.L. et al. Towards a wide spectrum language to support program specification and program development. SIGPLAN Notices 13. (December 1978), 15-24.
7. Bauer, F.L. et al. Programming in a wide spectrum language: A collection of examples. Sri. Comput. Program 1. (October 1981), 73-114.
8. Blum, B.I. The life cycle-A debate over alternative models. Softw. Eng. Notes 7 (October 1982), 18-20.
9. Britton, K.H. and Parnas. D.L. A-7E software module guide. Naval Research Laboraton/ Memorandum Report 4702, Washington, D.C. (December 1981).
10. Cameron, J.R. JSP and JSD: The jactcson Approach to Software Development, to be published.
11. Clements, P.C. Function specifications for the A-7E function driver module. Naval Research Laboratonl 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. Goldman, N.M. and Wile, D.S. A relational data base foundation for process specifications. In: Entity-Relationship Approach to Systems Analysis and Design, P.P. Chen, ed. Elsevier North-Holland, New York, 1980, 413-432.
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. Software requirements for the A-7E aircraft. Naval Research Laboratory Memorandum Report, 3876, Washington, D.C. (November 1978).
17. Hester, S.D., Parnas, D.L. and Utter, D.F. Using documentation as a software design medium. Bell Sys, Tech. ], 60, (October 1981), 1941-1977.
18. lackson, M.A. Principles of Program Design, Academic Press, New York, 1975.
19. Jackson, M.A. System Development, Prentice-Hall, Englewood Cliffs, NJ, 1982.
20. Knuth, D.E. Structured programming with go to statements. Comput Surv, 6 (December 1974), 261-301.
21. London, P. and Feather, M. Implementing specification freedoms. Sci. Comput. Program. 2 (November 1982), 91-131.
22. Michael)ackson 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 1980's, William W. Cotterman et ai, eds., Elsevier North-Holland, New York, 1981, 551553.
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. Parnas, D.L. On the criteria to be used in decomposing systems into modules. Commun. ACM 15 (December 1972), 1053-1058.
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. Swartout. W. and Balzer. R. On the inevitable intertwining of specification and implementation. Commun. ACM 25 (July 1982), 438-440.
31. TRW Defense and Space Systems Group. Distributed computing design system/DCDS description. Tech. Rep. CDRL A004. Huntsville, AB, (August 1981).
32. Turner, D.A. The semantic elegance of applicative languages. Proc.
33. Conf. Funct. Program. Lang. Comput. Archil., Portsmouth. NH, (October 1981), 85-92.
34. Wadler, P. Applicative style programming, program transformation, and list operators. Proc. Conf. Funct. Program. Lang. Comput. Archit. Portsmouth. N.H. (October 1981), 25-32.
35. Weyuker, E.|. On testing nontestable programs. The Comput. ]. 25, 4, (1982), 465-470.
36. Wirth, N. On the composition of well-structured programs. Comput. Surv. 6, (December 1974), 247-259.
37. 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.
38. Zave. P. The anatomy of a procl36s-control system. Submitted for publication. May 1982.
39. Zave. P. A distributed alternative to finite-state-machine specifications. Submitted for publication. December 1982.
40. Zave, P. An operational approach to requirements specification for embedded systems. IEEE Trans. Softw. Eng. SE-8 (May 1982). 250-269.
41. Zave, P. Testing incomplete specifications of distributed systems. ACM/SIGACT-SIGOPS Symp Princ. Distributed Comput. Ottawa, Canada (August 1982), 42-48.
42. Zave, P. Case study: The PAlSLey approach applied to its own software tools. Submitted for publication. June 1983.
43. Zave, P. and Yeh, R.T. Executable requirements for embedded systems. Fifth Int. Conf Softw. Eng. San Diego, California. (March 1981), 295-304.