Automating the software development process

Authors:
G. F. Hoffnagle;W. E. Beregi
Affiliations:
IBM Information Systems and Storage Group, Poughkeepsie, New York;IBM Information Systems and Storage Group, Poughkeepsie, New York
Venue:
IBM Systems Journal
Year:
1985

Citing 9
Cited 0

The entity-relationship model—toward a unified view of data

ACM Transactions on Database Systems (TODS) - Special issue: papers from the international conference on very large data bases: September 22–24, 1975, Framingham, MA
CADES - software engineering in practice

ICSE '79 Proceedings of the 4th international conference on Software engineering
Software requirements in the 80's

ACM '80 Proceedings of the ACM 1980 annual conference
Flowchart techniques for structured programming

ACM SIGPLAN Notices
PSL/PSA: A Computer-Aided Technique for Structured Documentation and Analysis of Information Processing Systems

IEEE Transactions on Software Engineering
A Requirements Engineering Methodology for Real-Time Processing Requirements

IEEE Transactions on Software Engineering
A Look at Japan's Development of Software Engineering Technology

Computer
Development Support Systems

Computer
The economics of software quality assurance

AFIPS '76 Proceedings of the June 7-10, 1976, national computer conference and exposition

Quantified Score

Hi-index	0.00

Visualization

Abstract

Demand for reliable software systems is stressing software production capability, and automation is seen as a practical approach to increasing productivity and quality. Discussed in this paper are an approach and an architecture for automating the software development process. The concepts are developed from the viewpoint of the needs of the software development process, rather than that of established tools or technology. We discuss why automation of software development must be accomplished by evolutionary means. We define the architecture of a software engineering support facility to support long-term process experimentation, evolution, and automation. Such a facility would provide flexibility, tool portability, tool and process integration, and process automation for a wide range of methodologies and tools. We present the architectural concepts for such a facility and examine ways in which it can be used to foster software automation.