Download the form
Department of Defense form 2630. Official designation: DD Form 2630, Software Description Annotated Outline, August 1992. Purpose: Software Description Annotated Outline. Current edition not stated, status not stated.
Issued under not stated, with not stated as proponent. A DD number marks a Department-wide instrument: the same blank form serves every military department and the defense agencies, rather than one service alone.
Users include uniformed members of any branch, DoD civilian employees, contractor personnel where authorized, and the administrative staff who process the completed record.
Timing of submission is fixed by not stated and by the implementing guidance of the submitting organization. What follows describes the blank document, not agency procedure.
Formats offered: PDF. Length: 4 pages. Fillable field count: roughly 183.
Distribution centres on pdf. Two states exist: fillable, where field boxes accept keyboard input and retain it, and printable, a static blank produced for manual completion. Typed data reproduces cleanly across copies; handwritten data depends on the writer.
What the form asks for
- Section I - Top-level characteristics (above CSCI level). 1. System requirement volatility. a. Level of definition and understanding of system requirements. Press space bar to mark X in first box if very little, second box if questionable, third box if fairly complete, or fourth box if very complete.
- b. How will overall technology advances during development affect the project? X first box if significant advances, second box if between one and three significant modifications, third box if minor modifications, or fourth box if no changes to system or requirements.
- c. Requirements volatility during development. X first box if no changes, second box if small noncritical changes, third box if frequent noncritical changes, fourth box if occasional moderate changes, fifth box if frequent moderate changes, or sixth box if many large changes.
- Additional comments.
- 2. System integration difficulty. a. Expected level of difficulty of integrating and testing the CSCI's to the element level. X first box if very little integration, no complex interfaces, second box if average degree of system integration/interface complexity, third box if several system interfaces, some complex, or fourth box if complex, time-intensive integration process anticipated.
- Additional comments.
- 3. Use of commercial off-the-shelf software. a. Expected impact of integrating software into the system. X first box if some impacts on the design/development effort, second box if few impacts created by the COTS software packages, or third box if no impacts.
- Additional comments.
- Additional comments.
- 4. Software size estimate of CSCIs. (1) Mode. a. Space.
- (2) Total KSLOC estimate: low.
- Most likely.
- High.
- (3) Percent new SLOC.
- (4) Percent reused SLOC.
- (5) Percent modified SLOC.
- (6) Programming languaged used.
- (7) Basis of size estimate (analogy, function points, other).
- (8) Reuse library percent.
- (1) Mode. b. Air.
- (2) Total KSLOC estimate: low.
- Most likely.
- High.
- (3) Percent new SLOC.
Completion runs in the order printed on the page: identifying data at the head, the body of the entry next, certification at the foot. Header data frequently governs what belongs in the fields below it.
Edition in use: not stated. Because DD forms are revised at Department level and distributed to all services at once, an obsolete printing may not match the fields an office expects. The date is printed on the form face.
Instructions printed on the form or in not stated govern individual field entries. Where the two differ, the governing publication controls.
Once executed, routing follows not stated and the submitting organization's own instruction. Keeping a copy is standard.
Related documents are located by series and number. DD forms sit in a single Department-wide sequence, so a form referenced inside DD Form 2630 is normally found by its number alone, without regard to service.
Some procedures pair a DD form with a service form. The two numbering systems are separate — service forms answer to a service proponent, DD forms to not stated or another Department office — and a matching number in each system means nothing.
Revision occurs when the prescribing directive is reissued, when the data collected changes, or when statutory notice language is amended. Verification of the edition date at download addresses all three.
The material here is descriptive. Nothing on the page constitutes legal or procedural advice, and no statement here determines whether a submitted form will be accepted. Such questions go to not stated, a servicing administrative office, or the authority identified in not stated.
Questions and answers
- What is DD Form 2630?
- DD Form 2630, Software Description Annotated Outline, August 1992
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?