DOD 2167A PDF

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.

Author: Kajilkree Dozragore
Country: Rwanda
Language: English (Spanish)
Genre: Technology
Published (Last): 21 November 2010
Pages: 438
PDF File Size: 15.65 Mb
ePub File Size: 15.64 Mb
ISBN: 171-8-58708-214-3
Downloads: 72929
Price: Free* [*Free Regsitration Required]
Uploader: Taurg

DOD-STD-2167

In addition, there 2167z a variety of new requirements for development aids and software engineering methods which are not particularly germane to this discussion. This model is based on the premise that a life cycle is a living model with multiple disciplines and multiple, reconfigurable steps which are inherently iterative.

The figure caption accompanying the figure from the standard, however, is “Figure 1. The waterfall model is most commonly attributed to Royce and appears as shown in Figure Evaluate alternatives with respect to objectives and constraints. This model, however, provides even more opportunity to overcome 216a7 difficulties present in waterfall developments by instantiating even more levels of iteration, innovative specification and cross-level communication. A username and password is required for access to the resources.

No mention is made of the potential for uncovering hardware and software architectural problems via a prototype of the user interface, 21677a the potential to iterate past one or more levels in order to alleviate the problem.

Ddo often resulted in so-called spaghetti code, which might have worked, but ddo almost impossible to maintain or enhance.

During the evolutionary prototyping process, much more attention must be paid to maintainability, reliability and robustness of software. Assessment is made regarding the compatibility of the standard with innovative requirements techniques, and how and where these techniques may be inserted into the life cycle.

  MABEL CONDEMARIN LIBROS PDF

Generally, a cycle of the spiral proceeds as follows: Most life cycle models mentioned by Sage and Palmer and Boehm as having the potential to enhance software productivity are highly iterative in nature. One of the most interesting departures from document-driven life cycles is that of Boehm’s spiral model of software development and enhancement.

This requirements may actually open the “contractual door” for a substantial iteration and rapid prototyping task. Evolutionary prototyping is appropriate, however, in some development environments and has a number of proponents in the academic, commercial and government communities e.

Finally, and most importantly for this discussion, Boehm asserts that partial implementations of the spiral are adaptable to most current models and are particularly helpful in reducing project risk. The developers then pick up the prototyping activity to aid in software requirements elicitation and validation, requirements are extracted from this version of the prototype and used to produce the Software Requirements Specification DI-MCCRA.

As can be seen in FigureBoar’s model is not a complete life cycle and ignores some important issues such as specification and software design.

DOD-STD-2167A

If you are not a client of PPI or CTI, limited access which permits download access to many 2176a these resources may be available on an approved-registration basis.

Views Read Edit View history. Contracting for Quality EEE Attention to these issues during prototype development necessarily requires more time and effort, leading to a greater inter-iteration interval.

Third, the spiral model needs further elaboration. Unfortunately, each of these standard life cycle models have inherited many of the same problems. Hear about relevant training courses in your area. One criticism of the standard was that it was biased toward the Waterfall Model. In addition, tailoring of most of these DIDs is allowed, with approval of the procuring organization. Little concern was given to life cycle, style, or anything other than performance.

DOD-STD – Wikipedia

Figure illustrates the Davis model. 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.

  BR M770 PDF

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. Society for Computer Simulation. According to Boehmthe waterfall was a refinement of an earlier model known as the “stagewise” model and provided at least two major enhancements to earlier models. Boehm also states, however, that the waterfall is not particularly good for many types of systems, particularly interactive ones in which end-users participate in design activities.

Armstrong Aerospace Medical Research Laboratory. Although this is not the first iterative model described in the literature, it is probably one of the most widely referenced.

This is not necessarily, however, the precise nature of the model to be used by government contractors dd software developers. Search SE Goldmine Search this site: This created problems matching design documents to the actual product. From Wikipedia, the free rod.

United States Department of Defense standards documents disestablishments in the United States. Iteration as described today is much more an active and interactive process. 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.

Form hypothesis that an operational mission can be improved by a software development effort. One remedy for this situation is the insertion of iteration within and between various phases of the software life cycle.