Beyond programming-in-the-large: The next challenges for software engineering

  • Mary Shaw
Knowledge-Based And Future Programming Environments
Part of the Lecture Notes in Computer Science book series (LNCS, volume 244)


As society's dependence on computing broadens, software engineering is being called upon to address new problems that raise new technical and nontechnical concerns. Aspirations and expectations for the application of computers appear to be unbounded, but present software development and support techniques will not be adequate to build computational systems that satisfy our expectations, even at very high cost. Each order-of-magnitude increase in the scale of the problems being solved leads to a new set of critical problems that require essentially new solutions. The next challenges for software engineering will deal with software as one of many elements in complex systems, which we call program-as-component, and with the role of software as an active participant in the software development process, which we call program-as-deputy.


Software Development Software Engineer Software Problem Software Development Process Abstract Data Type 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

8 References

  1. [AP 83]
    Associated Press story in Los Angeles Times, 24 August 1983, p. 1. Reported in Software Engineering Notes 8, 5, October 1983.Google Scholar
  2. [Baker 72]
    F. T. Baker. "Chief Programmer Team Management of Production Programming." IBM Systems Journal, 11, 1, 1972, pp. 56–73.Google Scholar
  3. [Barbacci 85]
    Mario Barbacci. A. Nico Habermann, Mary Shaw. "The Software Engineering Institute: Bridging Practice and Potential." IEEE Software, 2, 6, November 1985, pp. 4–21.Google Scholar
  4. [Boehm 81]
    Barry W. Boehm. Software Engineering Economics. Prentice-Hall, 1981.Google Scholar
  5. [DeRemer 76]
    Frank DeRemer and Hans H. Kron. "Programming-in-the-Large versus Programming-in-the-Small." IEEE Transactions on Software Engineering, 2, 2, June 1976, pp. 80–86.Google Scholar
  6. [Devenney 76]
    Thomas J. Devenney. An Exploratory Study of Software Cost Estimating at the Electronic Systems Division. MS dissertation, Air Force Institute of Technology, July 1976 (approved for public release).Google Scholar
  7. [Dijkstra 68]
    Edsger Dijkstra. "GOTO Statement Considered Harmful." Communications of the ACM, 11, 3, March 1968, pp. 147–148.Google Scholar
  8. [Fox 83]
    Joseph M. Fox. Software and Its Development. Prentice-Hall, 1983, pp. 187–188. Reported in Software Engineering Notes 9, 1, January 1984.Google Scholar
  9. [ElA 80]
    Electronic Industries Association, Government Division. DoD Digital Data Processing Study — a Ten Year Forecast. 1980.Google Scholar
  10. [Knuth 68]
    Donald E. Knuth. Fundamental Algorithms. The Art of Computer Programming, Vol. 1, Addison-Wesley 1968.Google Scholar
  11. [Marshall 80]
    Elliott Marshall. "NRC Takes a Second Look at Reactor Design." Science, 207 (28 March 1980), pp. 1445–48. Reported in Software Engineering Notes 10, 3 (July 1985).Google Scholar
  12. [Musa 85]
    John D. Musa. "Software Engineering: The Future of a Profession." IEEE Software, 2, 1, January 1985, pp. 55–62.Google Scholar
  13. [Naur 68]
    Peter Naur and Brian Randell (eds). Software Engineering. Report on a conference sponsored by the NATO Science Committee, Garmisch, Germany, 7–11 October 1968.Google Scholar
  14. [Parnas 72]
    David L. Parnas. "On the Criteria for Decomposing Systems into Modules." Communications of the ACM, 15, 12, December 1972, pp. 1053–1058.Google Scholar
  15. [Redwine 84]
    Samuel T. Redwine, Louise Giovane Becker, Ann B. Marmor-Squires, R. J. Martin, Sarah H. Nash, William E. Riddle. DoD Related Software Technology Requirements, Practice, and Prospects for the Future. Institute for Defense Analysis, IDA Paper P-1788, June 1984.Google Scholar
  16. [Shaw 85]
    Mary Shaw (ed). The Carnegie-Mellon Curriculum for Undergraduate Computer Science. Springer-Verlag, 1985.Google Scholar
  17. [Shaw 86]
    Mary Shaw. "Education for the Future of Software Engineering." Proc. of Software Engineering Institute Software Engineering Education Workshop, Springer-Verlag 1986 (to appear).Google Scholar
  18. [Tomayko 85]
    James Tomayko. Personal communication.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1987

Authors and Affiliations

  • Mary Shaw
    • 1
  1. 1.Software Engineering InstituteCarnegie-Mellon UniversityPittsburgh

Personalised recommendations