DI-AVCS-80491B

Computer Software Flowchart

The Computer Software Flowchart describes preparation requirements for flowcharts that provide graphic portrayals of the logic design and logic steps that computer software follows.

Approval DateOctober 26, 2022

AMSC Number7636

Preparing Activity—

Project NumberAVCS-2023-001

OPRNS (B81)

DTIC ApplicableNo

GIDEP ApplicableNo

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantYes

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

DI-MCCR-80491A

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The Computer Software Flowchart describes preparation requirements for flowcharts that provides graphic portrayals of the logic design and logic steps that computer software follows.

This Data Item Description (DID) contains format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

This DID supersede DI-MCCR-80491A.

Preparation Instructions

1Reference documents.The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as cited in the current issue of the DODISS at the time of solicitation; or for non-DODISS-listed documents, as stated herein.

2General requirements.

2.1Functional flowchart.Depict overall logic design, operation, and information flow. Limit to one page, when possible.

2.2General flowchart.Depict major logic steps, operations, and information flow. Limit to two pages and not more than 30 representative symbols.

2.3Detailed flowchart.Depict processing being performed in the sequence of operation and all branch and decision points which fulfill the objectives of each of the major logic steps shown in the general flowchart.

2.3.1Duplicate instructions.Depict duplication sets of instructions for a procedure by a single sequence of symbols with appropriate annotations.

3Format.

3.1Functional and general flowcharts.Prepared on one side only of white bond paper 8 1/2 x 11 inches with a 1 1/4 inch margin on left side and minimum of 3/4 inch margin on all other sides.

3.2Detailed flowcharts.Prepared on two sizes of paper. First size is prepared in accordance with 3.1. Second size prepared on 22 x 34 inch paper and includes all flow on one chart.

3.3Identification.All flowcharts shall contain the following identification on upper right hand corner of page.

3.3.1Program number.

3.3.2Program name.

3.3.3Programmer's name.

3.3.4Date and revision number.

3.3.5Description.

3.4Number of pages.The page number (and total number of pages) shall be applied in center of lower margin.

3.5Table of contents.Used for multiple page flowcharts. Indicates each program included in the document and shall divide each into its separate activities, showing page locations and name of each activity and program.

4Flowcharting standards.Flowcharting symbols shall conform to ANSI X3.5 with the following exceptions.

4.1Flow-line symbols.Flowcharts shall use the following flow-line symbols for clarity.

4.2Annotation symbol.Used as follows:

4.2.1Functional flowchartsOn functional flowcharts to further clarify the significance of a symbolic function.

4.2.2General flowchartsOn general flowcharts to provide direct linkage with the detailed flowchart(s)

4.2.3Flowchart symbolWith a flowchart symbol, when it is impractical to include explanatory information within the designated symbol.

4.3Magnetic tape symbol.Shall contain information to identify the type of information contained and its name.

4.4Communication link symbol.Depicted by use of open arrowheads for each time symbol is used.

4.5Predefined process symbol.Contains name and page location of the process and a brief description.

4.6Connector symbol.Entry connectors shall be the first symbol of each page and shall conform to the requirements of 10.5.

5Symbol identification and cross references.Identifies and, when applicable, cross references each symbol; i.e., connector and striped symbols.

5.1Identification notationIdentification notation used on detailed flowcharts(s) shall relate directly to program labels as specified by Computer Software Coding Standards specified in the contract.

References

—

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer