D. M. Johnson
Abstract
This report examines the software crisis from a systems engineer's viewpoint. It analyses the key areas of requirements specification, verification and validation and software re-use. It assesses some of the solutions to the crisis proposed by the software engineering community and highlights some of their problems and limitations from the systems engineer's perspective.The report describes how, through the use of computer-aided symbolic specification techniques and simulation, and with an understanding of the software development process, the skilled systems engineer can contribute to the resolution of the software crisis. The skilled systems engineer, can through the use of these techniques and by the application of systems engineering methods and project management skills, reduce the demands placed on software engineers, hence reducing the software engineering effort and also reducing the total development cost.
- 1 W. Royce (1990) "Current Problems." Aerospace Software Engineering Progress in Astronautics and Aeronautics Volume 136 (Eds. Anderson, C. and Dorfman, M.) (AIAA) pp. 5-15.Google Scholar
- 2 C. Anderson and M. Dorfman Preface to Aerospace Software Engineering Progress in Astronautics and Aeronautics Volume 136 (AIAA).Google Scholar
- 3 J. A. McDermid (1992) "Dependable Software - The State of the Art." Proceedings of Aerotech '92 (IMechE/IEE) C428/24/212.Google Scholar
- 4 S. C. Johnson. and R. W. Butler (1992) "Design for Validation." IEEE Aerospace and Electronic Systems January 1992 (IEEE) pp. 38-43.Google Scholar
- 5 E. M. Gray and R. H. Thayer (1991) "Requirements." In Aerospace Software Engineering Progress in Astronautics and Aeronautics Volume 136 (Eds. Anderson, C. and Dorfman, M.) (AIAA) pp. 87-121.Google Scholar
- 6 M. J. D. Brown, Air Vice Marshall (1990) "Rationale for the Development of the UK Defense Standards for Safety-Critical Computer Software." IEEE Aerospace and Electronic Systems November 1990 (IEEE) pp. 31-37.Google Scholar
- 7 B. H. Boar (1984) Application Prototyping: A Requirements Strategy for the 80's. (New York: Wiley-Interscience 1984). Google ScholarDigital Library
- 8 B. W. Boehm (1976) "Software Engineering." IEEE Transactions on Computing Vol. C-25 Dec. 1976 (IEEE) pp. 1226-1241.Google Scholar
- 9 M. L. Metersky (1993) "A Decision-Oriented Approach to System Design and Development." IEEE Transactions on Systems, Man and Cybernetics, Vol. 23 No. 4 July/August 1993 (IEEE) pp. 1024-1037.Google ScholarCross Ref
- 10 A. M. Davis (1992) "Operational Prototyping: A New Development Approach." IEEE Software September 1992 (IEEE) pp. 70- 78. Google ScholarDigital Library
- 11 J. Rea. (1993) "Boeing 777 High Lift Control System." IEEE Aerospace and Electronic Systems August 1993 (IEEE) pp. 15-21.Google Scholar
- 12 T. C. Jones (1984) "Reusability in Programming: A Survey of the State of the Art." IEEE Transactions on Software Engineering September 1984 (IEEE) pp. 488-494.Google ScholarDigital Library
- 13 J. C. Knight (1990) "Testing." Aerospace Software Engineering Progress in Astronautics and Aeronautics Volume 136 (Eds. Anderson, C. and Dorfman, M.) (AIAA) pp. 135-159.Google Scholar
- 14 B. Meyer (1987) "Reusability: The Case for Object Oriented Design." IEEE Software March 1993 (IEEE) pp. 50-64.Google Scholar
- 15 J. E. Kester (1993) "Some Limitations of Object-Oriented Design." IEEE Aerospace and Electronic Systems September 1993 (IEEE) pp. 14-16.Google Scholar
- 16 W. Kozaczynski and A. Kuntzmann-Combelles (1993) "What it Takes to Make OO Work." IEEE Software January 1993 (IEEE) pp. 20-23. Google ScholarDigital Library
- 17 S. Honiden, N. Kotaka and Y. Kishimoto (1993) "Formalizing Specification Modelling in OOA." IEEE Software January 1993 (IEEE) pp. 54-66. Google ScholarDigital Library
- 18 R. Pietro-Diaz and P. Freeman (1987) "Classifying Software for Reusability." IEEE Software January 1993 (IEEE) pp. 6-16.Google Scholar
Index Terms
- The systems engineer and the software crisis
Recommendations
Toward Gamification to Software Engineering and Contribution of Software Engineer
ICMSS 2020: Proceedings of the 2020 4th International Conference on Management Engineering, Software Engineering and Service SciencesWe wish to change developers' behaviors to increase software engineering efficiency and the previous research shows that gamification method can change user's behaviors. Gamification has become a popular topic in many areas including software ...
Bloom's Taxonomy Levels for Three Software Engineer Profiles
STEP '03: Proceedings of the Eleventh Annual International Workshop on Software Technology and Engineering PracticeThis paper is the product of a workshop held in Amsterdam during the Software Technology and Practice Conference (STEP 2003). The purpose of the paper is to propose Bloomýs taxonomy levels for the Guide to the Software Engineering Body of Knowledge (...
What makes a good software engineer?
TRI-Ada '89: Proceedings of the conference on Tri-Ada '89: Ada technology in context: application, development, and deploymentSince the term “software engineering” was coined some 20+ years ago, [4] a number of definitions for both the practice and the practitioner, a “software engineer,” have been proposed. The definition from a recent report on undergraduate software ...
Comments