National Academies Press: OpenBook
« Previous: 4. Research Modes
Suggested Citation:"5. Conclusions." National Research Council. 1989. Scaling Up: A Research Agenda for Software Engineering. Washington, DC: The National Academies Press. doi: 10.17226/1467.
×
Page 23
Suggested Citation:"5. Conclusions." National Research Council. 1989. Scaling Up: A Research Agenda for Software Engineering. Washington, DC: The National Academies Press. doi: 10.17226/1467.
×
Page 24

Below is the uncorrected machine-read text of this chapter, intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text of each book. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

5 Conclusions Modern society is increasingly dependent on large, complex computer-based systems and therefore on the software that drives them. In many cases, systems designed 20 years ago still provide a foundation for large businesses-and such systems are becoming unmaintainable. As the ability to manipulate, analyze, and grasp information has been magnified by information systems, so also has the appetite to process more and more information. Each new application has generated ever more complex sets of software systems. In the past few years, problems with such systems have cost millions of dollars, time, and even lives in applications ranging from aviation to controls for medical devices. Improving the quality and the trustworthiness of software systems is a national priority, but it is also a problem that seems forever to receive less attention than it deserves because software systems seem invisible, are poorly understood by laymen, and are not even adequately addressed in universities. Managers are consistently surprised by the inability of software engineers to deliver software on time, within budget, and with expected functionality. The nation should not have to wait for a catastrophe before it tries to enhance this critical resource. The software research community has ridden the waves of several advances; expert systems and object-oriented programming have been among the topical foci of researchers during this decade. Although large-system developers benefit from these and other advances, the software systems challenge is fundamental and is not amenable to solution through single categories of advances. As discussed in this report, a necessary first step is for the software engineering community and managers who procure and use large software systems to adopt a more realistic vision of the complex software system development process. Following on, the direction and conduct of software engineering research should be both broadened (in particular, by fostering interactions with practitioners) and made more systematic, through codification and dissemination of knowledge as well as an infusion of more mathematics, science, end' engineering. Good problems make good science and engineering and good problems in the software development community are being bypassed because software engineering researchers are unable to deal with them in a structured, rigorous manner. The Chinese pictograph for "crisis" is composed of the characters for "danger" and "opportunity." The wisdom this represents is worth noting as we grapple with the looming crisis in our ability to create and maintain large and complex software . - 23

24 systems. The danger is that soon we might not be able to create the software our business and government applications need. The opportunity is there for the software engineering research community to find new and fruitful directions in the problems faced by practitioners.

Next: Bibliography »
Scaling Up: A Research Agenda for Software Engineering Get This Book
×
Buy Paperback | $45.00
MyNAP members save 10% online.
Login or Register to save!
Download Free PDF

Large and growing opportunity costs are resulting from the inability to produce sophisticated, reliable software in a timely manner. Software engineering presents stubborn problems, but in this book, a group of experts suggest several constructive directions for research. Together, they support the need for greater interaction between researchers and practitioners and more aggressive efforts to share and reuse software engineering knowledge.

  1. ×

    Welcome to OpenBook!

    You're looking at OpenBook, NAP.edu's online reading room since 1999. Based on feedback from you, our users, we've made some improvements that make it easier than ever to read thousands of publications on our website.

    Do you want to take a quick tour of the OpenBook's features?

    No Thanks Take a Tour »
  2. ×

    Show this book's table of contents, where you can jump to any chapter by name.

    « Back Next »
  3. ×

    ...or use these buttons to go back to the previous chapter or skip to the next one.

    « Back Next »
  4. ×

    Jump up to the previous page or down to the next one. Also, you can type in a page number and press Enter to go directly to that page in the book.

    « Back Next »
  5. ×

    To search the entire text of this book, type in your search term here and press Enter.

    « Back Next »
  6. ×

    Share a link to this book page on your preferred social network or via email.

    « Back Next »
  7. ×

    View our suggested citation for this chapter.

    « Back Next »
  8. ×

    Ready to take your reading offline? Click here to buy this book in print or download it as a free PDF, if available.

    « Back Next »
Stay Connected!