Scaling up: a research agenda for software engineering

ABSTRACT

The following excerpts have been gleaned from a report by the Computer Science and Technology Board that summarizes the deliberations of a group of software engineers participating in a CSTB workshop that focused on setting research priorities.

REFERENCES

• 1: Ad Hoc Committee on the High Cost and risk of mission-critical Software. Report of the USAF Scientific Advisory Board Ad Hoc Committee on the High Cost and Risk of Mission-Critical Software, US Air Fovca Scientific Advisory Board, Dec. 1983.
• 2: Association for Computing Machinery. Proceedings of Conference on Computer-Supported Cooperative Work (Sept. 26-28, 1988, Portland, Ore.). ACM, N.Y.
• 3: Robert Balzer, A 15 year perspective on automatic programming, IEEE Transactions on Software Engineering, v.11 n.11, p.1257-1268, Nov. 1985 [doi>10.1109/TSE.1985.231877]
• 4: Belady, L. Software is the glue in large systems. IEEE Communications Magazine, Aug. 1989.
• 5: M. M. Lehman , L. A. Belady, Program evolution: processes of software change, Academic Press Professional, Inc., San Diego, CA, 1985
• 6: Bernstein, !_.., and Yuhas, C; The chain of comm_an& UNIX Review, Nov. 1987.
• 7: Besemer, D.J., et al. A Synergy of Industrial and Academic Education. Technical Information Series, General Electric Corporate Research and Development, Schenectady, N.Y., (Aug. 1986).
• 8: Ted J. Biggerstaff , Alan J. Perlis, Software reusability: vol. 1, concepts and models, ACM Press, New York, NY, 1989
• 9: Barry W. Boehm, Software Engineering Economics, Prentice Hall PTR, Upper Saddle River, NJ, 1981
• 10: Barry W. Boehm, A Spiral Model of Software Development and Enhancement, Computer, v.21 n.5, p.61-72, May 1988 [doi>10.1109/2.59]
• 11: Grady Booch, Software Component with ADA, Benjamin-Cummings Publishing Co., Inc., Redwood City, CA, 1987
• 12: Bowen, T., Wigle, G., and Tsai, J. Specification of Software Quality Attributes. RADC-TR-85-37, 1, Rome Air Development Center, 1985.
• 13: Brooks, F.P. No silver bullet--Essence and accidents of software engineering. IFIP's information Processit~g 86, H.j. Kugler (ed.), 1986 Elsevier Science Publishers B.V. (North-Holland).
• 14: J. Craig Cleaveland, Building Application Generators, IEEE Software, v.5 n.4, p.25-33, July 1988 [doi>10.1109/52.17799]
• 15: William James Cody, Software Manual for the Elementary Functions (Prentice-Hall series in computational mathematics), Prentice-Hall, Inc., Upper Saddle River, NJ, 1980
• 16: Computer Science and Technology Board, National Research Council. Toward a National Research Network. National Academy Press, Washington, D.C., 1988.
• 17: Bill Curtis , Herb Krasner , Neil Iscoe, A field study of the software design process for large systems, Communications of the ACM, v.31 n.11, p.1268-1287, Nov. 1988 [doi>10.1145/50087.50089]
• 18: Defense Science Board Task Force on Military Software. Report of the Defense Science Board Task Force on Military Software, Office of the kinder Secretary of Defense for Acquisition, Sept. !98%
• 19: P. Freeman, A conceptual analysis of the Draco approach to constructing software systems, IEEE Transactions on Software Engineering, v.13 n.7, p.830-844, July 1987 [doi>10.1109/TSE.1987.233494]
• 20: Guindon. R. (ed.). Cognitive Science and Its Applications for Human- Computer Interaction. Lawrence Erlbaum Assoc., Hillsdale, N.J., 1988.
• 21: Donald Ervin Knuth, The Art of Computer Programming, 2nd Ed. (Addison-Wesley Series in Computer Science and Information, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1978
• 22: Martin, R.J., and Osborne, W.M. Guidance on software maintenance. NBS special publicati0n 500-106.computer scienceand Teclillotogy, U.S. Dept. of Commerce, National Bureau of Standards, Washington, D.C., Dec. 1983, p. 6.
• 23: McCabe; T. Co_mp!exity Measure. IEEE Trans. on Software Eng.; 2, 4, 308-320.
• 24: Microelectronics and Computer Technology Corporation, Conference Committee for CSCW '86. Proceedings of Conference on Computer-Supported Cooperative Work (December 3-5, 1986, Austin, Tex.). MCC.
• 25: Mills, H.D. Benefits of Rigorous Methods of Software Engineering in DoD Software Acquisitions, Feb. i g8g.
• 26: Mosemann, L.K. Software Engineering and Beyond: The People Problem. Keynote address at the SEI Affiliates Symposium, Software Engineering Institute, Carnegie Mellon Univ., (May 2-4, !989~ Pittsburgh, Pa.).
• 27: Neighbors, J.M. The draco approach to constructing software from reusable components." IEEE Trans. on Software Engineering 10, 5 (1984), 564-573.
• 28: H. Partsch , R. Steinbrüggen, Program Transformation Systems, ACM Computing Surveys (CSUR), v.15 n.3, p.199-236, Sept. 1983 [doi>10.1145/356914.356917]
• 29: Perry, R.H., et al. Perry's Chemical Engineers' Handbook, (1984}. Mc- Graw Hill, N.Y., 1984.
• 30: Royce, W. Managing the development of large software systems. Proceedings WESCON, (Augu_s! !970)~
• 31: Shaw, M. Beyond programming-in-the-large: The next challenges for software engineering. Technical Memorandum SEI-86-TM-6, Software Engineering Institute, Carnegie Mellon Univ., Pittsburgh, Pa., May 1986.
• 32: M. Shaw, Larger scale systems require higher-level abstractions, Proceedings of the 5th international workshop on Software specification and design, p.143-146, April 1989, Pittsburgh, Pennsylvania, United States
• 33: Douglas R. Smith , Gordon B. Kotik , Stephen J. Westfold, Research on knowledge-based software environments at Kestrel Institute, IEEE Transactions on Software Engineering, v.11 n.11, p.1278-1295, Nov. 1985 [doi>10.1109/TSE.1985.231879]
• 34: Swanson, E.B., and Lientz, B. Software Maintenance Management' A Study of the Maintenance of Computer Application Software in 487 Data Processing Organizations. 1980. Addison-Wesley, Reading, Mass.
• 35: G. B. Williams , C. Mui , W. Alagappan , B. B. Johnson, Software design issues: a very large information systems perspective, Proceedings of the 5th international workshop on Software specification and design, p.238-240, April 1989, Pittsburgh, Pennsylvania, United States

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING

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

General Terms:
Design, Experimentation, Languages, Management, Theory