Title: DOD-STD, Version: A, Date: Feb, Status: Cancelled, Desc: DEFENSE SYSTEM SOFTWARE DEVELOPMENT (29 FEB ) [S/S BY. This handbook provides guidance in tailoring DOD-STDA, “Defense System Software Development: for use in concert with DOD-STDA, “DOD. On December 5th, it was superseded by MIL-STD, which merged DOD -STDA, DOD-STDA, and DOD-STD into a single document.
|Published (Last):||14 October 2013|
|PDF File Size:||7.70 Mb|
|ePub File Size:||7.4 Mb|
|Price:||Free* [*Free Regsitration Required]|
Most life cycle models mentioned by Sage and Palmer and Boehm as having the potential to enhance software productivity are highly iterative in nature. In addition to Boehm’s observations regarding the waterfall, it 217a possible to make some other observations about the model.
Boehm asserts that his approach allows evaluation of risk to drive which model is appropriate to follow at any particular stage of the life cycle. On the surface, this figure has a strong resemblance to the waterfall. Following this model, feedback would apparently not sod until system evaluation, at which time it would likely be too late to make an economical correction to the design.
DOD-STD A DEFENSE SYSTEM SOFTWARE DEVELOPMENT
Little concern was given to life cycle, style, or anything other than performance. Figure shows this model. These models have had some impact in the business and academic software development dodd, however, many look to the U.
One of the very first iterative software development life cycles employing prototyping was built around a set of tools and was described by Wasserman and Shewmake Consider the model proposed in Figure If you are a client of PPI or subsidiary company CTI and wish to obtain a username and password, please use the email contact form.
This life cycle model is based on a risk-driven approach to software development, but, according to Boehm, is capable of accommodating other life cycle models as special cases of the spiral. They termed their approach the User Software Engineering methodology with the following steps: The life cycle model which has been most widely used to date is the waterfall model. These enhancements were 1 ddo introduction of feedback loops between adjacent stages onlyand 2 the initiation of prototyping in the form of a parallel step within requirements analysis.
You are authorised to print the contents provided that this copyright notice is included. Figure illustrates the Davis model.
The spiral model is illustrated in Figure This requirements may actually open the “contractual door” for a substantial iteration and rapid prototyping task. This document established “uniform requirements for the software development that are applicable throughout the system life cycle. Evolutionary prototyping is appropriate, however, in some development environments and has a number of proponents in the academic, commercial and government communities e.
As an example of how these additional deliverable documents might be used, Melde, Overmyer, and Trowbridge recently demonstrated how rapid prototyping and system simulation eod be used together in the design of a large-scale interactive information system.
The only model which is not easily derivable from A is the evolutionary model. Overview of the EIA Standard: The reasons for this attention to software productivity issues are clear. Some general improvements over previous government standard life cycles can be seen. One such model is proposed by Davis in which throw-away rapid prototypes are employed at several levels of the life cycle for different purposes.
The knowledge-based system development life-cycle KBSDLC shown in Figure is another prototyping-based software development life cycle used to build knowledge-based systems. Notice that two steps, “test reasoning” and “test knowledge” are unique to this application. The full model is highly detailed, however, a simplified version is illustrated in Figure In addition, this life cycle model employs a variety of tools and techniques which are oriented toward solving problems, as opposed to document production.
Formulate cost-effective strategy for resolving sources of risk e. Figure shows how some of the human factors engineering data items might be required in the context of the DoD-StdA deliverable products schedule, relative to the software development life cycle stages. The fact that the waterfall and A are both document-driven standards, which Boehm has condemned as counter-productive to system developments which are highly interactive, can work both for and against iteration and rapid prototyping, depending on the requirements for the documents to be delivered.
One remedy for this situation is the insertion of iteration within and between various phases of the software life cycle. Several iterative life cycles, most including some form of prototyping have recently emerged.
A much more complete and detailed description of this life cycle can be found in Andriole’s paper. Iteration 21677a described today is much more an active and interactive process.
With the waterfall, the likely solution for such occurrences is a work-around. Form hypothesis that an operational mission can be improved by a software development effort. One particularly appropriate example of an associated discipline is that of human factors engineering.