DATA ITEM DESCRIPTION Form Approved 2. …

1 data ITEM DESCRIPTIONForm ApprovedOMB reporting burden for collection of this information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources,gathering and maintaining the data needed and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of thiscollection of information, including suggestions for reducing this burden to Washington Headquarters Services, Directorate of Operations and Reports, 1215 Jefferson Davis Highway, Suite1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington , DC TITLESOFTWARE DEVELOPMENT PLAN (SDP)2. IDENTIFICATION NUMBERDI-IPSC-814273.

2 The Software Development Plan (SDP) describes a developer s plans for conducting a softwaredevelopment effort. The term "software development" in this DID is meant to include new development,modification, reuse, reengineering, maintenance, and all other activities resulting in software The SDP provides the acquirer insight into, and a tool for monitoring, the processes to be followed forsoftware development, the methods to be used, the approach to be followed for each activity, and projectschedules, organization, and APPROVAL DATE(YYMMDD)9412055. OFFICE OF PRIMARY RESPONSIBILITYEC6a. DTICAPPLICABLE6b. GIDEPAPPLICABLE7. This data Item DESCRIPTION (DID) contains the format and content preparation instructions for the dataproduct generated by specific and discrete task requirements as delineated in the This DID is used when the developer is tasked to develop and record plans for conducting softwaredevelopment Portions of this plan may be bound separately if this approach enhances their usability.

3 Examples includeplans for software configuration management and software quality The Contract data Requirements List (CDRL) (DD 1423) should specify whether deliverable data are to bedelivered on paper or electronic media; are to be in a given electronic form (such as ASCII, CALS, or compatiblewith a specified word processor or other support software); may be delivered in developer format rather than inthe format specified herein; and may reside in a computer-aided software engineering (CASE) or otherautomated tool rather than in the form of a traditional This DID supersedes DI-MCCR-80030A, DI-MCCR-80297, DI-MCCR-80298, DI-MCCR-80299,DI-MCCR-80300, and APPROVAL LIMITATIONL imited Approval from 12/5/94 through 12/5/969a. APPLICABLE FORMS9b. AMSC NUMBERN707010.

4 PREPARATION General Automated techniques. Use of automated techniques is encouraged. The term "document" in this DIDmeans a collection of data regardless of its Alternate presentation styles. Diagrams, tables, matrices, and other presentation styles are acceptablesubstitutes for text when data required by this DID can be made more readable using these styles.(Continued on Page 2)11. DISTRIBUTION STATEMENTDISTRIBUTION STATEMENT A. Approved for public release; distribution is form 1664, APR 89 Previous editions are obsoletePage 1of 10 Pages135/123 Software Development Plan (SDP)(PDF version)DI-IPSC-8142710. PREPARATION INSTRUCTIONS -- General Instructions (continued)c. Title page or identifier. The document shall include a title page containing, as applicable:document number; volume number; version/revision indicator; security markings or otherrestrictions on the handling of the document; date; document title; name, abbreviation, andany other identifier for the system, subsystem, or item to which the document applies;contract number; CDRL item number; organization for which the document has beenprepared; name and address of the preparing organization; and distribution data in a database or other alternative form , this information shall be included onexternal and internal labels or by equivalent identification Table of contents.

5 The document shall contain a table of contents providing the number,title, and page number of each titled paragraph, figure, table, and appendix. For data ina database or other alternative form , this information shall consist of an internal or externaltable of contents containing pointers to, or instructions for accessing, each paragraph,figure, table, and appendix or their Page numbering/labeling. Each page shall contain a unique page number and display thedocument number, including version, volume, and date, as applicable. For data in adatabase or other alternative form , files, screens, or other entities shall be assignednames or numbers in such a way that desired data can be indexed and Response to tailoring instructions.

6 If a paragraph is tailored out of this DID, the resultingdocument shall contain the corresponding paragraph number and title, followed by "Thisparagraph has been tailored out." For data in a database or other alternative form , thisrepresentation need occur only in the table of contents or Multiple paragraphs and subparagraphs. Any section, paragraph, or subparagraph in thisDID may be written as multiple paragraphs or subparagraphs to enhance Standard data descriptions . If a data DESCRIPTION required by this DID has been publishedin a standard data element dictionary specified in the contract, reference to an entry inthat dictionary is preferred over including the DESCRIPTION of existing documents. Commercial or other existing documents, includingother project plans, may be substituted for all or part of the document if they contain therequired Content requirements.

7 Content requirements begin on the following page. The numbersshown designate the paragraph numbers to be used in the document. Each such number isunderstood to have the prefix " " within this DID. For example, the paragraph numbered understood to be paragraph within this Development Plan (SDP)(PDF version)DI-IPSC-814271. Scope. This section shall be divided into the following This paragraph shall contain a full identification of the system and thesoftware to which this document applies, including, as applicable, identification number(s), title(s),abbreviation(s), version number(s), and release number(s). overview. This paragraph shall briefly state the purpose of the system and thesoftware to which this document applies. It shall describe the general nature of the system andsoftware; summarize the history of system development, operation, and maintenance; identify theproject sponsor, acquirer, user, developer, and support agencies; identify current and plannedoperating sites; and list other relevant overview.

8 This paragraph shall summarize the purpose and contents of thisdocument and shall describe any security or privacy considerations associated with its to other plans. This paragraph shall describe the relationship, if any, of theSDP to other project management Referenced documents. This section shall list the number, title, revision, and date of alldocuments referenced in this plan. This section shall also identify the source for all documentsnot available through normal Government stocking Overview of required work. This section shall be divided into paragraphs as needed toestablish the context for the planning described in later sections. It shall include, as applicable,an overview of:a. Requirements and constraints on the system and software to be developedb.

9 Requirements and constraints on project documentationc. Position of the project in the system life cycled. The selected program/acquisition strategy or any requirements or constraints on ite. Requirements and constraints on project schedules and resourcesf. Other requirements and constraints, such as on project security, privacy, methods,standards, interdependencies in hardware and software development, Plans for performing general software development activities. This section shall be dividedinto the following paragraphs. Provisions corresponding to non-required activities may besatisfied by the words "Not applicable." If different builds or different software on the projectrequire different planning, these differences shall be noted in the paragraphs.

10 In addition to thecontent specified below, each paragraph shall identify applicable risks/uncertainties and plans fordealing with Development Plan (SDP)(PDF version) development process. This paragraph shall describe the software developmentprocess to be used. The planning shall cover all contractual clauses concerning this topic,identifying planned builds, if applicable, their objectives, and the software development activitiesto be performed in each plans for software development. This paragraph shall be divided into thefollowing Software development methods. This paragraph shall describe or reference the softwaredevelopment methods to be used. Included shall be descriptions of the manual and automatedtools and procedures to be used in support of these methods.