Quick Form Download

DD Form 2630 — DD Form 2630, Software Description Annotated Outline, August 1992

Software Description Annotated Outline

Download the form

DD Form 2630 is a Department of Defense form, not a service form: DD Form 2630, Software Description Annotated Outline, August 1992, used to Software Description Annotated Outline. The DD prefix is the operative fact. It means one blank serves every military department — Army, Navy, Air Force, Marine Corps, Space Force, Coast Guard under Defense jurisdiction — plus the defense agencies and combatant commands. No branch variant exists.

Requirement traces to not stated; the form belongs to not stated. Everything about schedule sits below that in local instruction, which is where to ask if a date matters.

Current edition is not stated, carried as not stated. Check that against any copy you already hold before doing anything else — Department-level revisions land everywhere simultaneously, so a stale file is stale across the whole Department.

Formats: PDF. Length 4 pages, approximately 183 entries.

Nothing costs anything here. Work in a full desktop pdf application rather than a browser preview; field behaviour in browsers is unreliable.

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.

Edition check comes first, ahead of any entry. Compare the printed date to not stated and replace anything older. Department-level supersession is simultaneous across the services, so a superseded blank is not merely out of date locally; the office receiving it is already working from the new field structure whichever branch it belongs to.

Fill top to bottom. Identification, then substance, then certification — lower fields commonly derive from the header, and completing out of order produces internal contradictions a reviewer will catch.

Nothing stays blank. N/A on an inapplicable item, because an empty box is indistinguishable from a skipped question and the form returns for it. Dates follow the format printed beside the field, not local habit — a joint form is read by clerks in several services with different date conventions, and ambiguity is expensive.

Privacy Act Statement first, personal entries second. It names the authority for the collection, what the data is for, who else routinely sees it, and whether you have to answer at all.

Sign last, in ink or with a credentialed digital signature. A typed name in a signature field certifies nothing. CAC-based signing is the usual electronic method where the receiving system supports it. Date the block immediately — unsigned and undated certifications account for a large share of returns.

Final pass, against the standing defect list: superseded edition, empty mandatory fields, handwriting illegible after scanning, non-conforming dates, missing signature or date. For anything ambiguous in a specific field, the form's own instructions come first and not stated controls where the two differ.

Send it as not stated or local guidance specifies. Save a copy. Cross-service and cross-agency routing is normal for Department forms, and a lost original outside your own organization is harder to chase down.

Related forms are found by number alone. The DD sequence is one unified Department-wide series, so a cited number resolves to exactly one document with no branch qualifier needed.

Do not read across from a service number. DA numbering is Army-specific under an Army proponent; DD numbering is Department-wide under not stated or an equivalent Department office. The sequences are unrelated, so identical digits in each identify two different documents. Read the prefix, not the digits.

Three drivers of revision: directive reissue, altered collection requirements, updated statutory notice text. No notification accompanies any of them, so download fresh and confirm not stated rather than reusing an archived file.

Limits of this page: it distributes a published Department of Defense document and describes it. No legal advice, no procedural ruling, no statement about whether any submission will be accepted. Applicability, eligibility and procedure belong to not stated, to a servicing personnel office, or to the office named 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?
PDF

Other forms in the series