Ada and Beyond Software Policies for the Department of Defense (1997) / Chapter Skim
Currently Skimming:
Software Engineering and the Role of ADA in DOD Systems
Software Engineering and the Role of ADA in DOD Systems
Pages 19-33
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 19... ...
Examples of important developments include advanced tools and techniques such as computer-automated software engineering (CASE) tools, application generators, and object-oriented methods; process improvement, including iterative/spiral development processes, the Software Engineering Institute's Capability Maturity Model, the Air Force Software Development Capability Evaluation, and the ISO 9000 quality standard; product-line management such as architecturedriven processes and components and common operating environments; and technology for 19
|
From page 20... ...
DOD's formulation of an improved policy regarding its use of the Ada programming language should take into consideration the fundamental need for improved software architectures, more effective and mature development processes, and increased process automation. Because DOD's requirements for quality-generally high reliability, state-of-the-art performance, and maintainability by DOD personnel usually cannot be compromised, DOD software development projects often require increased funds and/or extended schedules.
|
From page 21... ...
For example, tools enable reduction of the amount of source code and process improvements; attempts to reduce size lead to process improvements; and improved processes drive too} requirements. These interrelationships mean that even though programming languages do not directly affect project outcomes' they can have significant indirect effects.
|
From page 22... ...
The disadvantages of COTS are not sufficient to peremptorily drop that approach, but they point to areas in which architectural trade-off analysis and risk management approaches will be needed. Improving Software Processes The importance of a mature software development process has been well established (CSTB, 1987; DOD, 1987b)
|
From page 23... ...
Thus, the view that the quality of the software engineering process is independent of the programming language can be misleading. Language standardization has led to tools for automated support of configuration control and increased automation of quality assessment (through interface specification, compilation and consistency analysis, readability, and "inspection automations.
|
From page 24... ...
-GENERATION PROGRAMMING LANGUAGES , ~· . This section provides a brief technical evaluation of the programming languages Ada 95, C, Cal `, and Java, based on the summaries of language features given in Appendix B and focusing specifically on attributes related to the development of real-time critical systems.
|
From page 25... ...
For the foreseeable future, Ada provides the strongest available support for high-assurance, real-time software development. As languages develop attractive new capabilities, DOD should be prepared to periodically perform technical comparisons, such as the one provided here and in Appendix B
|
From page 26... ...
Analyses of language features: comparisons of how the features of programming languages contribute to such desired properties as reliability, maintainability, and efficient programming; 2. Comparisons of empirical data: comparisons based on data collected from completed projects in various languages; and 3.
|
From page 27... ...
and defects per 1,000 source lines of code (defects/KSLOC) is confounded by differences in the expressive power of a source line of code in different programming languages.
|
From page 29... ...
Zeialer cites ~ _ _ A _ ~ ~ , architecture and design, configuration management, testing, process, programmer expertise, and management skills as more significant than the particular programming language used. In summary, based on analysis of available empirical data and comparisons of language features, a conclusion that Ada is superior in ensuring availability, reliability, and fewer defects appears warranted.
|
From page 30... ...
A primary example is Boeing Corporation, which, like DOD, sought a single, common programming language for its commercial mission-critical software (Box 2.11. THE NEED TO INSTITUTE COLLECTION OF DATA FOR SOFTWARE METRICS The committee searched for sources of data that could provide a strong scientific basis for concluding that Ada is or is not a superior programming language in any given application domain.
|
From page 31... ...
The software data that have been collected are largely in proprietary databases held by DOD contractors, consultants, or commercial cost-modeling or marketanalysis firms.
|
From page 32... ...
Without more reliable data, decision making will have only a weak foundation. On an individual project level, DOD has endorsed the concept of using metrics data to improve software process management through its endorsement of the Software Engineering Institute's Capability Maturity Model, which includes quantitative process management as a key process.
|
From page 33... ...
9. No independent evaluations of language features were located by the committee, prompting the analysis presented above in the section titled "Technical Evaluation of Ada 95 and Other Third-Generation Programming Languages" and in Appendix B of this report.
|
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.