Start here if you have been told to submit DD Form 2630. First, know what you are filling: Software Description Annotated Outline. The document is titled DD Form 2630, Software Description Annotated Outline, August 1992.
Next, check the edition. You want not stated, currently carried as not stated by the publisher. Then confirm the form applies to you — this is a Department of Defense form, so you use it whether you serve in the Army, Navy, Air Force, Marine Corps, Space Force or Coast Guard under Defense jurisdiction.
Once you know the form fits, find out when you file it. not stated sets the requirement, and not stated maintains the form itself. Your own command or agency adds local timing on top of that, so ask your administrative office if the deadline matters to you.
Before you download, pick your approach — editable file or printed page. What follows covers the formats first, then the entries, then what you do afterward.
Now fill it in. Work from the top of the page downward, and do not jump ahead — the identifying block comes first, the substance of your entry second, the certification last. Later boxes often depend on what you put at the top.
Check the edition before you type a word. The date appears on the face of the form; it should read not stated. When it does not, discard the file and take a fresh copy from this page. Department-level revisions replace the blank across all services simultaneously, which means an old printout can be out of step everywhere.
For questions about a specific entry, check the form's own instructions, and if that does not settle it, open not stated. The directive controls where they differ.
Download the form
Begin by choosing a file. Available here: PDF. Plan for 4 pages and about 183 entries.
Download the pdf first. After it opens, test a field with your cursor. Fillable means you type, tab to the next box, and save your work inside the file. Printable means the page is a flat blank, so print it and write your answers in ink.
Go with the typed route whenever the choice is yours. Consider what happens after you submit: the copy gets scanned, forwarded and filed, and each pass costs handwriting some legibility. Block letters help if you are stuck with a pen.
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.
Submit the completed form through the channel not stated or your local guidance specifies. Save a copy for yourself before it leaves your hands, whether that means a scan, a photograph or a duplicate file.
If the form points you to another document, you can find it by number alone. DD numbering runs across the whole Department, so you do not need to work out which service issued it — one number, one form, everywhere.
Be careful when a procedure pairs this form with a service form. Read the prefix, not just the digits. Service forms answer to a service proponent, while DD forms answer to not stated or an equivalent Department office, and the two sequences were never aligned. Grabbing the wrong prefix gets you a form that has nothing to do with your task.
Do not archive this file and reuse it in a year. Forms are reissued as directives are revised, as data requirements shift, and as statutory notice text is amended. Your protection is simple: download fresh each time and confirm the edition date.
Before you go, note what is not covered here. You have the blank form and instructions for completing it; you do not have legal guidance, and no statement on this page determines what any office will do with your submission. Direct those questions to not stated, to the personnel office that serves you, or to the office designated 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?