You are authorised to print the contents provided that this copyright notice is included. Your Alert Profile lists the documents that will be monitored. We apologise for being unable to respond to access requests that are declined. Department of Defense DoD.
|Published (Last):||3 September 2007|
|PDF File Size:||3.86 Mb|
|ePub File Size:||14.14 Mb|
|Price:||Free* [*Free Regsitration Required]|
Automated techniques. Use of automated techniques is encouraged. The term "document" in this DID means a collection of data regardless of its medium. Alternate presentation styles. Diagrams, tables, matrices, and other presentation styles are acceptable substitutes for text when data required by this DID can be made more readable using these styles. Title page or identifier. For data in a database or other alternative form, this information shall be included on external and internal labels or by equivalent identification methods.
Table of contents. 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 in a database or other alternative form, this information shall consist of an internal or external table of contents containing pointers to, or instructions for accessing, each paragraph, figure, table, and appendix or their equivalents.
Each page shall contain a unique page number and display the document number, including version, volume, and date, as applicable. For data in a database or other alternative form, files, screens, or other entities shall be assigned names or numbers in such a way that desired data can be indexed and accessed. Response to tailoring instructions. If a paragraph is tailored out of this DID, the resulting document shall contain the corresponding paragraph number and title, followed by "This paragraph has been tailored out.
Multiple paragraphs and subparagraphs. Any section, paragraph, or subparagraph in this DID may be written as multiple paragraphs or subparagraphs to enhance readability.
Standard data descriptions. If a data description required by this DID has been published in a standard data element dictionary specified in the contract, reference to an entry in that dictionary is preferred over including the description itself.
Substitution of existing documents. Commercial or other existing documents, including other project plans, may be substituted for all or part of the document if they contain the required data Content requirements begin on the following page. The numbers shown designate the paragraph numbers to be used in the document. Each such number is understood to have the prefix " For example, the paragraph numbered 1. This section shall be divided into the following paragraphs. This paragraph shall contain a full identification of the system and the software to which this document applies, including, as applicable, identification number s , title s , abbreviation s , version number s , and release number s.
This paragraph shall briefly state the purpose of the system and the software to which this document applies. It shall describe the general nature of the system and software; summarize the history of system development, operation, and maintenance; identify the project sponsor, acquirer, user, developer, and support agencies; identify current and planned operating sites; and list other relevant documents.
This paragraph shall summarize the purpose and contents of this document and shall describe any security or privacy considerations associated with its use. This paragraph shall describe the relationship, if any, of the SDP to other project management plans. Referenced documents. This section shall list the number, title, revision, and date of all documents referenced in this plan.
This section shall also identify the source for all documents not available through normal Government stocking activities. Overview of required work. This section shall be divided into paragraphs as needed to establish 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 developed b. Requirements and constraints on project documentation c. Position of the project in the system life cycle d. Requirements and constraints on project schedules and resources f. Other requirements and constraints, such as on project security, privacy, methods, standards, interdependencies in hardware and software development, etc.
Plans for performing general software development activities. Provisions corresponding to non-required activities may be satisfied by the words "Not applicable. This paragraph shall describe the software development process to be used. The planning shall cover all contractual clauses concerning this topic, identifying planned builds, if applicable, their objectives, and the software development activities to be performed in each build. This paragraph shall be divided into the following subparagraphs.
This paragraph shall describe or reference the software development methods to be used. Included shall be descriptions of the manual and automated tools and procedures to be used in support of these methods. The methods shall cover all contractual clauses concerning this topic. Reference may be made to other paragraphs in this plan if the methods are better described in context with the activities to which they will be applied.
This paragraph shall describe or reference the standards to be followed for representing requirements, design, code, test cases, test procedures, and test results. The standards shall cover all contractual clauses concerning this topic. Reference may be made to other paragraphs in this plan if the standards are better described in context with the activities to which they will be applied.
Standards for code shall be provided for each programming language to be used. They shall include at a minimum: a. Standards for format such as indentation, spacing, capitalization, and order of information b. Standards for other comments such as required number and content expectations d. Naming conventions for variables, parameters, packages, procedures, files, etc. Restrictions, if any, on the use of programming language constructs or features f.
Restrictions, if any, on the complexity of code aggregates 4. This paragraph shall describe the approach to be followed for identifying, evaluating, and incorporating reusable software products, including the scope of the search for such products and the criteria to be used for their evaluation.
It shall cover all contractual clauses concerning this topic. Candidate or selected reusable software products known at the time this plan is prepared or updated shall be identified and described, together with benefits, drawbacks, and restrictions, as applicable, associated with their use.
This paragraph shall describe the approach to be followed for identifying, evaluating, and reporting opportunities for developing reusable software products.
This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for handling requirements designated critical. The planning in each subparagraph shall cover all contractual clauses concerning the identified topic.
DI-IPSC-81427A, DATA ITEM DESCRIPTION: SOFTWARE DEVELOPMENT PLAN (SDP) (10 JAN 2000)
Ganos Proceed to Checkout Continue Shopping. This standard is not included in any packages. Your Alert Profile lists the documents that will be monitored. It is recommended that you use Adobe Reader v7. We have no document history for this standard.