The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.01 - January-March (1997 vol.19)
pp: 20-54
ABSTRACT
<p>For the last quarter of a century, software technologists have worked to address the "software crisis" identified in the 1960s. Their efforts have focused on a number of different areas, but have often been marked by the search for singular "best" solutions. However, the fundamental nature of software—involving basic and poorly understood problem-solving processes combined with unprecedented and multifaceted complexity—weighs heavily against the utility of singular approaches. Examination of the discourse of software technologists in a number of key professional and trade journals over the last 25 years illuminates various disputes central to the development of software engineering and highlights the necessity of a more pluralistic mindset revolving around synthesis and trade-offs.</p>
CITATION
Stuart Shapiro, "Splitting the Difference: The Historical Necessity of Synthesis in Software Engineering", IEEE Annals of the History of Computing, vol.19, no. 1, pp. 20-54, January-March 1997, doi:10.1109/85.560729
REFERENCES
1. Andrew L. Friedman with Dominic S. Cornfeld, Computer Systems Development: History, Organization and Implementation.New York: John Wiley&Sons, 1989.
2. David Lorge Parnas, "Software Aspects of Strategic Defense Systems," Am. Scientist, vol. 73, no. 5, pp. 432-440; reprinted in Computerization and Controversy: Value Conflicts and Social Choices, Charles Dunlop and Rob Kling, eds. New York: Academic Press, 1991, pp. 593-611.
3. F.P. BrooksJr., "No Silver Bullet—Essence and Accidents of Software Engineering," Computer, vol. 20, no. 4, Apr. 1987, pp. 10-19.
4. Eloina Pelaez, "A Gift from Pandora's Box: The Software Crisis," PhD diss., Univ. of Edinburgh, 1988.
5. Peter Naur and Brian Randell, eds., Software Engineering: Report on a Conference Sponsored by the NATO Science Committee,Garmisch, Germany, Oct.7-11, 1968. Brussels: Scientific Affairs Division, NorthAtlantic Treaty Organization (NATO), 1969, p. 13.
6. B. Randell, "Towards a Methodology of Computing System Design," Peter Naur and Brian Randell, eds., Software Engineering: Report on a Conference Sponsored by the NATO Science Committee,Garmisch, Germany, Oct.7-11, 1968. Brussels: Scientific Affairs Division, NorthAtlantic Treaty Organization (NATO), 1969, p. 205.
7. Stanley Gill, "Thoughts on the Sequence of Writing Software," Peter Naur and Brian Randell, eds., Software Engineering: Report on a Conference Sponsored by the NATO Science Committee,Garmisch, Germany, Oct.7-11, 1968. Brussels: Scientific Affairs Division, NorthAtlantic Treaty Organization (NATO), 1969, p. 186.
8. J. N. Buxton and B. Randell, eds., Software Engineering Techniques: A Report on a Conference Sponsored by the NATO Science Committee,Rome, Italy, Oct.27-31, 1969. Brussels: Scientific Affairs Division, NATO, 1970, p. 7.
9. R. M. Needham and J. D. Aron, "Software Engineering and Computer Science," J. N. Buxton and B. Randell, eds., Software Engineering Techniques: A Report on a Conference Sponsored by the NATO Science Committee,Rome, Italy, Oct.27-31, 1969. Brussels: Scientific Affairs Division, NATO, 1970, p. 114.
10. Niklaus Wirth, "Program Development by Stepwise Refinement," Comm. ACM, vol. 14, p. 221, Apr. 1971.
11. Alan Cohen, "Letter," Datamation, vol. 17, p. 15, Feb.1, 1971.
12. D. L. Parnas, "A Technique for Software Module Specification with Examples," Comm. ACM, vol. 15, p. 330, May 1972.
13. D.L. Parnas, "On the Criteria to be Used in Decomposing Systems into Software Modules," Comm. ACM, Dec. 1972, pp. 1,053-1,058.
14. Glenford J. Myers, "Characteristics of Composite Design," Datamation, vol. 19, p. 102, Sept. 1973.
15. Frank DeRemer and Hans Kron, "Programming-in-the-Large Versus Programming-in-the-Small," SIGPLAN Notices, vol. 10, p. 114, June 1975.
16. Barbara H. Liskov and Stephen N. Zilles, "Specification Techniques for Data Abstractions," IEEE Transactions on Software Engineering, vol. 1, p. 7, Mar. 1975.
17. John Guttag, "Abstract Data Types and the Development of Data Structures," Comm. ACM, vol. 20, p. 404, June 1977.
18. Grady Booch, "Object-Oriented Development," IEEE Transactions on Software Engineering, vol. 12, p. 212, Feb. 1986.
19. Patrick H. Loy, "A Comparison of Object-Oriented and Structured Development Methods," Software Eng. Notes, vol. 15, p. 46, Jan. 1990.
20. Brad J. Cox, "Message/Object Programming: An Evolutionary Change in Programming Technology," IEEE Software, vol. 1, p. 51, Jan. 1984.
21. Victor R. Basili et al., "Characterization of an Ada Software Development" Computer, vol. 18, p. 64, Sept. 1985.
22. Paul T. Ward, "How to Integrate Object Orientation with Structured Analysis and Design," IEEE Software, vol. 6, pp. 74-82, Mar. 1989.
23. Russell J. Abbott, "Knowledge Abstraction," Comm. ACM, vol. 30, p. 666, Aug. 1987.
24. B. Curtis, H. Krasner, and N. Iscoe, "A Field Study of the Software Design Process for Large Systems," Comm. ACM, vol. 31, no. 11, pp. 1,268-1,287, 1988.
25. Galen Gruman, "ICSE Assesses the State of Software Engineering," IEEE Software, vol. 6, pp. 110-111, July 1989.
26. M.A. Jackson, Principles of Program Design.New York: Academic Press, 1975.
27. Jean Warnier, Logical Construction of Programs, translation by B.M. Flanagan. New York: Van Nostrand Reinhold, 1976.
28. John Parker, "A Comparison of Design Methodologies," Software Eng. Notes, vol. 3, p. 19, Oct. 1978.
29. James R. Donaldson, "Structured Programming," Datamation, vol. 19, p. 53, Dec. 1973.
30. W. Stevens, G. Myers, and L. Constantine, "Structured Design," IBM Systems J., vol. 13, pp. 115-139, May 1974; reprinted in Classics in Software Engineering, Edward N. Yourdon, ed. New York: Yourdon Press, 1979, pp. 207-232.
31. H.A. Simon, The Sciences of the Artificial, MIT Press, Cambridge, Mass., 1981.
32. F. Terry Baker and Harlan D. Mills, "Chief Programmer Teams," Datamation, vol. 19, p. 58, Dec. 1973.
33. Gerald M. Weinberg, The Psychology of Computer Programming.New York: Van Nostrand Reinhold, 1971.
34. Laton McCartney, "Data for Rent," Datamation, vol. 23, p. 167, May 1977.
35. Fred Gruenberger, "Letter," Datamation, vol. 20, pp. 27-28, Feb. 1974.
36. Dick Butterworth, "Letter," Datamation, vol. 20, p. 158, Mar. 1974.
37. John G. Fletcher, "Letter," Datamation, vol. 20, p. 29, Mar. 1974.
38. R. R. Brown, "1974 Lake Arrowhead Workshop on Structured Programming," Computer, vol. 7, p. 62, Oct. 1974.
39. James L. Elshoff, "The Influence of Structured Programming on PL/I Program Profiles," IEEE Transactions on Software Engineering, vol. 3, p. 367, Sept. 1977.
40. Frank P. Mathur, "Review of Infotech State of the Art Report: Structured Programming," Computer, vol. 9, p. 116, Dec. 1976.
41. Paul Abrahams, "'Structured Programming' Considered Harmful," SIGPLAN Notices, vol. 10, p. 13, Apr. 1975.
42. Daniel M. Berry, "Structured Documentation," SIGPLAN Notices, vol. 10, p. 9, Nov. 1975.
43. D.L. Parnas and P.C. Clements, "A Rational Design Process: How and Why to Fake It," IEEE Trans. Software Eng., Feb. 1986, pp. 251-257.
44. "Address on Structured Programming Keynotes Compcon Software Sessions," Computer, vol. 8, p. 7, Mar. 1975.
45. Peter J. Denning, "Comments on Mathematical Overkill," SIGPLAN Notices, vol. 10, p. 11, Sept. 1975.
46. C. Wrandle Barth, "STRCMACS—an Extensive Set of Macros to Aid in Structured Programming in 360/370 Assembly Language," SIGPLAN Notices, vol. 11, p. 31, Aug. 1976.
47. David Frost, "Psychology and Program Design," Datamation, vol. 21, p. 138, May 1975.
48. Lawrence J. Peters and Leonard L. Tripp, "Is Software Design Wicked?" Datamation, vol. 22, p. 127, May 1976.
49. Lawrence J. Peters and Leonard L. Tripp, "Comparing Software Design Methodologies," Datamation, vol. 23, p. 94, Nov. 1977.
50. Dennis P. Geller, "Letter," Software Eng. Notes, vol. 4, p. 18, Jan. 1979.
51. F.P. Brooks, Jr., The Mythical Man-Month: Essays on Software Engineering, Addison Wesley Longman, Reading, Mass., 1975.
52. Edsger W. Dijkstra, Selected Writings on Computing: A Personal Perspective.New York: Springer Verlag, 1982, pp. 126-128.
53. Harlan D. Mills, "The New Math of Computer Programming," Comm. of the ACM, vol. 18, p. 44, Jan. 1975.
54. Harlan Mills, "Software Development," IEEE Transactions on Software Engineering, vol. 2, pp. 268-269, Dec. 1976.
55. E.W. Dijkstra, A Discipline of Programming.Englewood Cliffs, N.J.: Prentice Hall, 1976.
56. M. E. Hopkins, "A Case for the GOTO," Proc. 25th Nat'l ACM Conf., 1972, pp. 787-790, reprinted in Yourdon, Classics in Software Engineering, pp. 101-109; W. A. Wulf, "A Case Against the GOTO," Proc. 25th Nat'l ACM Conf., pp. 791-797, reprinted in Yourdon, Classics in Software Engineering, pp. 85-98.
57. D.E. Knuth, "Structured Programming with the GOTO Statement," Computing Surveys, vol. 6, 1974.
58. R. A. DeMillo, S. C. Eisenstat, and R. J. Lipton, "Can Structured Programs Be Efficient?" SIGPLAN Notices, vol. 11, p. 16, Oct. 1976.
59. Ronald E. Jeffries, "Letter," SIGPLAN Notices, vol. 11, p. 1, Dec. 1976.
60. William Rosenfeld, "Letter," SIGPLAN Notices, vol. 11, p. 3, Dec. 1976.
61. Henry F. Ledgard and Michael Marcotty, "A Genealogy of Control Structures," Comm. ACM, vol. 18, p. 629, Nov. 1975.
62. Mario J. Gonzalez, Jr., "Workshop Report: The Science of Design," Computer, vol. 12, p. 113, Dec. 1979.
63. Tom Gilb, "Letter," Software Eng. Notes, vol. 3, p. 28, July 1978.
64. Kenneth W. Kolence, "A Software View of Measurement Tools," Datamation, vol. 17, p. 32, Jan.1, 1971.
65. M.H. Halstead, Elements of Software Science. North-Holland, 1977.
66. Thomas J. McCabe, "A Complexity Measure," IEEE Transactions on Software Engineering, vol. 2, p. 308, Dec. 1976.
67. Glenford J. Meyers, "An Extension to the Cyclomatic Measure of Program Complexity," SIGPLAN Notices, vol. 12, p. 61, Oct. 1977.
68. James L. Elshoff and Michael Marcotty, "On the Use of the Cyclomatic Number to Measure Program Complexity," SIGPLAN Notices, vol. 13, p. 38, Dec. 1978.
69. Alonzo G. Grace, Jr., "The Dimensions of Complexity," Datamation, vol. 23, p. 317, Sept. 1977.
70. Edward T. Chen, "Program Complexity and Programmer Productivity," IEEE Transactions on Software Engineering, vol. 4, p. 188, May 1978.
71. Bill Curtis et al., "Measuring the Psychological Complexity of Software Maintenance Tasks with the Halstead and McCabe Metrics," IEEE Transactions on Software Engineering, vol. 5, p. 103, Mar. 1979.
72. N. F. Schneidewind and Heinz-Michael Hoffmann, "An Experiment in Software Error Data Collection and Analysis," IEEE Transactions on Software Engineering, vol. 5, p. 283, May 1979.
73. Warren Harrison et al., "Applying Software Complexity Metrics to Program Maintenance," Computer, vol. 15, p. 78, Sept. 1982.
74. W. M. Evangelist, "Relationships Among Computational, Software, and Intuitive Complexity," SIGPLAN Notices, vol. 18, p. 58, Dec. 1983.
75. Victor R. Basili, Richard W. Selby, Jr., and Tsai-Yun Phillips, "Metric Analysis and Data Validation Across Fortran Projects," IEEE Transactions on Software Engineering, vol. 9, p. 662, Nov. 1983.
76. Martin Shepperd, "A Critique of Cyclomatic Complexity as a Software Metric," Software Eng. J., vol. 3, p. 35, Mar. 1988.
77. J. Paul Myers, Jr., "The Complexity of Software Testing," Software Eng. J., vol. 7, p. 13, Jan. 1992.
78. John C. Munson and Taghi M. Khoshgoftaar, "Measuring Dynamic Program Complexity," IEEE Software, vol. 9, pp. 48-49, Nov. 1992.
79. Victor R. Basili, "Tailoring SQA to Fit Your Own Life Cycle," IEEE Software, vol. 5, p. 87, Mar. 1988.
80. S.L. Pfleeger, "Lessons Learned in Building a Corporate Metrics Program," IEEE Software, May 1993, pp. 67-74.
81. Bernard Elspas, Milton W. Green, and Karl N. Levitt, "Software Reliability," Computer, vol. 4, p. 22, Jan./Feb. 1971.
82. John L. Kirkley, "The Critical Issues: A 1974 Perspective," Datamation, vol. 20, p. 65, Jan. 1974.
83. T. J. Vander Noot, "Systems Testing ... a Taboo Subject?" Datamation, vol. 17, p. 64, Nov.15, 1971.
84. Dorothy A. Walsh, "Structured Testing," Datamation, vol. 23, p. 111, July 1977.
85. Paul F. Barbuto, Jr. and Joe Geller, "Tools for Top-Down Testing," Datamation, vol. 24, p. 178, Oct. 1978.
86. Laura L. Scharer, "Improving System Testing Techniques," Datamation, vol. 23, p. 117, Sept. 1977.
87. John B. Goodenough and Susan L. Gerhart, "Toward a Theory of Test Data Selection," IEEE Transactions on Software Engineering, vol. 1, p. 165, June 1975.
88. B. Chandrasekaran, "Guest Editorial," IEEE Transactions on Software Engineering, vol. 6, p. 235, May 1980.
89. Richard A. DeMillo, Richard J. Lipton, and Frederick G. Sayward, "Hints on Test Data Selection: Help for the Practicing Programmer," Computer, vol. 11, p. 41, Apr. 1978.
90. Elaine J. Weyuker and Thomas J. Ostrand, "Theories of Program Testing and the Application of Revealing Subdomains," IEEE Transactions on Software Engineering, vol. 6, p. 245, May 1980.
91. Nathan H. Petschenik, "Practical Priorities in System Testing," IEEE Software, vol. 2, p. 18, Sept. 1985.
92. Simeon C. Ntafos, "On Required Element Testing," IEEE Transactions on Software Engineering, vol. 10, p. 795, Nov. 1984.
93. Samuel T. Redwine, Jr., "An Engineering Approach to Software Test Data Design," IEEE Transactions on Software Engineering, vol. 9, p. 192, Mar. 1983.
94. Robert W. Floyd, "Assigning Meanings to Programs," Mathematical Aspects of Computer Science, Proceedings of Symposia in Applied Mathematics. Providence, R.I.: American Mathematical Society, 1967, pp. 19-32. For a more in-depth discussion of the history of research on formal verification, see C. B. Jones, The Search for Tractable Ways of Reasoning About Programs. Manchester, England: Dept. of Computer Science, Manchester Univ., 1992, UMCS-92-4-4.
95. C. A. R. Hoare, "Proof of a Program: FIND," Comm. ACM, vol. 14, p. 39, Jan. 1971.
96. M. Foley and C. A. R. Hoare, "Proof of a Recursive Program: Quicksort," Computer J., vol. 14, p. 391, Nov. 1971.
97. C. A. R. Hoare, "Proof of a Structured Program: 'The Sieve of Eratosthenes,'" Computer J., vol. 15, p. 321, Nov. 1972.
98. Richard A. DeMillo, Richard J. Lipton, and Alan J. Perlis, "Social Processes and Proofs of Theorems and Programs," Comm. ACM, vol. 22, p. 271, May 1979.
99. Leslie Lamport, "Letter," Comm. ACM, vol. 22, p. 624, Nov. 1979.
100. W. D. Maurer, "Letter," Comm. ACM, vol. 22, p. 625, Nov. 1979.
101. Richard A. DeMillo, Richard J. Lipton, and Alan J. Perlis, "Letter," Comm. ACM, vol. 22, p. 630, Nov. 1979.
102. Henry Petroski, To Engineer Is Human: The Role of Failure in Successful Design.New York: St. Martin's Press, 1985, p. 165.
103. Richard Hill, "Letter," Comm. ACM, vol. 22, p. 621, Nov. 1979.
104. H. Lienhard, "Letter," Comm. ACM, vol. 22, p. 622, Nov. 1979.
105. Edsger W. Dijkstra, "On a Political Pamphlet from the Middle Ages," Software Eng. Notes, vol. 3, p. 14, Apr. 1978.
106. Richard A. DeMillo, Richard J. Lipton, and Alan J. Perlis, "Letter," Software Eng. Notes, vol. 3, pp. 16-17, Apr. 1978.
107. H. J. Jeffrey, "Letter," Software Eng. Notes, vol. 3, p. 18, Apr. 1978.
108. Raymond J. Rubey, Joseph A. Dana, and Peter W. Biche, "Quantitative Aspects of Software Validation," IEEE Transactions on Software Engineering, vol. 1, p. 152, June 1975.
109. Douglas T. Ross and Kenneth E. Schoman, Jr., "Structured Analysis for Requirements Definition," IEEE Transactions on Software Engineering, vol. 3, p. 6, Jan. 1977.
110. Susan Gerhart, "Workshop Report: Software Testing and Test Documentation," Computer, vol. 12, p. 99, Mar. 1979.
111. Edsger W. Dijkstra, "Correctness Concerns and, Among Other Things, Why They Are Resented," SIGPLAN Notices, vol. 10, p. 547, June 1975.
112. Andrew S. Tanenbaum, "In Defense of Program Testing or Correctness Proofs Considered Harmful," SIGPLAN Notices, vol. 11, p. 68, May 1976.
113. Susan L. Gerhart and Lawrence Yelowitz, "Observations of Fallibility in Applications of Modern Programming Methodologies," IEEE Transactions on Software Engineering, vol. 2, p. 206, Sept. 1976.
114. David L. Parnas, "Letter," Software Eng. Notes, vol. 3, p. 20, Oct. 1978.
115. Debra J. Richardson and Lori A. Clarke, "Partition Analysis: A Method Combining Testing and Verification," IEEE Transactions on Software Engineering, vol. 11, p. 1,488, Dec. 1985.
116. James H. Fetzer, "Program Verification: The Very Idea," Comm. ACM, vol. 31, p. 1,057, Sept. 1988.
117. Mark Ardis et al., "Letter," Comm. ACM, vol. 32, p. 287, Mar. 1989.
118. Richard Hill, "Letter," Comm. ACM, vol. 32, p. 790, July 1989.
119. James C. Pleasant, "Letter," Comm. ACM, vol. 32, p. 374, Mar. 1989.
120. Lawrence Paulson, Avra Cohen, and Michael Gordon, "Letter," Comm. ACM, vol. 32, p. 375, Mar. 1989.
121. James H. Fetzer, "Letter," Comm. ACM, vol. 32, p. 378, Mar. 1989.
122. John Dobson and Brian Randell, "Program Verification: Public Image and Private Reality," Comm. ACM, vol. 32, pp. 420-422, Apr. 1989.
123. James H. Fetzer, "Letter," Comm. ACM, vol. 32, p. 381, Mar. 1989.
124. David A. Nelson, "Letter," Comm. ACM, vol. 32, p. 792, July 1989.
125. James H. Fetzer, "Letter," Comm. ACM, vol. 32, p. 381, Mar. 1989.
126. Leon Stucki, "Guest Editorial," IEEE Transactions on Software Engineering, vol. 2, p. 194, Sept. 1976.
127. C. V. Ramamoorthy, Siu-Bun F. Ho, and W. T. Chen, "On the Automated Generation of Program Test Data," IEEE Transactions on Software Engineering, vol. 2, p. 293, Dec. 1976.
128. G eorge J. Schick and Ray W. Wolverton, "An Analysis of Competing Software Reliability Models," IEEE Transactions on Software Engineering, vol. 4, p. 105, Mar. 1978.
129. Nancy G. Leveson, "Software Safety," Software Eng. Notes, vol. 7, p. 21, Apr. 1982.
130. Algirdas Avizienis and John P. J. Kelly, "Fault Tolerance by Design Diversity: Concepts and Experiments," Computer, vol. 17, p. 67, Aug. 1984.
131. Dave E. Eckhardt, Jr. and Larry D. Lee, "A Theoretical Basis for the Analysis of Multiversion Software Subject to Coincident Errors," IEEE Transactions on Software Engineering, vol. 11, p. 1,511, Dec. 1985.
132. J.C. Knight and N.G. Leveson, "An Experimental Evaluation of the Assumption of Independence in Multiversion Programming," IEEE Trans. Software Eng., Vol. 12, No. 1, 1986, pp. 96-109.
133. John C. Knight and Nancy G. Leveson, "A Reply to the Criticisms of the Knight&Leveson Experiment," Software Eng. Notes, vol. 15, pp. 24-35, Jan. 1990.
134. Bev Littlewood and Douglas R. Miller, "Conceptual Modeling of Coincident Failures in Multiversion Software," IEEE Transactions on Software Engineering, vol. 15, p. 1,596, Dec. 1989.
135. S.S. Brilliant et al., "Analysis of Faults in an N-Version Software Experiment," IEEE Trans. Software Eng., Vol. 16, No. 2, 1990, pp. 238-247.
136. A.A. Abdel-Ghaly,P.Y. Chan,, and B. Littlewood,“Evaluation of competing software reliability predictions,” IEEE Trans. on Software Engineering, vol. 12, no. 9, 1986.
137. Richard Hamlet, "Special Section on Software Testing," Comm. ACM, vol. 31, pp. 665-666, June 1988.
138. Galen Gruman, "IFIP Participants Debate Programming Approaches," IEEE Software, vol. 6, p. 76, Nov. 1989.
139. Donald MacKenzie, "Negotiating Arithmetic, Constructing Proof: The Sociology of Mathematics and Information Technology," Social Studies of Science, vol. 23, pp. 37-65, Feb. 1993.
140. National Bureau of Standards, Guideline for Lifecycle Validation, Verification, and Testing of Software,Washington, D.C., 1983, NBS FIPS 101; quoted in David Gelperin and Bill Hetzel, "The Growth of Software Testing," Comm. ACM, vol. 31, p. 690, June 1988.
141. D.R. Wallace and R.U. Fujii, "Software Verification and Validation: An Overview," IEEE Software, pp. 10-17, May 1989.
142. C.A.R. Hoare, "An Axiomatic Basis for Computer Programming," Comm. ACM, 1969.
143. C. A. R. Hoare, "Professionalism," Computer Bull., 2nd series, p. 3, Sept. 1981.
144. Stuart Shapiro, "Its Own Worst Enemy: How Software Engineering Has Fallen Victim to Engineering Mythology," CRICT Discussion Paper No. 25, Brunel Univ., 1992.
145. Nancy G. Leveson, "Formal Methods in Software Engineering," IEEE Transactions on Software Engineering, vol. 16, p. 929, Sept. 1990.
146. Susan L. Gerhart, "Applications of Formal Methods: Developing Virtuoso Software," IEEE Software, vol. 10, p. 10, Sept. 1990.
147. C. B. Jones, "Theorem Proving and Software Engineering," Software Eng. J., vol. 3, p. 2, Jan. 1988.
148. Susan Gerhart, "Formal Methodists Warn of Software Disasters," IEEE Software, vol. 6, p. 77, Nov. 1989.
149. Anthony Hall, "Seven Myths of Formal Methods," IEEE Software, vol. 7, p. 13, Sept. 1990.
150. J.M. Wing, “A Specifier's Introduction to Formal Methods,” IEEE Computer, vol. 23, pp. 8–24, Sept. 1990.
151. Harlan D. Mills, Michael Dyer, and Richard C. Linger, "Cleanroom Software Engineering," IEEE Software, vol. 4, p. 20, Sept. 1987.
152. R. W. Selby, V. R. Basili, and F. T. Baker,“Cleanroom software development: An empirical investigation,”IEEE Trans. Software Eng., vol. SE-13, pp. 1027–1037, Sept. 1987.
153. D. A. Duce and E.V. C. Fielding, "Formal Specification—a Comparison of Two Techniques," Computer J., vol. 30, p. 327, Aug. 1987.
154. C.A. R. Hoare, "An Overview of Some Formal Methods for Program Design," Computer, vol. 20, pp. 90-91, Sept. 1987.
155. Carl Chang, "Let's Stop the Bipolar Drift," IEEE Software, vol. 7, p. 4, May 1990.
156. I. F. Currie, "NewSpeak: An Unexceptional Language," Software Eng. J., vol. 1, pp. 170-176, July 1986.
157. Jean E. Sammet, Programming Languages: History and Fundamentals.Englewood Cliffs, N.J.: Prentice Hall, 1969; and Richard L. Wexelblat, ed., History of Programming Languages. New York: Academic Press, 1981. These works contain in-depth histories of these older languages.
158. David A. Fisher, "DoD's Common Programming Language Effort," Computer, vol. 11, p. 25, Mar. 1978.
159. Barry W. Boehm, "Software and Its Impact: A Quantitative Assessment," Datamation, vol. 19, p. 48, May 1973.
160. Edsger W. Dijkstra, "DoD-I: The Summing Up," SIGPLAN Notices, vol. 13, pp. 24-26, July 1978.
161. Robert L. Glass, "From Pascal to Pebbleman ... and Beyond," Datamation, vol. 25, pp. 146-147, July 1979.
162. Rob Kling and Walter Scacchi, "The DoD Common High Order Programming Language Effort (DoD-1): What Will the Impacts Be?" SIGPLAN Notices, vol. 14, pp. 32-40, Feb. 1979.
163. Paul R. Eggert, "Letter," SIGPLAN Notices, vol. 15, p. 9, Jan. 1980.
164. J. T. Galkowski, "A Critique of the DOD Common Language Effort," SIGPLAN Notices, vol. 15, p. 15, June 1980.
165. Patrick Skelly, "The ACM Position on Standardization of the Ada Language," Comm. ACM, vol. 25, p. 119, Feb. 1982.
166. Henry F. Ledgard and Andrew Singer, "Scaling Down Ada (or Towards a Standard Ada Subset)," Comm. ACM, vol. 25, p. 121, Feb. 1982.
167. Robert L. Glass, "Letter," Comm. ACM, vol. 25, p. 500, July 1982.
168. Randall Leavitt, "Letter," Comm. ACM, vol. 25, p. 500, July 1982.
169. Brian Wichmann, "Is Ada Too Big? A Designer Answers the Critics," Comm. ACM, vol. 27, p. 103, Feb. 1984.
170. William I. MacGregor, "Letter," SIGPLAN Notices, vol. 13, p. 18, Sept. 1978.
171. Peter Wegner, "The Ada Language and Environment," Software Eng. Notes, vol. 5, p. 9, Apr. 1980.
172. Charles Antony Richard Hoare, "The Emperor's Old Clothes," Comm. ACM, vol. 24, p. 82, Feb. 1981.
173. "DOD Interim Policy on Ada Issued," Comm. ACM, vol. 26, p. 706, Sept. 1983.
174. Saul Rosen, "Programming Systems and Languages 1965-1975," Comm. ACM, vol. 15, p. 591, July 1972.
175. David R. Hanson, "A Simple Technique for Representing Strings in Fortran IV," Comm. ACM, vol. 17, p. 646, Nov. 1974.
176. Daniel D. McCracken, "Is There a Fortran in Your Future?" Datamation, vol. 19, p. 237, May 1973.
177. Daniel D. McCracken, "Letter," Comm. ACM, vol. 28, p. 568, June 1985.
178. "The NCC: Reminiscent of the Late Sixties," Datamation, vol. 21, p. 104, June 1975.
179. Tomasz Kowaltowski, "Letter," SIGPLAN Notices, vol. 10, p. 4, Aug. 1975.
180. Eric Campbell, "Letter," SIGPLAN Notices, vol. 11, p. 2, May 1976.
181. Stuart W. Rowland, "Some Comments on Structured Fortran," SIGPLAN Notices, vol. 11, p. 45, Oct. 1976.
182. Michael J. Viehman, "Letter," SIGPLAN Notices, vol. 10, p. 8, Oct. 1975.
183. Anthony Ralston and Jerrold L. Wagener, "Structured Fortran&mdash;an Evolution of Standard Fortran," IEEE Transactions on Software Engineering, vol. 2, p. 154, Sept. 1976.
184. Daniel D. McCracken, "Let's Hear It for COBOL!" Datamation, vol. 22, p. 242, May 1976.
185. Peter Naur, "Programming Languages, Natural Languages, and Mathematics," Comm. ACM, vol. 18, pp. 678-680, Dec. 1975.
186. Michael Hammer et al., "A Very High Level Programming Language for Data Processing Applications," Comm. ACM, vol. 20, pp. 832-833, Nov. 1977.
187. Mark R. Crispin, "Letter," Datamation, vol. 22, p. 7, Nov. 1976.
188. A. C. Larman, "Letter," Computer Bull., 1st series, no. 16, p. 506, Nov. 1972.
189. Ware Myers, "Key Developments in Computer Technology: A Survey," Computer, vol. 9, p. 59, Nov. 1976.
190. Linda Runyan, "Software Still a Sore Spot," Datamation, vol. 27, p. 165, Mar. 1981.
191. Ronald A. Frank, "Let the Users Program," Datamation, vol. 28, p. 88, Jan. 1982.
192. Nigel S. Read and Douglas L. Harmon, "Language Barrier to Productivity," Datamation, vol. 29, p. 209, Feb. 1983.
193. John Cardullo and Herb Jacobsohn, "Letter," Datamation, vol. 29, p. 24, May 1983.
194. Bill Inmon, "Rethinking Productivity," Datamation, vol. 30, p. 185, June15, 1984.
195. Michael H. Brown, "Letter," Datamation, vol. 30, p. 23, Sept.15, 1984.
196. F. J. Grant, "The Downside of 4GLs," Datamation, vol. 31, p. 99, July15, 1985.
197. Peter Wegner, "Capital-Intensive Software Technology, Part 2: Programming in the Large," IEEE Software, vol. 1, p. 31, July 1984.
198. Alex Pines and Dan Pines, "Don't Shoot the Programmers," Datamation, vol. 29, p. 114, Aug. 1983.
199. Santosh K. Misra and Paul J. Jalics, "Third-Generation Versus Fourth-Generation Software Development," IEEE Software, vol. 6, p. 14, July 1989.
200. Bruce Hailpern, "Multiparadigm Languages and Environments," IEEE Software, vol. 3, p. 6, Jan. 1986.
201. Pamela Zave, "A Compositional Approach to Multiparadigm Programming," IEEE Software, vol. 6, p. 15, Sept. 1989.
202. John W. Backus, "Can Programming be Liberated From the von Neumann Style? A Functional Style and Its Algebra of Programs," Communications of the ACM, vol. 21, pp. 613-641, 1978.
203. R. N. Caffin, "Heresy on High-Level Languages," Computer, vol. 12, pp. 108-109, Mar. 1979.
204. Jim Haynes, "Comment on High-Level Heresy," Computer, vol. 12, p. 109, Mar. 1979.
205. David Feign, "Letter," Computer, vol. 12, p. 122, Sept. 1979.
206. William A. Wulf, "Trends in the Design and Implementation of Programming Languages," Computer, vol. 13, p. 15, Jan. 1980.
207. Victor R. Basili and Albert J. Turner, "Iterative Enhancement: A Practical Technique for Software Development," IEEE Transactions on Software Engineering, vol. 1, p. 390, Dec. 1975.
208. W. P. Dodd, "Prototype Programs," Computer, vol. 13, p. 81, Feb. 1980.
209. Pat Hall, Janet Low, and Steve Woolgar, "Human Factors in Information Systems Development: A Project Report," CRICT Discussion Paper No. 31, Brunel University, 1992.
210. Fletcher J. Buckley, "A Modest Proposal," Computer, vol. 15, p. 103, Dec. 1982.
211. Daniel D. McCracken and Michael A. Jackson, "Life Cycle Concept Considered Harmful," Software Eng. Notes, vol. 7, p. 32, Apr. 1982.
212. G. R. Gladden, "Stop the Life-Cycle, I Want to Get Off," Software Eng. Notes, vol. 7, p. 35, Apr. 1982.
213. Patrick A. V. Hall, "Letter," Software Eng. Notes, vol. 7, p. 23, July 1982.
214. Bruce I. Blum, "The Life Cycle&mdash;a Debate Over Alternate Models," Software Eng. Notes, vol. 7, p. 18, Oct. 1982.
215. Joseph W. Chambers, "Letter," Comm. ACM, vol. 26, p. 108, Feb. 1983.
216. Ware Myers, "Can Software Development Processes Improve—Drastically?" IEEE Software, vol. 1, p. 101, July 1984; Mark Dowson and Jack C. Wileden, "A Brief Report on the International Workshop on the Software Process and Software Environments," Software Eng. Notes, vol. 10, p. 21, July 1985.
217. Stefano Nocentini, "The Planning Ritual," Datamation, vol. 31, p. 128, Apr.15, 1985.
218. R. E. A. Mason and T. T. Carey, "Prototyping Interactive Information Systems," Comm. ACM, vol. 26, p. 348, May 1983.
219. Jerry Schulz, "Letter," Datamation, vol. 29, p. 24, Sept. 1983.
220. Barry W. Boehm, Terence E. Gray, and Thomas Seewaldt, "Prototyping Versus Specifying: A Multiproject Experiment," IEEE Transactions on Software Engineering, vol. 10, p. 300, May 1984.
221. Gruia-Catalin Roman, "A Taxonomy of Current Issues in Requirements Engineering," Computer, vol. 18, p. 20, Apr. 1985.
222. Zohar Manna and Richard Waldinger, "Synthesis: Dreams => Programs," IEEE Transactions on Software Engineering, vol. 5, p. 295, July 1979.
223. D. J. Cooke, "Program Transformation," Computer Bull., 2nd series, p. 20, Dec. 1979.
224. David W. Wile, "Program Developments: Formal Explanations of Implementations," Comm. ACM, vol. 26, p. 903, Nov. 1983.
225. Pamela Zave, "The Operational Versus the Conventional Approach to Software Development," Comm. ACM, vol. 27, p. 113, Feb. 1984.
226. Manfred Broy and Peter Pepper, "Program Development as a Formal Activity," IEEE Transactions on Software Engineering, vol. 7, p. 22, Jan. 1981.
227. B. Boehm, "A Spiral Model of Software Development and Enhancement," Computer, May 1988, pp. 61-72.
228. D. M. Ritchie and K. Thompson,“The UNIX time sharing system,”Commun. ACM, vol. 17, no. 7, pp. 365–375, July 1974.
229. Evan L. Ivie, "The Programmer's Workbench&mdash;a Machine for Software Development," Comm. ACM, vol. 20, p. 746, Oct. 1977.
230. B. W. Kernighan and P. J. Plauger, "Software Tools," Software Eng. Notes, vol. 1, p. 15, May 1976.
231. Anthony I. Wasserman, "Automated Development Environments," Computer, vol. 14, p. 9, Apr. 1981.
232. Michael Lesk, "Another View," Datamation, vol. 27, p. 139, Nov. 1981.
233. David Morris, "How Not to Worry About Unix," Datamation, vol. 30, p. 83, Aug.1, 1984.
234. Dennis F. Barlow and Norman S. Zimbel, "Unix—How Important Is It?" Datamation, vol. 30, p. 101, Aug.1, 1984.
235. T.H. Crowley, L. L. Crume, and C. B. Hergenhan, "AT&T Asks for a Unix Standard," Datamation, vol. 30, p. 100, Aug.1, 1984.
236. Peter J. Denning, "Throwaway Programs," Comm. ACM, vol. 24, p. 58, Feb. 1981.
237. Grover P. Righter, "Letter," Datamation, vol. 30, p. 16, Nov.1, 1984.
238. Tim Teitelbaum, "The Cornell Program Synthesizer: A Syntax-Directed Programming Environment," SIGPLAN Notices, vol. 14, p. 75, Oct. 1979.
239. Vic Stenning et al., "The Ada Environment: A Perspective," Computer, vol. 14, p. 27, June 1981.
240. Charles Rich and Howard E. Shrobe, "Initial Report on a Lisp Programmer's Apprentice," IEEE Transactions on Software Engineering, vol. 4, p. 456, Nov. 1978.
241. Elliot Soloway, "A Cognitively-Based Methodology for Designing Languages/Environments/Methodologies," SIGPLAN Notices, vol. 19, p. 195, May 1984.
242. Ware Myers, "MCC: Planning the Revolution in Software," IEEE Software, vol. 2, p. 72, Nov. 1985.
243. S. Patil and P. Banerjee,“Performance trade-offs in a parallel test generation/fault simulation environment,” IEEE Trans. Computer-Aided Design, vol. 10, no. 12, pp. 1542-1558, Dec. 1991.
244. Winston Royce, "Has the Exploratory Approach Come of Age?" IEEE Software, vol. 10, p. 104, Jan. 1993.
245. A. Nico Habermann and David Notkin, "Gandalf: Software Development Environments," IEEE Transactions on Software Engineering, vol. 12, p. 1,118, Dec. 1986.
246. Jayshree Ramanathan and Soumitra Sarkar, "Providing Customized Assistance for Software Lifecycle Approaches," IEEE Transactions on Software Engineering, vol. 14, p. 749, June 1988.
247. Ronald J. Norman and Gene Forte, "CASE in the '90s," Comm. ACM, vol. 35, p. 30, Apr. 1992.
248. Arthur J. Collmeyer, "Developments in Design Automation," Computer, vol. 7, p. 11, Jan. 1974.
249. Peter Freeman, "Automating Software Design," Computer, vol. 7, p. 34, Apr. 1974.
250. F.P. BrooksJr., "No Silver Bullet—Essence and Accidents of Software Engineering," Computer, vol. 20, no. 4, Apr. 1987, pp. 10-19.
251. Paul Rook, "Controlling Software Projects," Software Eng. J., vol. 1, p. 8, Jan. 1986.
252. Anthony Finkelstein, "London Open CRIS Conference," Computer Bull., 2nd series, p. 5, Sept. 1984.
253. A. T. Wood-Harper and G. Fitzgerald, "A Taxonomy of Current Approaches to Systems Analysis," Computer J., vol. 25, pp. 12-16, Feb. 1982.
254. G. Fitzgerald, N. Stokes, and J.R. G. Wood, "Feature Analysis of Contemporary Information Systems Methodologies," Computer J., vol. 28, no. 3, pp. 223-230, 1985.
255. J. Mayhew and P. A. Dearnley, "An Alternative Prototyping Classification," Computer J., vol. 30, pp. 481-484, Dec. 1987.
256. Xiping Song and Leon J. Osterweil, "Toward Objective, Systematic Design-Method Comparisons," IEEE Software, vol. 9, p. 44, May 1992.
257. D. M. Episkopou and A. T. Wood-Harper, "Towards a Framework to Choose Appropriate IS Approaches," Computer J., vol. 29, p. 222, June 1986.
258. Alan M. Davis, Edward H. Bersoff, and Edward R. Comer, "A Strategy for Comparing Alternative Software Development Life Cycle Models," IEEE Transactions on Software Engineering, vol. 14, pp. 1,453-1,461, Oct. 1988.
259. Bo Sanden, "The Case for Electric Design of Real-Time Software," IEEE Transactions on Software Engineering, vol. 15, p. 360, Mar. 1989.
260. "Panel on Problems of the 80s, ICSE Atlanta," Software Eng. Notes, vol. 3, p. 29, July 1978.
261. Ware Myers, "New British Tool Centre a Response to Software Complexity," IEEE Software, vol. 2, p. 94, Nov. 1985.
262. W. Wayt Gibbs, "Software's Chronic Crisis," Scientific Am., pp. 72-81, Sept. 1994.
263. Annie Kuntzmann-Combelles, "Software Help Wanted: Revolutionary Thinkers," IEEE Software, vol. 9, p. 10, Sept. 1992.
22 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool