Principles of software engineering environment design.
Frost, John Richard
MacLennan, Bruce J.
MetadataShow full item record
The history of programming languages, operating systems and computer hardware is briefly reviewed. Then the general methodology of established engineering disciplines is examined. Software "engineering" is then examined in light of its history and by analogy with the general engineering methodology. Here, a critical difference between software engineering methods and those of other disciplines is revealed. Software design is not separated from its implementation nor is there an effective means to communicate a software design from a designer to an implementor. It is shown that without an analog to the engineering blueprint, software engineering is not, and cannot become, a true engineering discipline. In following the engineering analogy, twenty-one principles of software engineering environment design are put forth. These touch on technical, management and ergonomic issues. Finally, it is concluded that work on software engineering environments holds much more promise for improved productivity than the traditional approach of programming language design.
RightsThis publication is a work of the U.S. Government as defined in Title 17, United States Code, Section 101. Copyright protection is not available for this work in the United States.
Showing items related by title, author, creator and subject.
Agrawal, B.N. (2005);This paper presents a review of the spacecraft design program at the Naval Postgraduate School. This program is part of the space systems engineering curriculum. In this curriculum, the students take at least one course ...
Naegle, Brad R. (Monterey, California. Naval Postgraduate School, 2017-04); NPS-CE-17-042Department of Defense (DoD) software-intensive systems and the software content in other systems will continue to grow and may dominate total ownership costs (TOC) in the future. These costs are exacerbated by the fact ...
Naegle, Brad R. (Monterey, California. Naval Postgraduate School, 2017-04-19); NPS-CE-17-042Department of Defense (DoD) software-intensive systems and the software content in other systems will continue to grow and may dominate total ownership costs (TOC) in the future. These costs are exacerbated by the fact ...