July 17, 2008

System Design Specification Guidebook Appendix E – Integrated Warfare, Combat, Weapon Systems

Attachment 1 - Statutory and regulatory requirements specified in DoDI 5000.2 enclosure 3.

System Design Specification Appendix E: INTEGRATED WARFARE SYSTEMS,

COMBAT SYSTEMS, WEAPON SYSTEMS

Use of this Guide:

This appendix of the System Design Specification Guidebook is intended to provide guidance in the
preparation of a document that articulates comprehensive, cogent information for use by the Program
Manger, his staff, industry partners, and the chain of command. It is not intended to replicate
information found elsewhere, such as in Systems Engineering Plans, requirements documents, and other
items required for program management; however, it must reference and include information from those
documents. To minimize the effort needed to maintain consistency among the documents, the
recommended practice is to provide linkage to the detail of particular topics through reference to the
appropriate documentation and to provide synopsis or summary level information in the System Design
Specification to ensure that it contains enough context to function as a stand-alone entity while leaving
details to the pertinent reference. Where possible and not prohibited by classification or business
sensitivity, the use of hyper-linking and other tools available in electronic form should be used to
provide ready access to the detailed information when used in an networked, web-enabled, or other
suitable environment (e.g., CD or DVD based collections of documents).

1. Scope
1.1. Introduction

2. Operational Requirements
2.1. Missions
2.2. Threat
2.3. Environment
2.4. Requirements
2.4.1. Performance Requirements
2.4.1.1. Derivation of Performance Requirements from Concept of Operations (CONOPS)
and Capabilities Development Document (CDD)
2.4.1.1.1. KPPs
2.4.1.1.2. KSAs
2.4.1.1.3. Additional / Derived Attributes
2.4.2. Capabilities
2.4.2.1. Derivation of Functional Requirements from Concept of Operations (CONOPS)
and Capabilities Development Document (CDD)
2.4.2.1.1. KPPs
2.4.2.1.2. KSAs
2.4.2.1.3. Additional / Derived Attributes

2.5. Family of System (FoS) Requirements

2.6. System of System (SoS) Requirements
2.7. Naval Open Architecture – Requirements should be addressed in the SDS based on the
mandate stipulated in the NOA Requirements Letter (OPNAV N6/N7 Memorandum 0f 23
December 2005 requiring Program Managers to implement NOA principles). At a minimum,
programs should be evaluated on the criteria they have established to ensure the key tenets of NOA
are met.
2.7.1. Tools to Assist OA Requirements
2.7.1.1. OAAT- The Naval OA Compliance Action List consists of questions contained in
the Open Architecture Assessment Tool (OAAT v1.1). The OAAT was developed
by the Open Architecture Enterprise Team (OAET) to provide a common

Page 1 of 15
 July 17, 2008
System Design Specification Guidebook Appendix E – Integrated Warfare, Combat, Weapon Systems

Attachment 1 - Statutory and regulatory requirements specified in DoDI 5000.2 enclosure 3.

approach to assessing the openness of Naval Programs. Although this CAL was
created to be consistent with the FORCEnet Consolidated Compliance Checklist,
it cannot be used as a substitute for the OAAT itself. Each program must conduct
an OA Assessment using the OAAT to accurately assess its openness. The
OAAT also provides extensive explanations and standard answers to assist
programs in conducting an accurate assessment. The tool is available as a
Microsoft Excel spreadsheet from the Naval OA website
(https://acc.dau.mil/oa under TOOLS) and will transition to the FORCEnet
Implementation Tool Suite (FITS) environment when its available.
2.7.1.2. OSJTF- Open Systems Joint Task Force (OSJTF), Modular Open System’s
Approach (MOSA) Program Assessment Rating Tool (PART) questions. By
Completing the OAAT, a program also conducts a MOSA PART assessment.
The tool also produces the required outputs for submission to OSJTF.

3. List of Reference Documents – provide an itemized list of specifications developed during Systems
Engineering. List them in order as they are cited. A specification tree should be included.

3.1. System Requirements Document (SRD) - The Functional Baseline is documented in the SRD.
The System/Subsystem Specification specifies the requirements for a system or subsystem and
the methods to be used to ensure that each requirement has been met. Requirements pertaining
to the system or subsystem's external interfaces may be presented in the SRD or in one or more
Interface Requirements Specifications (IRSs) All functional requirements shall be traceable to
higher-level capabilities and shall be verifiable by a specific test method. All elements of the
SRD will be reviewed at the System Requirements Review (SRR) and the follow-on System
Functional Review (SFR). A template for the Systems Requirements Documents can be found
in the System/Subsystem Specification (DI-IPSC-81431A)1.
3.2. System/Subsystem Design Document (SSDD) - The SSDDs (DI-IPSC-81432) can be used as a
guide to SSDD development. Requirements pertaining to the system or subsystem's external
interfaces may be presented in the SSDD or in one or more IRSs referenced from the SSDD.
The SSDD, possibly supplemented by IRS and Interface Design Document (IDD) is used as
the basis for design and qualification testing of a system or subsystem.
3.3. Element Requirement Specifications – Uses the same System/Subsystem Specification (DI-
IPSC-81431A) as the System Requirements Document but provides a lower level of
requirements detail.
3.4. Interface Requirements Specifications (IRS) - The IRS (DI-IPSC-81434) specifies the
requirements imposed on one or more systems, subsystems, hardware configuration items,
(HWCIs), computer software configuration items, (CSCIs), manual operations, or other system
components to achieve one or more interfaces among these entities. An IRS can cover any
number of interfaces. The IRS can be used to supplement the SSDD and SRS as the basis for
design and qualification testing of systems and CSCI.
3.5. Interface Design Document (IDD) - The IDD (DI-IPSC-81436) describes the interface
characteristics of one or more systems, subsystems, HWCIs, CSCIs, manual operations, or
other system components. An IDD may also describe any number of interfaces. The IDD can
be used to supplement the System/Subsystem Design Description (SSDD) (DI-IPSC-81432) or
Software Design Description (SDD) (DI-IPSC-81435). The IDD and its companion IRS serve
to communicate and control interface design decisions.
3.6. Software Requirements Specifications (SRS) – The SRS (DI-IPSC-81433) specifies the
requirements for a Computer Software CSCI and the methods to be used to ensure that each
1
Military standard data item descriptions are publicly available at http://assistdocs.com through the Defense
Standardization Program.

Page 2 of 15
 July 17, 2008
System Design Specification Guidebook Appendix E – Integrated Warfare, Combat, Weapon Systems

Attachment 1 - Statutory and regulatory requirements specified in DoDI 5000.2 enclosure 3.

requirement has been met. Requirements pertaining to the CSCI external interfaces may be
presented in the SRS or in one or more Interface IRS referenced from the SRS. The SRS,
possibly supplemented by the IRS, is used as the basis for design and qualification testing of a
CSCI.
3.7. Initial Capabilities Document (ICD)
3.8. Draft Capabilities Development Document (CDD)
3.9 Concept of Operations (CONOPS)
3.10 Systems Engineering Plan (SEP)
3.11 System Program Director (SPD)

4. Weapon System Design Criteria

4.1. Standards and Practices – describe the applicability of each of the following directives/
instructions/ practices etc on your program. It is not expected that every program will have a
component that addresses each standard and practice – the list should be tailored to those
standards that are applicable to the system being described. If you have tailored a particular
standard or specification, annotate why that was done and the expected result.
4.1.1. MIL SPEC / MIL STDs
4.1.2. OPNAV Instructions
4.1.3. SYSCOM Instructions
4.1.4. PEO IWS Instructions
4.1.5. Design Standards
4.1.6. Information Assurance
4.1.7. Navy Open Architecture Standards
4.1.8. Open System Architecture Standards
4.1.9. System Software Safety Technical Review Panel (SSSTRP) Guidance
4.1.10. Weapon Systems Explosive Safety Review Board (WSESRB) Guidance
4.1.11. Wartime Reserve Mode Requirements
4.1.12. National Security Strategy (NSS) Supportability – Bandwidth / Quality of Service
Requirements

4.2. Statutory and Regulatory Requirements – This paragraph should address the satisfaction of
statutory and regulatory requirements specified in DoDI 5000.2 enclosure 3 (see attachment 1).

5. Weapon System Requirements - This section shall be divided into the following paragraphs to
specify the system requirements, that is, those characteristics of the system that are conditions for its
acceptance. Each requirement shall be assigned a project-unique identifier to support testing and
traceability and shall be stated in such a way that an objective test can be defined for it. Each
requirement shall be annotated with associated qualification method(s) (see section 7) and, for
subsystems, traceability to system requirements (see section 6.7), if not provided in those sections.
The degree of detail to be provided shall be guided by the following rule: Include those
characteristics of the system that are conditions for system acceptance; defer to design descriptions
those characteristics that the acquirer is willing to leave up to the developer. If there are no
requirements in a given paragraph, the paragraph shall so state. If a given requirement fits into more
than one paragraph, it may be stated once and referenced from the other paragraphs.

5.1. Required states and modes - If the system is required to operate in more than one state or mode
having requirements distinct from other states or modes, this paragraph shall identify and
define each state and mode. Examples of states and modes include: idle, ready, active, post-use
analysis, training, degraded, emergency, back-up, wartime, peacetime. The distinction between
states and modes is arbitrary. A system may be described in terms of states only, modes only,
states within modes, modes within states, or any other scheme that is useful. If no states or

Page 3 of 15
 July 17, 2008
System Design Specification Guidebook Appendix E – Integrated Warfare, Combat, Weapon Systems

Attachment 1 - Statutory and regulatory requirements specified in DoDI 5000.2 enclosure 3.

modes are required, this paragraph shall so state, without the need to create artificial
distinctions. If states and/or modes are required, each requirement or group of requirements in
this specification shall be correlated to the states and modes. The correlation may be indicated
by a table or other method in this paragraph, in an appendix referenced from this paragraph or
by annotation of the requirements in the paragraphs where they appear.

5.2. System capability requirements - This paragraph shall be divided into subparagraphs to itemize
the requirements associated with each capability of the system. A "capability" is defined as a
group of related requirements. The word "capability" may be replaced with "function,"
"subject," "object," or other term useful for presenting the requirements.

5.2.1. Air Warfare – This section should include hard-kill and soft -kill performance
requirements against Anti-Ship Cruise Missile Threats, Manned and Unmanned Aircraft,
Land Attack Cruise Missiles and High Divers in various environmental and jamming
conditions. The requirements should include planning, sensing, control and engagement
capabilities. The performance requirements should cover detection ranges, number and
types of tracks, reaction time, coverage, firepower, simultaneous engagements, probability
of kill, system availability etc.
5.2.2. Ballistic Missile Defense - This section should include hard-kill and soft-kill
performance requirements against Short Range Ballistic Missile, Medium Range Ballistic
Missiles, Intermediate Range Ballistic Missiles and Inter-Continental Ballistic Missiles in
various environmental and jamming conditions. The requirements should include
planning, sensing, control and engagement capabilities. The performance requirements
should cover detection ranges, number and types of tracks, reaction time, coverage,
firepower, simultaneous engagements, probability of kill, system availability etc.
5.2.3. Surface Warfare - This section should include hard-kill and soft-kill performance
requirements against Small Boats (manned and unmanned), patrol boats and Naval Ships
in various environmental and jamming conditions. The requirements should include
planning, sensing, control and engagement capabilities. The performance requirements
should cover detection ranges, number and types of tracks, reaction time, coverage,
firepower, simultaneous engagements, probability of kill, system availability etc.
5.2.4. Undersea Warfare - This section should include hard-kill and soft-kill performance
requirements against submarines, unmanned underwater vehicles, and mines in various
environmental and jamming conditions. The requirements should include planning,
sensing, control and engagement capabilities. The performance requirements should
cover detection ranges, number and types of tracks, reaction time, coverage, firepower,
simultaneous engagements, probability of kill, system availability etc.
5.2.5. Strike Warfare - This section should include hard-kill and soft-kill performance
requirements against Land Based targets (mobile and fixed) in various environmental and
jamming conditions. The requirements should include planning, sensing, control and
engagement capabilities. The performance requirements should cover detection ranges,
number and types of tracks, reaction time, coverage, firepower, simultaneous
engagements, probability of kill, system availability etc.
5.2.6. Naval Surface Fire Support - This section should include gun and missile performance
requirements against land targets (mobile and fixed) in support of USMC call for fire in
various environmental and jamming conditions. The requirements should include
planning, sensing, control and engagement capabilities. The performance requirements
should cover detection ranges, number and types of tracks, reaction time, coverage,
firepower, simultaneous engagements, probability of kill, system availability etc.

Page 4 of 15
 July 17, 2008
System Design Specification Guidebook Appendix E – Integrated Warfare, Combat, Weapon Systems

Attachment 1 - Statutory and regulatory requirements specified in DoDI 5000.2 enclosure 3.

5.2.7. Command, Control and Communications – This section should include the systems
performance regarding planning, command and control and communications for force
level command functions.
5.2.8. Electronic and Information Warfare – This section should include performance
requirements associated with achieving information superiority by affecting adversary
information, information-based processes, information systems, and computer-based
networks while defending one’s own information, information-based processes,
information systems and computer-based networks.
5.2.9. Anti-Terrorism and Force Protection
5.2.10. Amphibious Warfare – This section should include performance requirements regarding
attacks launched from the sea by naval forces and landing forces embarked in ships and
craft designed to achieve shore presence in a littoral zone.
5.2.11. Naval Special Warfare – This section should include performance requirements
associated with naval special warfare operations include special mobile operations,
unconventional warfare, coastal and river interdiction, beach and coastal reconnaissance,
and certain intelligence operations.

5.3. System external interface requirements - This paragraph shall be divided into subparagraphs to
specify the requirements, if any, for the system’s external interfaces. This paragraph may
reference one or more Interface Requirements Specifications (IRSs) or other documents
containing these requirements.
5.3.1. Interface identification and diagrams. This paragraph shall identify the required external
interfaces of the system. The identification of each interface shall include a project-unique
identifier and shall designate the interfacing entities (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). One or more interface
diagrams shall be provided to depict the interfaces.
5.3.2. (Project-unique identifier of interface). This paragraph (beginning with 5.3.2) shall
identify a system external interface by project-unique identifier, shall briefly identify the
interfacing entities, and shall be divided into subparagraphs as needed to state the
requirements imposed on the system to achieve the interface. Interface characteristics of
the other entities involved in the interface shall be stated as assumptions or as "When [the
entity not covered] does this, the system shall...," not as requirements on the other entities.
This paragraph may reference other documents (such as data dictionaries, standards for
communication protocols, and standards for user interfaces) in place of stating the
information here. The requirements shall include the following, as applicable, presented in
any order suited to the requirements, 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).

5.4. System internal interface requirements. This paragraph shall specify the requirements, if any,
imposed on interfaces internal to the system. If all internal interfaces are left to the design or to
requirement specifications for system components, this fact shall be so stated. If such
requirements are to be imposed, paragraph 5.3 provides a list of topics to be considered.

5.5. System internal data requirements. This paragraph shall specify the requirements, if any,
imposed on data internal to the system. Included shall be requirements, if any, on databases and
data files to be included in the system.

Page 5 of 15
 July 17, 2008
System Design Specification Guidebook Appendix E – Integrated Warfare, Combat, Weapon Systems

Attachment 1 - Statutory and regulatory requirements specified in DoDI 5000.2 enclosure 3.

5.6. Adaptation requirements. This paragraph shall specify the requirements, if any, concerning
installation-dependent data that the system is required to provide (such as site dependent
latitude and longitude or site-dependent state tax codes) and operational parameters that the
system is required to use that may vary according to operational needs (such as parameters
indicating operation-dependent targeting constants or data recording).

5.7. Safety requirements. This paragraph shall specify the system requirements, if any, concerned
with preventing or minimizing unintended hazards to personnel, property, and the physical
environment. Examples include restricting the use of dangerous materials; classifying
explosives for purposes of shipping, handling, and storing; abort/escape provisions from
enclosures; gas detection and warning devices; grounding of electrical systems;
decontamination; and explosion proofing. This paragraph shall include the system
requirements, if any, for nuclear components, including, as applicable, requirements for
component design, prevention of inadvertent detonation, and compliance with nuclear safety
rules.

5.8. Security and privacy requirements. This paragraph shall specify the system requirements, if
any, concerned with maintaining security and privacy. The requirements shall include, as
applicable, the security/privacy environment in which the system must operate, the type and
degree of security or privacy to be provided, the security/privacy risks the system must
withstand, required safeguards to reduce those risks, the security/privacy policy that must be
met, the security/privacy accountability the system must provide, and the criteria that must be
met for security/privacy certification/accreditation.

5.9. System environment requirements. This paragraph shall specify the requirements, if any,
regarding the environment in which the system must operate. Examples for a software system
are the computer hardware and operating system on which the software must run. (Additional
requirements concerning computer resources are given in the next paragraph). Examples for a
hardware-software system include the environmental conditions that the system must withstand
during transportation, storage, and operation, such as conditions in the natural environment
(wind, rain, temperature, geographic location), the induced environment (motion, shock, noise,
electromagnetic radiation), and environments due to enemy action (explosions, radiation).

5.10. Computer resource requirements. This paragraph shall be divided into the following
subparagraphs. Depending upon the nature of the system, the computer resources covered in
these subparagraphs may constitute the environment of the system (as for a software system) or
components of the system (as for a hardware-software system).

5.10.1. Computer hardware requirements. This paragraph shall specify the requirements, if any,
regarding computer hardware that must be used by, or incorporated into, the system. The
requirements shall include, as applicable, number of each type of equipment, type, size,
capacity, and other required characteristics of processors, memory, input/output devices,
auxiliary storage, communications/network equipment, and other required equipment.

5.10.2. Computer hardware resource utilization requirements. This paragraph shall specify the
requirements, if any, on the system’s computer hardware resource utilization, such as
maximum allowable use of processor capacity, memory capacity, input/output device
capacity, auxiliary storage device capacity, and communications/network equipment
capacity. The requirements (stated, for example, as percentages of the capacity of each
computer hardware resource) shall include the conditions, if any, under which the resource
utilization is to be measured.

Page 6 of 15
 July 17, 2008
System Design Specification Guidebook Appendix E – Integrated Warfare, Combat, Weapon Systems

Attachment 1 - Statutory and regulatory requirements specified in DoDI 5000.2 enclosure 3.

5.10.3. Computer software requirements. This paragraph shall specify the requirements, if any,
regarding computer software that must be used by, or incorporated into, the system.
Examples include operating systems, database management systems,
communications/network software, utility software, input and equipment simulators, test
software, and manufacturing software. The correct nomenclature, version, and
documentation references of each such software item shall be provided.

5.10.4. Computer communications requirements. This paragraph shall specify the additional
requirements, if any, concerning the computer communications that must be used by, or
incorporated into, the system. Examples include geographic locations to be linked;
configuration and network topology; transmission techniques; data transfer rates;
gateways; required system use times; type and volume of data to be transmitted/received;
time boundaries for transmission/reception/response; peak volumes of data; and diagnostic
features.

5.11. System quality factors. This paragraph shall specify the requirements, if any, pertaining
to system quality factors. Examples include quantitative requirements concerning system
functionality (the ability to perform all required functions), reliability (the ability to perform
with correct, consistent results -- such as mean time between failure for equipment),
maintainability (the ability to be easily serviced, repaired, or corrected), availability (the ability
to be accessed and operated when needed), flexibility (the ability to be easily adapted to
changing requirements), portability of software (the ability to be easily modified for a new
environment), reusability (the ability to be used in multiple applications), testability (the ability
to be easily and thoroughly tested), usability (the ability to be easily learned and used), and
other attributes.

5.12. Design and construction constraints. This paragraph shall specify the requirements, if
any, that constrain the design and construction of the system. For hardware-software systems,
this paragraph shall include the physical requirements imposed on the system. These
requirements may be specified by reference to appropriate commercial or military standards
and specifications.

Page 7 of 15
 July 17, 2008
System Design Specification Guidebook Appendix E – Integrated Warfare, Combat, Weapon Systems

Attachment 1 - Statutory and regulatory requirements specified in DoDI 5000.2 enclosure 3.

Examples include requirements concerning:

 Use of a particular system architecture or requirements on the architecture, such as required

subsystems; use of standard, military, or existing components; or use of Government/acquirer-
furnished property (equipment, information, or software)
 Use of particular design or construction standards; use of particular data standards; use of a
particular programming language; workmanship requirements and production techniques
 Physical characteristics of the system (such as weight limits, dimensional limits, color,
protective coatings); interchangeability of parts; ability to be transported from one location to
another; ability to be carried or set up by one, or a given number of, persons
 Materials that can and cannot be used; requirements on the handling of toxic materials; limits
on the electromagnetic radiation that the system is permitted to generate
 Use of nameplates, part marking, serial and lot number marking, and other identifying markings
 Flexibility and expandability that must be provided to support anticipated areas of growth or
changes in technology, threat, or mission

5.13. Personnel-related requirements. This paragraph shall specify the system requirements, if
any, included to accommodate the number, skill levels, duty cycles, training needs, or other
information about the personnel who will use or support the system. Examples include
requirements for the number of work stations to be provided and for built-in help and training
features. Also included shall be the human factors engineering requirements, if any, imposed on
the system. These requirements shall include, as applicable, considerations for the capabilities
and limitations of humans, foreseeable human errors under both normal and extreme
conditions, and specific areas where the effects of human error would be particularly serious.
Examples include requirements for adjustable-height work stations, color and duration of error
messages, physical placement of critical indicators or buttons, and use of auditory signals.

5.14. Training-related requirements. This paragraph shall specify the system requirements, if
any, pertaining to training. Examples include training devices and training materials to be
included in the system.

5.15. Logistics-related requirements. This paragraph shall specify the system requirements, if
any, concerned with logistics considerations. These considerations may include: system
maintenance, software support, system transportation modes, supply-system requirements,
impact on existing facilities, and impact on existing equipment.

5.16. Demilitarization and Disposal. This paragraph shall specify how demilitarization will
be controlled and how disposal will be carried out to minimize the Navy’s liability due to
environmental, safety, security, and health issues.

5.17. Other requirements. This paragraph shall specify additional system requirements, if any,
not covered in the previous paragraphs. Examples include requirements for system
documentation, such as specifications, drawings, technical manuals, test plans and procedures,
and installation instruction data, if not covered in other contractual documents.

5.18. Packaging requirements. This section shall specify the requirements, if any, for
packaging, labeling, and handling the system and its components for delivery. Applicable
military specifications and standards may be referenced if appropriate.

Page 8 of 15
 July 17, 2008
System Design Specification Guidebook Appendix E – Integrated Warfare, Combat, Weapon Systems

Attachment 1 - Statutory and regulatory requirements specified in DoDI 5000.2 enclosure 3.

5.19. Precedence and criticality of requirements. This paragraph shall specify, if applicable,
the order of precedence, criticality, or assigned weights indicating the relative importance of
the requirements in this specification. Examples include identifying those requirements deemed
critical to safety, to security, or to privacy for purposes of singling them out for special
treatment. If all requirements have equal weight, this paragraph shall so state.

5.20. Certification requirements. This paragraph shall specify all certification requirements
and the applicable technical warrant holders. It should be noted if additional systems or
components require fabrication for delivery to test and the proposed timing of the certification
events.

6. System Design

6.1. System Components – High-level diagram and description of the segments, elements, and
components of the warfare system. A diagram should be included.

The follow paragraph should address:

 Identify the component of the system (element hardware configuration items, software
configuration items, etc).
 Show the static (such as “consists of”) relationship(s) of the components. Multiple relationships
may be presented (using multiple diagrams), depending on the selected design methodology.
 State the purpose of each component and identify the system requirements and system-wide
design decisions allocated to it.
 Identify each component’s develop status/type, if known (such as new development, existing
component to be reused as it, existing design or component to be reengineered, component to
be developed for reuse, component planned for Build N, etc.) For existing design components,
the description shall be provided identifying information, such as name, version, documentation
references, location, etc.
 For each computer system or other aggregate of computer hardware resources identified for
use in the system, describe its computer hardware resources (such as processors, memory,
input/output devices, auxiliary storage, and communications/network equipment). Each
description shall, as applicable, identify the configuration items that will use the resource,
describe the allocation of the resource utilization to each configuration item (CSCI) that will use
the resource (for example, 20% of the resource’s capacity allocated to CSCI 1, 30% to CSCI
2), describe the conditions under which the utilization will be measured, and describe the
characteristics of the resource:
o Computer processors
o Memory
o Input/output devices
o Auxiliary storage
o Communications/network equipment
o Growth and diagnostics capabilities
 Present a specification tree for the system/subsystem
 A sample list of Segments/Elements/Components to consider is presented below

6.2. Computing Infrastructure Segment

6.2.1. Processors
6.2.2. Networks

Page 9 of 15
 July 17, 2008
System Design Specification Guidebook Appendix E – Integrated Warfare, Combat, Weapon Systems

Attachment 1 - Statutory and regulatory requirements specified in DoDI 5000.2 enclosure 3.

6.2.3. Displays
6.2.4. Common Services
6.2.5. Operating Systems
6.2.6. Middleware

6.3. Sense Segment

6.3.1. Air Search Radar

6.3.2. Surface Search Radar
6.3.3. Towed Array
6.3.4. Fire Control Radar
6.3.5. Ballistic Missile Defense Radar
6.3.6. Air and Missile Defense Radar
6.3.7. Bow Array
6.3.8. Sonobouys
6.3.9. ES Systems
6.3.10. EO/IR Systems
6.3.11. Identification Systems (IFF, NCTR, etc)
6.3.12. Off-board Sensors (UAV, etc)
6.3.13. Sensor Management Element

6.4. Command and Control Segment

6.4.1. Combat Control Element
6.4.1.1. Track Management
6.4.1.2. Identification
6.4.1.3. Tactical Planning
6.4.1.4. Threat Evaluation
6.4.1.5. Weapon Assignment
6.4.1.6. Off-board Vehicle Control
6.4.1.7. Resource Management
6.4.1.8. Readiness Assessment
6.4.1.9. Communications

6.4.2. Operational C2 Elements

6.4.2.1. GCCS-M
6.4.2.2. DCGS
6.4.2.3. Communications

6.5. Engage Segment

6.5.1. Weapons Management Element
6.5.2. Strike Missiles
6.5.3. AAW Missiles
6.5.4. BMD Missiles
6.5.5. Torpedoes
6.5.6. Rockets
6.5.7. Launchers
6.5.8. Guns
6.5.9. Electronic Attack
6.5.10. Decoys
6.5.11. Illuminators
6.5.12. Helicopters

Page 10 of 15
 July 17, 2008
System Design Specification Guidebook Appendix E – Integrated Warfare, Combat, Weapon Systems

Attachment 1 - Statutory and regulatory requirements specified in DoDI 5000.2 enclosure 3.

6.5.13. Off-board Weapons (UAVs, TACAIR, etc)

6.6. Support Segment

6.6.1. Weapon System Power
6.6.2. Weapon System Cooling
6.6.3. Training Elements
6.6.4. Logistics Elements
6.6.5. Maintenance Elements

6.7. Requirements traceability Matrix – Summary matrix of the traceability from each subsystem
(section 6) to the system requirements it addresses (section 5).

7. Qualification provisions. This section shall define a set of qualification methods and shall specify
for each requirement in Section 5 the method(s) to be used to ensure that the requirement has been
met. A table may be used to present this information, or each requirement in Section 5 may be
annotated with the method(s) to be used.

Qualification methods may include:

 Demonstration: The operation of the system, or a part of the system, that relies on observable
functional operation not requiring the use of instrumentation, special test equipment, or
subsequent analysis.
 Test: The operation of the system, or a part of the system, using instrumentation or other
special test equipment to collect data for later analysis.
 Analysis: The processing of accumulated data obtained from other qualification methods.
Examples are reduction, interpolation, or extrapolation of test results.
 Inspection: The visual examination of system components, documentation, etc.
 Special qualification methods. Any special qualification methods for the system, such as
special tools, techniques, procedures, facilities, acceptance limits, use of standard samples,
preproduction or periodic production samples, pilot models, or pilot lots.

8. Producibility
8.1. Data Rights
8.2. Parts/Components Strategy
8.2.1. Commonality of parts / subsystems
8.2.2. Advanced Material Purchases
8.2.3. Unique and Long lead Resources (castings / materials / etc)
8.2.4. Standard index / Restrictions
8.2.5. Quantity Buy
8.2.6. Strategic Sourcing
8.2.7. Equipment Management
8.2.8. Commodity Management
8.2.9. In-Service Support
8.2.10. PBL / ISEA decisions
8.3. Product Data Environment
8.3.1. CAD
8.3.2. CAM
8.3.3. Data Management
8.3.4. Selected Record Drawing Index

Page 11 of 15
 July 17, 2008
System Design Specification Guidebook Appendix E – Integrated Warfare, Combat, Weapon Systems

Attachment 1 - Statutory and regulatory requirements specified in DoDI 5000.2 enclosure 3.

8.3.5. Simulations
8.3.6. Archiving Data
8.3.7. Data Standards
8.3.8. Drawing / data extraction
8.3.9. Protocols / controls / permissions
8.4. Make / Buy Decisions
8.5. Design Build Strategy / Methodology
8.5.1. Modularity
8.5.1.1. Construction
8.5.1.2. Mission systems
8.5.1.3. Electronics
8.6. Construction / Assembly
8.6.1. Strategy
8.6.1.1. “Green field” / modify / use existing plant
8.6.1.2. Construct Build Sequencing
8.6.1.3. Facility requirements
8.6.1.3.1. Special Jigs and Fixtures
8.6.1.3.2. Special Plant Equipment
8.6.1.4. Process Flow and integration
8.6.1.4.1. Configuration control
8.6.1.4.2. Information flow
8.6.1.4.3. Assembly lines
8.6.1.5. Workforce
8.6.1.5.1. Skill level
8.6.1.5.2. Numbers (include age demographics by skill)
8.6.1.5.3. Phasing of skills over time
8.6.1.5.4. Special training programs
8.6.2. Government Furnished Property (GFP) Listing
8.6.3. Quality Assurance and Certification Strategy
8.6.3.1. Contractor
8.6.3.2. Regulatory / Statutory
8.6.3.3. By instruction
8.6.3.4. Government

9. Human System Integration

9.1. Manning and manpower assumptions
9.1.1. Operator Organization
9.2. Manning Analysis
9.3. Crewing methodology
9.3.1. Rotational crews, etc
9.4. Crew workload analysis by operation mode
9.5. Training
9.5.1. Off-board
9.5.2. On-board
9.5.3. Training status of arriving crewman
9.6. Effect of New Design Systems / Equipment
9.6.1. Human System interface requirements
9.6.1.1. Maintenance
9.6.1.2. Accessibility of equipments

10. Weapon System Supportability

Page 12 of 15
 July 17, 2008
System Design Specification Guidebook Appendix E – Integrated Warfare, Combat, Weapon Systems

Attachment 1 - Statutory and regulatory requirements specified in DoDI 5000.2 enclosure 3.

10.1. Operating Logistics
10.1.1. General Concepts
10.1.2. Maintenance Concepts and Operating Cycle
10.1.3. Equipment Selection Policy
10.1.4. Maintenance Policy
10.1.5. Arrangement and Accessibility Policy
10.1.6. Detachments Support Policy
10.2. Integrated Logistics Support
10.2.1. Integrated Logistics Support Planning
10.2.1.1. Maintenance and Repair
10.2.1.2. Support and Test Equipment (S&TE)
10.2.1.3. Special tooling / repair equipment / services
10.2.1.4. Special Refurbishment facilities and equipment
10.2.1.5. Special Disposal Facilities, Sites and Processes
10.2.1.6. Supply Support
10.2.1.7. Technical Documentation
10.2.1.8. Facilities
10.2.1.9. Packaging, Handling, Storage, and Transportation
10.2.1.10. Personnel and Training
10.2.1.11. Consumables
10.2.1.12. Spares and Repair Parts
10.3. Operability / Maintainability
10.3.1. Deployment Plans
10.3.2. Training Plans
10.3.3. Identify Training Facilities / infrastructure / simulators
10.3.4. Maintenance Support plans
10.3.5. Disposal Plans
10.3.6. OPTEMPO plans
10.3.7. Identify Special Storage Facilities and Sites
10.4. Reliability, Maintainability, and Availability

11. Risk Operational Safety, Suitability, and Effectiveness

11.1. Risk Identification
11.1.1. Identify risks and its associated root causes
11.2. Risk Analysis
11.2.1 Analyzes each root cause to determine the probability it will occur and the
consequence in terms of performance, schedule and cost
11.3 Risk Mitigation Planning
11.3.1 Identify, evaluate, and select options to set risk at an acceptable level given program
constraints and objectives
11.4 Risk Mitigation Plan Implementation
11.4.1 Execute the planned risk mitigation efforts
11.5Risk Tracking
11.5.1 Provide the ability to monitor and provide feedback on the effectiveness of the risk
mitigation execution and the status of the program’s propensity for risk
11.6 Risk Resolution- Resolve or Retire the risk
11.6.1 Determine the course of action after the risk has been mitigated to the lowest level
11.6.2 Retire the risk if mitigation is complete and there is no residual risk or if the MPM
will accept the residual risk
11.6.3 Transfer the risk if mitigation remains, but control of the mitigation resides in
another directorate

Page 13 of 15
 July 17, 2008
System Design Specification Guidebook Appendix E – Integrated Warfare, Combat, Weapon Systems

Attachment 1 - Statutory and regulatory requirements specified in DoDI 5000.2 enclosure 3.

12. Cost Analysis

12.1.1. Cost Analysis Requirements Description (CARD)
12.1.2. Program Office Life Cycle Cost Estimate
12.1.3. Cost Drivers and Risk Assessment
12.1.4. CAIV Approach
12.1.5. Unit Cost Report and LRIP Requirements
12.1.6. Acquisition Strategy Options
Information Required Applicable Statute When Required
Consideration of Technology 10 U.S.C. 2364, reference (q) Milestone (MS) A
Issues MS B
MS C
Market Research 10 U.S.C. 2377, reference (r) Technology Opportunities
15 U.S.C. 644(e)(2), reference (s) User Needs
MS A
MS B
CCA Compliance 40 U.S.C. Subtitle III, reference (l) MS A (MAIS only)
(All IT-including NSS) (See Sec. 8088, Pub. L. 107-248, reference (t) Program Initiation for Ships
enclosure 4, Table E4.T1.) (or successor appropriations act provision) MS B
MS C (if equivalent to
Full-Rate Production DR)
Full-Rate Production DR
Post-Deployment Performance 5 U.S.C. 306, reference (u) Full-Rate Production DR
Review 40 U.S.C. 11313, reference (v)
Registration of mission-critical and Sec. 8088(a), Pub. L. Program Initiation for
mission-essential information 107-248, reference (t) (or Ships
systems, successor appropriations act MS B (if Program
RCS: DD-C3I(AR)2096 provision) Initiation)
Pub. L. 106-398, Section 811, MS C (if Program
reference (w) Initiation or if equivalent
to Full-Rate Production
DR)
Full-Rate Production
DR
(After initial registration,
shall be updated
quarterly)
Benefit Analysis and Determination 15 U.S.C. 644(e), reference MS B
(applicable to bundled acquisitions) (s) MS C (if no MS B)
(part of acquisition strategy)
Beyond-LRIP Report (OSD OT&E 10 U.S.C. 2399, reference (h) Full-Rate Production
Oversight programs only) DR
Programmatic Environment Safety 42 U.S.C. 4321, reference (x) Program Initiation for
and Occupational Health Evaluation Ships
(PESHE) (Including National MS B
Environmental Policy Act MS C
(NEPA) Compliance Schedule) Full-Rate Production
DR
Spectrum Certification Compliance 47 U.S.C. 305, reference (y) MS B
(DD Form 1494) (applicable to all Pub. L. 102-538, 104, reference (z) MS C (if no MS B)
systems/equipment that require 47 U.S.C. 901-904, reference (aa)
utilization of the electromagnetic DoD Directive 4650.1, reference (ab)
spectrum) OMB Circular A-11, Part 2, reference (d)
The following information requirements are statutory, but are not applicable to MAIS acquisition programs:
Selected Acquisition Report (SAR)-- 10 U.S.C. 2432, reference (ac) Program Initiation for Ships
Reports Control Symbol (RCS): DD- MS B and annually thereafter
AT&L(Q&A)823 (MDAPs only) End of quarter following MS C
Full-Rate Production DR
Breach
Unit Cost Report (UCR)--RCS: DD- 10 U.S.C. 2433, reference (ad) Quarterly
AT&L(Q&R)1591 (MDAPs only)
Live-Fire Waiver & Alternate LFT&E 10 U.S.C. 2366, reference (ae) MS B
Plan (N/A for AISs)
(Covered Systems only)
Industrial Capabilities (part of 10 U.S.C. 2440, reference (af) MS B

Page 14 of 15
 July 17, 2008
System Design Specification Guidebook Appendix E – Integrated Warfare, Combat, Weapon Systems

Attachment 1 - Statutory and regulatory requirements specified in DoDI 5000.2 enclosure 3.

acquisition strategy) (N/A for AISs) MS C
LRIP Quantities (N/A for AISs) 10 U.S.C. 2400, reference (ag) MS B
Independent Cost Estimate (CAIG) 10 U.S.C. 2434, reference (ah) Program Initiation for Ships
and Manpower Estimate (reviewed (cost assessment only)
OUSD(P&R)) MS B
(N/A for AISs) (MDAPs Only) MS C
Full-Rate Production DR
LFT&E Report, 10 U.S.C. 2366, reference (ae) Full-Rate Production DR
RCS: DD-OT&E(AR)1845
(LFT&E-covered programs only)
Electronic Warfare (EW) T&E Sec. 220 of Pub. L. 103-160 as amended by Sec. Annually
RCS: DD-AT&L(A)2137 214 of Pub. L. 103-337, reference (ai)
(EW programs on OSD T&E
Oversight List)
Core Logistics Analysis/Source of 10 U.S.C. 2460, reference (aj) MS B
Repair Analysis (part of acquisition 10 U.S.C. 2464, reference (ak) MS C (if no MS B)
strategy) 10 U.S.C. 2466, reference (al)
Competition Analysis (Depot-level 10.U.S.C. 2469, reference (am) MS B
Maintenance $3M rule) (part of MS C (if no MS B)
acquisition strategy)
The following information requirements are statutory for MDAPs and are applicable to MAIS acquisition programs by
this Instruction:
Technology Development Strategy Sec. 803, Pub. L. 107-314, reference (an) MS A
(TDS) MS B
MS C
Acquisition Program Baseline (APB) 10 U.S.C. 2435, reference (ao) Program Initiation for Ships
MS B
MS C (updated, as necessary)
Full-Rate Production DR
Program Deviation Report 10 U.S.C. 2435, reference (ao) Immediately upon a program
deviation
Operational Test Plan 10 U.S.C. 2399, reference (h) Prior to start of operational test
(DOT&E Oversight Programs only) and evaluation
Cooperative Opportunities (part of 10 U.S.C. 2350a, reference (ap) MS B
acquisition strategy) MS C
Cooperative Opportunities (part of 10 U.S.C. 2350a, reference (ap) MS B
acquisition strategy) MS C
The following information requirements are statutory for MAIS acquisition programs and are not applicable to MDAPs:
Certification of compliance with the Sec. 8088, Pub. L. 107-248, reference (t) (or MS A
Clinger-Cohen Act successor appropriations act provision) MS B
MS C (if equivalent to
Full-Rate Production
DR)
Full-Rate Production
DR
Certification of compliance with the Sec. 8088, Pub. L. 107-248, reference (t) (or MS A
Financial Management Enterprise successor appropriations act provision) MS B
Architecture (Financial Management MS C (if equivalent to
MAIS acquisition programs only) Full-Rate Production
DR)
Full-Rate Production
DR

Page 15 of 15