Exhibit B-DIDs.pdf

For the best experience, open this PDF portfolio in

Acrobat X or Adobe Reader X, or later.

Get Adobe Reader Now!

http://www.adobe.com/go/reader

DATA ITEM DESCRIPTION

Title: Software Development Plan (SDP)

Number: DI-IPSC-81427B Approval Date: 20170313

AMSC Number: N9775 Limitation: N/A

DTIC Applicable: No GIDEP Applicable: No

Preparing Activity: EC Project Number: IPSC-2017-001

Applicable Forms: N/A

Use/relationship: The Software Development Plan (SDP) with Agile, Cyber Security and Safety

Assurance contains the format, content, and delivery timeframes for the SDP. The SDP provides the acquirer insight into, and a tool for monitoring, the processes to be followed for software development, the methods to be used, the approach to be followed for each activity, and project schedules, organization, and resources. This DID is useful for new development, modification, reuse, reengineering, maintenance, and other activities resulting in software products.

This Data Item Description contains the format, content, and intended use information for the data product resulting from the work task described by the contract.

This DID supersedes DI-IPSC-81427A.

Requirements:

1. 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. The complete address or website or other conditions for availability will be described.

2. Format. The SDP shall adhere to the format described under Content.

3. Content:

3.1. Identification. 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).

3.2. System overview. 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.

Source: http://assist.dla.mil -- Downloaded: 2022-10-26T16:43Z Check the source to verify that this is the current version before use.

DI-IPSC-81427B

3.3. Document overview. This paragraph shall summarize the purpose and contents of this document and shall describe any security or privacy considerations associated with its use.

3.4. Relationship to other plans. This paragraph shall describe the relationship, if any, of the

SDP to other project management plans.

3.5. 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. The selected program/acquisition strategy or any requirements or constraints on it

e. 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.

3.6. Plans for performing general software development activities. This section shall be divided into the following paragraphs. Provisions corresponding to non-required activities may be satisfied by the words "Not applicable." If different builds or different software on the project require different planning, these differences shall be noted in the paragraphs. In addition to the content specified below, each paragraph shall identify applicable risks/uncertainties and plans for dealing with them.

a. Software development process. 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 include why the approach was chosen and provide a description of previous experience in developing software of the same nature as being acquired.

b. If the software development process is an Agile process, the following must be addressed within this section or subsection(s):

1. Cite the Agile technique(s) being employed (Scrum, pair programming, extreme programming, etc.).

2. For each Agile technique employed, describe your approach.

3. Describe the approach for release planning.

4. For Scrum, identify the sprint length and how it was determined.

5. Describe how the backlog is initially established, and the process for modifying and re-prioritizing it.

6. For Scrum, describe the typical sprint activities, and what happens during each iteration.

7. Identify the Product Owner and his/her roles/responsibilities.

8. Describe the acquirer’s role in the sprints if the customer is not also the

Product Owner.

9. Describe the mechanism for getting acquirer ( or end user) feedback for each sprint.

10. Describe how the product (working, useful piece of software) will be demonstrated to the Product Owner after each sprint (e.g., live demo on real equipment, in the lab with sim/stim, PowerPoint slides, etc.).

11. Describe the handling of incomplete user stories, unsatisfactory user stories, and bugs, and how they are factored back into the backlog.

12. Describe your Configuration Management process for keeping track of which user stories passed without any rework needed, which require rework, and which failed.

13. Describe your approach to artifact delivery; when documents such as the SRS, SDD, Software Test Plan and System Integration Plan will be available.

14. Discuss your approach to refactoring.

15. List and describe the software metrics to be used.

16. Discuss your approach to paying off technical debt.

17. Describe how you will determine story points for the velocity metric.

18. Describe your Integrated Requirements Toolset (IRT) that traces user stories to mission threads and KPPs, and whether this is a commercial tool or a tool developed by your organization.

19. Describe how software development activities will be coordinated with the

Integration and Test (I&T) team, and how it will be assured that the I&T team can keep up with testing all the software releases.

20. Describe how sprint-to-sprint dependencies (related to product and development resources) will be resolved and factored into the Sprint/Release

Plan.

21. Describe your strategy/mechanism for keep multiple sprint teams in sync.

22. Describe how the integrity of the baseline is maintained for use in the development of the next sprint.

23. Describe how regression testing will be conducted for each sprint release for all previous functions released.

24. Describe how automated testing techniques will be used for sprint and/or regression testing.

25. Describe how the software development effort will be synchronized and coordinated with systems engineering activities and reviews.

3.7. General plans for software development. This paragraph shall be divided into the following subparagraphs.

a. Software development methods. 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.

b. Standards for software products. 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:

1. Standards for format (such as indentation, spacing, capitalization, and order of information)

2. Standards for header comments (requiring, for example, name/identifier of the code; version identification; modification history; purpose; requirements and design decisions implemented; notes on the processing (such as algorithms used, assumptions, constraints, limitations, and side effects); and notes on the data (inputs, outputs, variables, data structures, etc.)

3. Standards for other comments (such as required number and content expectations)

4. Naming conventions for variables, parameters, packages, procedures, files, etc.

5. Restrictions, if any, on the use of programming language constructs or features

6. Restrictions, if any, on the complexity of code aggregates

c. Reusable software products. This paragraph shall be divided into the following subparagraphs.

1. Incorporating reusable software products. 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.

2. Developing reusable software products. This paragraph shall describe the approach to be followed for identifying, evaluating, and reporting opportunities for developing reusable software products. It shall cover all contractual clauses concerning this topic.

d. Handling of critical requirements. 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.

1. Safety Assurance

a. Software Requirements

b. System Software Architecture and Software Preliminary Design

c. Software Detailed Design

d. Software Coding and Unit Test

e. Computer Software Component (CSC) Integration and Test

f. Computer Software Configuration Item (CSCI) Formal Qualification

Test (FQT)

g. Subsystem Integration and Test

h. System Qualification Test

2. Cyber-Security / Software Assurance

a. Software Requirements

b. System Software Architecture and Software Preliminary Design

c. Software Detailed Design

d. Software Coding and Unit Test

e. CSC Integration and Test

f. CSCI FQT

g. Subsystem Integration and Test

h. System Qualification Test

i. Describe the mechanism to address constant emerging cyber-security requirements.

1. Assurance of other critical requirements

f. Computer hardware resource utilization. This paragraph shall describe the approach to be followed for allocating computer hardware resources and monitoring their utilization. It shall cover all contractual clauses concerning this topic.

g. Recording rationale. This paragraph shall describe the approach to be followed for recording rationale that will be useful to the support agency for key decisions made on the project. It shall interpret the term "key decisions" for the project and state where the rationales are to be recorded. It shall cover all contractual clauses concerning this topic.

h. Access for acquirer review. This paragraph shall describe the approach to be followed for providing the acquirer or its authorized representative access to developer and subcontractor facilities for review of software products and activities. It shall cover all contractual clauses concerning this topic.

3.8. Plans for performing detailed software development activities. This section shall be divided into the following paragraphs. Provisions corresponding to non-required activities may be satisfied by the words "Not applicable." If different builds or different software on the project require different planning, these differences shall be noted in the paragraphs. The discussion of each activity shall include the approach (methods/procedures/tools) to be applied to: 1) the analysis or other technical tasks involved; 2) the recording of results; and, 3) the preparation of associated deliverables, if applicable. The discussion shall also identify applicable risks/uncertainties and plans for dealing with them.

a. Project planning and oversight. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for project planning and oversight. The planning in each subparagraph shall cover all contractual clauses regarding the identified topic.

1. Software development planning (covering updates to this plan)

2. CSCI test planning

3. System test planning

4. Software installation planning

5. Software transition planning

6. Following and updating plans, including the intervals for management review

b. Establishing a software development environment. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for establishing, controlling, and maintaining a software development environment. The planning in each subparagraph shall cover all contractual clauses regarding the identified topic.

1. Software engineering environment

2. Software test environment

3. Software development library

4. Software development files

5. Non-deliverable software

6. Software assurance considerations, including on tool selection

c. System requirements analysis. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for participating in system requirements analysis. The planning in each subparagraph shall cover all contractual clauses regarding the

1. Analysis of user input

2. Operational concept

3. System requirements

d. System design. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for participating in system design. The planning in each subparagraph shall cover all contractual clauses regarding the identified topic.

1. System-wide design decisions

2. System architectural design

e. Software requirements analysis. This paragraph shall describe the approach to be followed for software requirements analysis. The approach shall cover all contractual clauses concerning this topic.

f. Software design. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for software design. The planning in each subparagraph shall cover all contractual clauses regarding the identified topic.

1. CSCI-wide design decisions

2. CSCI architectural design

3. CSCI detailed design

g. Peer Review. This paragraph shall describe the peer review process covering: System requirements, system design, software requirements, software design, software implementation and software testing.

h. Coding Standards. This paragraph shall describe the uniform set of rules and guidelines of the project and organization used for software development. This shall include standards for the creation and sustainment of secure systems.

i. Software implementation and unit testing. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for software implementation and unit testing. The planning in each subparagraph shall cover all contractual clauses regarding the identified topic.

1. Software implementation

2. Preparing for unit testing

3. Performing unit testing

4. Revision and retesting

5. Analyzing and recording unit test results

j. Unit integration and testing. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for unit integration and testing. The

1. Preparing for unit integration and testing

2. Performing unit integration and testing

3. Revision and retesting

4. Analyzing and recording unit integration and test results

k. CSCI qualification testing. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for CSCI qualification testing. The

1. Independence in CSCI qualification testing

2. Testing on the target computer system

3. Preparing for CSCI qualification testing

4. Dry run of CSCI qualification testing

5. Performing CSCI qualification testing

6. Revision and retesting

7. Analyzing and recording CSCI qualification test results

l. CSCI/HWCI integration and testing. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for participating in CSCI/HWCI integration and testing. The planning in each subparagraph shall cover all contractual clauses regarding the identified topic.

1. Preparing for CSCI/HWCI integration and testing

2. Performing CSCI/HWCI integration and testing

3. Revision and retesting

4. Analyzing and recording CSCI/HWCI integration and test results

m. System qualification testing. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for participating in system qualification testing. The planning in each subparagraph shall cover all contractual clauses regarding the

1. Independence in system qualification testing

2. Testing on the target computer system

3. Preparing for system qualification testing

4. Dry run of system qualification testing

5. Performing system qualification testing

6. Revision and retesting

7. Analyzing and recording system qualification test results

8. Describe the process to allow access by the government to the results of this code evaluation on a real-time basis and shall address the use of automated code analyzers and documented peer review process.

n. Preparing for software use. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for preparing for software use. The

1. Preparing the executable software

2. Preparing version descriptions for user sites

3. Preparing user manuals

4. Installation at user sites

o. Preparing for software transition. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for preparing for software transition. The

1. Preparing the executable software

2. Preparing source files

3. Preparing version descriptions for the support site

4. Preparing the "as built" CSCI design and other software support information

5. Updating the system design description

6. Preparing support manuals

7. Transition to the designated support site

8. Details for proposed evaluation of code quality and removal of defects before the code leaves the hands of the software developers to the system integrators. This includes conformance to coding standards, as well as problems such as dead code, memory leaks and unreachable code

p. Software configuration management. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for software configuration management. The planning in each subparagraph shall cover all contractual clauses regarding the

1. Configuration identification

2. Configuration control

3. Configuration status accounting

4. Configuration audits

5. Packaging, storage, handling, and delivery

q. Software product evaluation. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for software product evaluation. The

1. In-process and final software product evaluations

2. Software product evaluation records, including items to be recorded

3. Independence in software product evaluation

r. Software quality assurance. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for software quality assurance. The

1. Software quality assurance evaluations

2. Software quality assurance records, including items to be recorded

3. Independence in software quality assurance

s. Corrective action. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for corrective action. The planning in each subparagraph shall cover all contractual clauses regarding the identified topic.

1. Problem/change reports, including items to be recorded (candidate items include project name, originator, problem number, problem name, software element or document affected, origination date, category and priority, description, analyst assigned to the problem, date assigned, date completed, analysis time, recommended solution, impacts, problem status, approval of solution, follow-up actions, corrector, correction date, version where corrected, correction time, description of solution implemented)

2. Corrective action system

t. Joint technical and management reviews. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for joint technical and management reviews. The planning in each subparagraph shall cover all contractual clauses regarding the identified topic.

1. Joint technical reviews, including a proposed set of reviews

2. Joint management reviews, including a proposed set of reviews

u. Other software development activities. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for other software development activities. The planning in each subparagraph shall cover all contractual clauses regarding the

1. Risk management, including known risks and corresponding strategies

2. Software management indicators, including indicators to be used

3. Security and privacy

4. Subcontractor management

5. Interface with software independent verification and validation (IV&V) agents

6. Coordination with associate developers

7. Improvement of project processes

8. Other activities not covered elsewhere in the plan

v. Schedules and activity network. This section shall present:

1. Schedule(s) identifying the activities in each build and showing initiation of each activity, availability of draft and final deliverables and other milestones, and completion of each activity

2. An activity network, depicting sequential relationships and dependencies among activities and identifying those activities that impose the greatest time restrictions on the project

3.9. Project organization and resources. This section shall be divided into the following paragraphs to describe the project organization and resources to be applied in each build.

a. Project organization. This paragraph shall describe the organizational structure to be used on the project, including the organizations involved, their relationships to one another, and the authority and responsibility of each organization for carrying out required activities. This paragraph shall also include the definition of Systems Engineering, Software Engineering, Integrated Product and Process Development, and processes for the Division(s) responsible for the development and the principle sub-contractors responsible for software development, as applicable.

b. Project resources. This paragraph shall describe the resources to be applied to the project.

This section shall include a description of the extent to which personnel who contributed to these previous efforts using these processes will be supporting this development effort. It shall include:

1. Personnel resources, including:

a. The estimated staff-loading for the project (number of personnel over time)

b. The breakdown of the staff-loading numbers by responsibility (for example, management, software engineering, software testing, software configuration management, software product evaluation, software quality assurance)

c. A breakdown of the skill levels, geographic locations, and security clearances of personnel performing each responsibility

2. Overview of developer facilities to be used, including geographic locations in which the work will be performed, facilities to be used, and secure areas and other features of the facilities as applicable to the contracted effort.

3. Acquirer-furnished equipment, software, services, documentation, data, and facilities required for the contracted effort. A schedule detailing when these items will be needed shall also be included.

4. Other required resources, including a plan for obtaining the resources, dates needed, and availability of each resource item.

3.10. Notes. This section shall contain any general information that aids in understanding this document (e.g., background information, glossary, rationale). This section shall include an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document and a list of any terms and definitions needed to understand this document.

3.11 Appendixes. Appendixes may be used to provide information published separately for convenience in document maintenance (e.g., charts, classified data). As applicable, each appendix shall be referenced in the main body of the document where the data would normally have been provided. Appendixes may be bound as separate documents for ease in handling. Appendixes shall be lettered alphabetically (A, B, etc.).

End of DI-IPSC-81427B

Source: http://assist.dla.mil -- Downloaded: 2022-10-26T16:46Z

Title: SOFTWARE DESIGN DESCRIPTION (SDD)

Number: DI-IPSC-81435B Approval Date: 20211122

AMSC Number: N10191 Limitation: None

DTIC Applicable: No GIDEP Applicable: No

Preparing Activity: EC Project Number: IPSC-2020-002

Applicable Forms: None

Use/Relationship

1. The Software Design Description (SDD) describes the design of a Computer

Software Configuration Item (CSCI). It describes the CSCI-wide design decisions, the

CSCI architectural design, and the detailed design needed to implement the software. The

SDD may be supplemented by Interface Design Descriptions (IDDs) (DI-IPSC-81436) and

Database Design Descriptions (DBDDs) (DI-IPSC-81437).

1.1. The SDD, with its associated IDDs and DBDDs, is used as the basis for implementing the software. It provides the acquirer visibility into the design and provides information needed for software support.

2. This Data Item Description (DID) contains the format, content, and intended use information for the data product resulting from the work task described in the contract statement of work (SOW).

2.1. This DID is used when the developer is tasked to define and record the design of a CSCI.

2.2. Designs pertaining to interfaces may be presented in the SDD or in IDDs.

Designs pertaining to databases may be presented in the SDD or in DBDD.

2.3. The SDD shall be in the format as directed in the contract.

Requirements

3. Format.

a. Automated techniques. Use of automated techniques is encouraged. The term

"document" in this DID means a collection of data, regardless of its medium.

b. Alternate presentation styles. Diagrams, tables, matrices, and other presentation styles shall be acceptable substitutes for text when data required by this DID can be made more readable using these styles.

Source: http://assist.dla.mil -- Downloaded: 2022-10-26T16:50Z

DI-IPSC-81435B

c. Title page or identifier. The document shall include a title page containing, as applicable: document number; volume number; version or revision indicator; security markings in accordance with DoD Manual (DoDM) 5200.01 or other restrictions on the handling of the document; date; document title; name, abbreviation, and any other identifier for the system, subsystem, or item to which the document applies; contract number; CDRL item number; organization for which the document has been prepared; name and address of the preparing organization; and distribution statement in accordance with DoD Instruction

(DoDI) 5230.24. For data in a database or other alternative form, this information shall be included on external and internal labels or by equivalent identification methods. Copies of the aforementioned instructions can be obtained at https://www.esd.whs.mil/DD/DoD-Issuances/

d. 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.

e. Page numbering and labeling. 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 the desired data can be indexed and accessed.

f. 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." For data in a database or other alternative form, this representation need occur only in the table of contents or equivalent.

g. Multiple paragraphs and subparagraphs. Any section, paragraph, or subparagraph in the SDD shall be written as multiple paragraphs or subparagraphs if it enhances readability.

h. 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.

i. Substitution of existing documents. Commercial or other existing documents shall be substituted for all or part of the document if they contain the required data.

Content Requirements

1. Scope. This section shall be divided into the following paragraphs.

1.1. System Identification. This paragraph shall contain a full identification of the https://www.esd.whs.mil/DD/DoD-Issuances/ system and the software to which the SDD applies, including, as applicable:

a) Identification number(s)

b) Title(s)

c) Abbreviation(s)

d) Version number(s)

e) Release number(s)

1.2. System overview. This paragraph shall briefly state the purpose of the system and the software to which the SDD 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.

1.3. Document overview. This paragraph shall summarize the purpose and contents of this document and shall describe any security or privacy considerations associated with its use.

1.4. Section 508, IT Accessibility. Usability will be in compliance with the Section 508

Amendment of the Rehabilitation Act of 1973.

2. Referenced documents. This section shall list the number, title, revision, and date of all documents referenced in this document. This section shall also identify the source for all referenced documents not available through Government sources.

3. CSCI-wide design decisions. This section shall be divided into paragraphs as needed to present CSCI-wide design decisions, that is, decisions about the CSCI's behavioral design

(how it will behave, from a user's point of view, in meeting its requirements, ignoring internal implementation) and other decisions affecting the selection and design of the software units that make up the CSCI. If all such decisions are explicit in the CSCI requirements or are deferred to the design of the CSCI's software units, this section shall so state. Design decisions that respond to requirements designated critical, such as those for safety, security, or privacy, shall be placed in separate subparagraphs. If a design decision depends upon system states, modes or lists, explain the software states and modes. Design conventions needed to understand the design shall be presented or referenced. Examples of CSCI-wide design decisions are the following:

a. Input /Output (I/O). Design decisions regarding inputs the CSCI will accept and outputs it will produce, including interfaces with other systems, HWCIs, CSCIs, and users.

If part or all of this information is given in IDDs, they may be referenced. Define the target operating system(s). CSCI Behavior for I/O Conditions. Design decisions on software behavior in response to each input or condition, including actions the CSCI performs, response times, and other performance characteristics.

b. Equations, algorithms, rules, and handling of un-allowed inputs or conditions.

c. Databases and Data Files. Design decisions on how databases and data files appear to the end user. If part or all of this information is given in DBDDs, they may be referenced.

d. Selected approach to meeting safety, security, and privacy requirements.

e. Other Decisions. Other CSCI-wide design decisions made in response to requirements, such as selected approach to providing required flexibility, availability, and maintainability.

f. Model Based Systems Engineering (MBSE). MBSE can be used to develop a set of related system models that help define, design, analyze, and document the system under development.

g. External Dependencies. List all external dependencies for example:

1. Software libraries

2. Web services, etc.

3.1. Cyber security and Personally Identifiable Information (PII) requirements. This paragraph shall specify the software requirements, concerned with maintaining cyber security and any PII data. These requirements shall include, as applicable, the security/privacy environment in which the software must operate, the type and degree of security or privacy to be provided, the security/privacy risks the software must withstand, required safeguards to reduce those risks, the security/privacy policy that must be met, the security/privacy accountability the software must provide, and the criteria that must be met for security/privacy certification/accreditation.

4. CSCI architectural design. This section shall be divided into the following paragraphs to describe the CSCI architectural design. If part or all of the design depends upon system states or modes, this dependency shall be indicated. If design information falls into more than one paragraph, it may be presented once and referenced from the other paragraphs.

Design conventions needed to understand the design shall be presented or referenced.

4.1. CSCI components. This paragraph shall:

a. Identify the individual software units that make up the CSCI. Each software unit shall be assigned a unique identifier.

Note: A software unit shall be defined as an element in the design of a CSCI;

for example, a major subdivision of a CSCI, a component of that subdivision, a class, object, module, function, routine, or database. Software units may occur at different levels of a hierarchy and may consist of other software units. Software units in the design may or may not have a one-to-one relationship with the code and data entities (routines, procedures, databases, data files, etc.) that implement them or with the computer files containing those entities. A database may be treated as a CSCI or as a software unit. The SDD may refer to software units by any name(s) consistent with the design methodology being used.

b. Relationships. Show the static (such as "consists of") relationship(s) of the software units. Multiple relationships shall be presented, depending on the selected software design methodology (for example, in an object-oriented design or modular open systems design, this paragraph may present the class and object structures as well as the module and process architectures of the CSCI).

c. Requirements and Allocation. State the purpose of each software unit, the

CSCI requirements, and the CSCI-wide design decisions allocated to it.

d. Identifying Information. Identify groups of software unit's development status/type (such as: new development, existing design or software to be reused as is, existing design or software to be reengineered, software to be developed for reuse, software planned for Build N, etc.). For existing design or software, the description shall include identifying information, such as name, version, documentation references, library, etc.

e. Computer Hardware Resources. Describe the CSCI's (and as applicable, each software unit's) planned utilization of computer hardware resources (such as processor capacity, memory capacity, input/output device capacity, auxiliary storage capacity, and communications/network equipment capacity). The description shall cover all computer hardware resources included in resource utilization requirements for the CSCI, in system-level resource allocations affecting the CSCI, and in resource utilization measurement planning in the Software Development Plan. If all utilization data for a given computer hardware resource are presented in a single location, such as in another SDD, the referenced

SDD and paragraph shall be stated. Included for each computer hardware resource shall be:

1. The CSCI requirements or system-level resource allocations being satisfied

2. The assumptions and conditions on which the utilization data are based (for example, typical usage, worst-case usage, assumptions of certain events)

3. Any special considerations affecting the utilization (such as use of virtual memory, overlays, or multiprocessors or the impacts of operating system overhead, library software, or other implementation overhead)

4. The units of measure used (such as percentage of processor capacity, cycles per second, bytes of memory, bytes per second)

5. The level(s) at which the estimates or measures are made (such as software unit, CSCI, or executable program)

f. State the library, website, etc. where the software unit is to be placed.

4.2. Concept of execution. This paragraph shall describe the concept of execution among the software units. It shall include diagrams and descriptions showing the dynamic relationship of the software units, that is, how they will interact during CSCI operation, including, as applicable:

Flow of execution control

Data flow

State transition diagrams

Timing

Priorities among units

Handling of interrupts

Timing/sequencing relationships

Exception handling

Concurrent execution

Dynamic allocation/deallocation

Dynamic creation or deletion of objects, processes, tasks, and other aspects of dynamic behavior

4.3. Interface design. This paragraph shall be divided into the following subparagraphs to describe the interface characteristics of the software units. It shall include both interfaces among the software units and their interfaces with external entities such as systems, configuration items, Service level Agreements for interfaces, and users. If part or all of this information is contained in IDDs or elsewhere, these sources may be referenced.

4.3.1 Interface identification and diagrams. This paragraph shall state the project-unique identifier assigned to each interface and shall identify the interfacing entities (software units, systems, configuration items, users, etc.) by name, number, version, and documentation references, as applicable. The identification shall state which entities have fixed interface characteristics (and therefore impose interface requirements on interfacing entities) and which are being developed or modified (thus having interface requirements imposed on them). If needed one or more interface diagrams shall be provided, as appropriate, to depict the interfaces.

4.3.2 (Unique identifier of interface). This paragraph shall identify an interface by unique identifier, shall briefly identify the interfacing entities, and shall be divided into subparagraphs, as needed, to describe the interface characteristics of one or both of the interfacing entities. If a given interfacing entity is not covered by this SDD (for example, an external system) but its interface characteristics need to be mentioned to describe interfacing entities that are, these characteristics shall be stated as assumptions or as “When [the entity not covered] does this, [the entity that is covered] will…” This paragraph may reference other documents (such as data dictionaries, standards for protocols, and standards for user interfaces) in place of stating the information here. The design description shall include the following, as applicable, presented in any order suited to the information to be provided, and shall note any differences in these characteristics from the point of view of the interfacing entities (such as different expectations about the size, frequency, or other characteristics of data elements):

a. Priority assigned to the interface by the interfacing entity(ies) such as:

1. Spanning tree

2. Priority queue

3. Tree

4. Other data structures

b. Cybersecurity considerations for interface requirements such as:

1. Identifying vulnerabilities

2. Evaluating vulnerabilities

3. Reporting vulnerabilities

4. Mitigating or resolving security vulnerabilities

c. Type of interface (such as real-time data transfer, storage-and-retrieval of data, etc.) to be implemented

d. Characteristics of individual data elements that the interfacing entity(ies) provide, store, send, access, receive, etc., such as:

1. Names and identifiers:

a) Unique identifier

b) Non-technical (natural-language) name

c) DoD standard data element name

d) Technical name (e.g., variable or field name in code or database)

e) Abbreviation or synonymous name(s)

2. Data type (alphanumeric, integer, etc.)

3. Size and format (such as length and punctuation of a character string)

4. Units of measurement (such as meters, dollars, nanoseconds)

5. Range or enumeration of possible values (such as 0-99)

6. Accuracy (how correct) and precision (number of significant digits)

7. Priority, timing, frequency, volume, sequencing, and other constraints, such as whether the data element may be updated and whether business rules apply

8. Security and privacy constraints

9. Sources (setting/sending entities) and recipients (using/receiving entities)

e. Characteristics of data element assemblies (records, messages, files, arrays, displays, reports, etc.) that the interfacing entity(ies) will provide, store, send, access, receive, etc., such as:

1. Names and identifiers:

a) Unique identifier

b) Non-technical (natural language) name

c) Technical name (e.g., record or data structure name in code or database)

d) Abbreviations or synonymous name(s)

2. Data elements in the assembly and their structure (number, order, grouping)

3. Medium (such as disk) and structure of data elements/assemblies on the medium

4. Visual and auditory characteristics of displays and other outputs (such as colors, layouts, fonts, icons and other display elements, beeps, lights)

5. Relationships among assemblies, such as sorting/access characteristics

6. Priority, timing, frequency, volume, sequencing, and other constraints, such as whether the assembly may be updated and whether business rules apply

7. Security and privacy constraints

8. Sources (setting/sending entities) and recipients (using/receiving entities)

f. Characteristics of communication methods that the interfacing entity(ies) use for the interface, such as:

1. Unique identifier(s)

2. Communication links, bands, frequencies, media and their characteristics

3. Message formatting

4. Flow control (such as sequence numbering and buffer allocation)

5. Data transfer rate, whether periodic/aperiodic, and interval between transfers

6. Routing, addressing, and naming conventions

7. Transmission services, including priority and grade

8. Safety, security, and privacy considerations, such as encryption, user authentication, compartmentalization, and auditing

g. Characteristics of protocols that the interfacing entity(ies) use for the interface, such as:

1. Unique identifier(s)

2. Priority and layer of the protocol

3. Packeting, fragmentation and reassembly, routing, and addressing

4. Legality checks, error control, and recovery procedures

5. Synchronization, including: connection establishment, maintenance, termination status, identification, and any other reporting features

h. Other characteristics, such as physical compatibility of the interfacing entity(ies)

(dimensions, tolerances, loads, voltages, plug compatibility, etc.)

5. Requirements traceability. This section shall contain:

a. Traceability from each software unit identified in this SDD to the CSCI requirements allocated to it. (Use of MBSE methods is acceptable.)

b. Traceability from each CSCI requirement to the software units to which it is allocated.

6. Notes. This section shall contain any general information that aids in understanding this document (e.g., background information, glossary, rationale). This section shall include an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document and a list of any terms and definitions needed to understand the SDD.

Appendixes. Appendices may be used to provide information published separately for convenience in document maintenance (e.g., charts, classified data). As applicable, each appendix shall be referenced in the main body of the document where the data would normally have been provided. Appendices may be bound as separate documents for ease in handling.

Appendices shall be lettered alphabetically (A, B, etc.).

End of DI-IPSC-81435B

Source: http://assist.dla.mil -- Downloaded: 2022-10-26T17:15Z

Source: http://assist.dla.mil -- Downloaded: 2022-10-26T17:24Z

Source: http://assist.dla.mil -- Downloaded: 2022-10-26T17:09Z

Source: http://assist.dla.mil -- Downloaded: 2022-10-26T17:31Z

Title: SOFTWARE DOCUMENTATION

Number: DI-IPSC-81756 Approval Date: 20080528 AMSC Number: N9043 Limitation:

DTIC Applicable: GIPDEP Applicable: N/A Office of Primary Responsibility: SH/ PEO IWS 1.0 Applicable Forms: N/A

Use/Relationship: The Software Documentation is used to support required reviews and Test Readiness Evaluations

This data item description contains the format and content preparation instructions for the data product resulting from the discrete task requirements as delineated in the contract.

Requirements:

1.0 Format. The Software Documentation shall be in contractor’s format.

2.0 Content. The Software Documentation shall include activity and sequence diagrams, data dictionaries, and design products vaulted as drafts-in-process for the software design artifacts.

2.1 Procedures to assemble an installed computer program from the component software modules shall be included. The documentation shall also include subprograms, commercial off the shelf and non-developmental items programs.

2.2 Unit test data sets and technical functional test scripts shall be included. The equivalent data sets used to test the software unit shall be identified when unit test data sets are not used.

2.3 Quick reference cards, context sensitive help and simulations for the reusable learning objects shall be included.

3.0 End of DI-IPSC-81756

Source: http://assist.dla.mil -- Downloaded: 2022-10-26T17:27Z

Title: Management Plan

Number: DI-MGMT-80004A Approval Date: 30 OCT 2006 AMSC Number: 7621 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: NS/DA02 Applicable Forms: N/A

Use/relationship: The management plan describes the contractor’s organization, assignment of functions, duties, and responsibilities, management procedures and policies, and reporting requirements for the conduct of contractually-imposed tasks, projects, or programs.

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 may be applied in any contract or program phase where the contract management is under the direction and control of the contractor.

Requirements:

1. Reference documents. None.

2. Format. The plan shall be in a format that the contractor devises and conforms to the following:

a. Identification. The plan shall be identified with the preparing office or contractors title, the identifying numbers or designation of the Contract/Procurement Request, the identify and/or nomenclature of the system/component/program/project, the security classification and the Government activity issuing the controlling contract.

b. Descriptive material. As may be needed to clarify or explain matters in the text, the plan may include descriptive material, sketches, drawings, photographs, tables, forms, graphs, worksheets, charts, etc.

c. Page size. The plan may be typewritten or printed on standard size paper, e.g., 8 ½ x 11 inches or metric A4. The pages shall be sequentially numbered and security bound together. As necessary, graphic material may be one-way fold-outs. All attachments shall be identified and referenced in the text. Each section and paragraph shall be numbered.

d. Table of contents and index. Plans of more than 30 pages in length shall contain a

Source: http://assist.dla.mil -- Downloaded: 2022-10-26T17:45Z

h. delivery procedures

DI-MGMT-80004A

table of contents. Plans more than 120 pages in length shall also include an Index.

e. Legibility. The document shall be legible and reproducible.

3.1 General. The Management Plan shall consist of the organizational structure, the assignment of functions, duties, and responsibilities, the procedures and policies and the reporting requirements that are established for the initiation, monitoring, control, completion, test and verification, and reporting of contractual tasks, projects, and programs.

3.2 Specific contents. The Management Plan shall cover the organizational structure, program management methodology, personnel, security, and the reports as described herein. Other subjects to be included are as follows:

a. design control

b. reliability

c. configuration control

d. standardization

e. quality assurance

f. provisioning

g. control of Government property

i. tests

j. certifications

k. packaging

l. shipping

m. other

3.3 Organizational structure. The plan shall present an organizational chart and supporting narrative…