Scaling Up A Research Agenda for Software Engineering (1989) / Chapter Skim
Currently Skimming:
1. Introduction and Summary
1. Introduction and Summary
Pages 1-6
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 1... ...
The problem has resisted the efforts of many talented individuals over many years. Some degree of resistance to change is inevitable, reflecting the inertia that comes from the large and cumulative investment that companies have made in their software development processes, but CSTB workshop participants expressed a widely shared frustration that options circulating within the software engineering community fall short of what is needed (or fall on deaf ears)
|
From page 2... ...
The CRIB workshop underscored the need for both software engineering researchers and practitioners to accept a more realistic view of the problem. Many of the problems experienced today reflect implicit assumptions that the flow from software system concept to implementation is smoother and more orderly than it is, as well as implicit assumptions that a development process involving project teams is subject to the degree and kind of control that might be found if a single individual were responsible for the software.
|
From page 3... ...
For instance, our state-of-the-practice can finally handle serial, monolithic systems quite well but our challenge is distributed parallel, asynchronous applications for which we have little or no practical cnginecring principles. ~ ~ v v v 0~ Industry does not collaborate effectively with the research community in creating the next generation of software capability and software production technology.
|
From page 4... ...
Perspective Portray systems realistically Research a unifying model · View systems as systems for software · Recognize change as development -- for intrinsic matching programming languages to applications Study and preserve domains and design software artifacts phases . Strengthen mathematical and scientific foundations Engineering practice Codify software Automate handbook engineering knowledge knowledge, access, and for dissemination and reuse -- and make reuse development of routine Develop software software more routine engineering handbooks Nurture collaboration Research modes Foster practitioner and researcher interactions among system developers and between developers and users Legitimize academic exploration of large software systems in situ Glean insights frown behavioral and managerial sciences Develop additional research directions and paradigms -- encourage recognition of review studies, contributions to handbooks clearer understanding of the realities of software development can lead to improvements in any of several ways.
|
From page 5... ...
CSTB workshop participants urged efforts to preserve and study software artifacts and their development processes in the hope that understanding their structure and properties would contribute to the development of better experiments, tools, and software development methods. Develop Unifying Models and Strengthen Mathematical and Scientific Foundations.
|
From page 6... ...
Support for research into and development and use of computer-supported tools for collaborative work would improve the software development process. Research Modes Foster Practitioner and Researcher Interaction and Legitimize Academic Exploration of Large Software Systems.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.