Ada and Beyond Software Policies for the Department of Defense (1997) / Chapter Skim
Currently Skimming:
Implementation of Recommended DOD Software Policy
Implementation of Recommended DOD Software Policy
Pages 53-61
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 53... ...
. The third level specifies circumstances under which Ada is required for software development using a third-generation programming language (3GL,)
|
From page 54... ...
4. Software development will emphasize good software engineering practice, including the application of management techniques, methodologies, support tools, metrics, and appropriate programming languages.
|
From page 55... ...
are generally preferable to machine or assembly language; further, fourth-generation programming languages (4GLs) ' program generators, graphical user interface builders, and database query languages, such as Structured Query Language (SQL)
|
From page 56... ...
, but this type of assessment focuses more on organizational process maturity than on specific technical decisions made by a particular project. Another approach was to add review of programming language and software engineering decisions to the Defense Acquisition Board (DAB)
|
From page 57... ...
software engineering common practices, SEPR evaluation criteria, and SEPR process policies developed at the service and command levels (these would be specific to each service, and possibly to PEOs who could, for example, require conformance to particular architectural frameworks for a class of systems (e.g., a particular level of a common operating environment)
|
From page 58... ...
Stakeholder Role The committee recommends that the SAEs be in charge of carrying out the SEPR process at the DOD service level. The SAEs would establish milestones for the SEPR process, appoint expert reviewers and stakeholder representatives, and establish criteria for evaluation.
|
From page 59... ...
research, the committee recommends that the DDR&E establish a software engineering review process that addresses issues pertinent to the efficient transition of software technologies associated with major 6.3a demonstration programs, including plans to modify prototype 6.3a software to conform to the committee's recommended policy on selection of programming language, as appropriate. The review criteria, which would be at the discretion of the DDR&E, would not need to use the SEPR process, thus enabling the DDR&E to manage the trade-off between efficient transitions, on the one hand, and responsiveness and flexibility of research programs to the emergence of new technologies and concepts, on the other.
|
From page 60... ...
; and · Choice of programming language, subject to the recommended policy in Appendix A Software Engineering Codes As experience is gained, SAEs, PEOs, and other stakeholders will develop service-specific or domain-specif~c refinements of the review criteria listed in the previous section.
|
From page 61... ...
2. The committee recommends using the term "software engineering plan reviews" rather than "architecture reviews" to emphasize the importance of integrating plans for products (i.e., architecture or building plan)
|
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.