DI-FACR-82242

Hardware Design Description (HDD)

The Hardware Design Description (HDD) describes the CI-wide design decisions and detailed hardware design of a Configuration Item, supporting implementation and design visibility.

Approval DateSeptember 18, 2018

AMSC Number9980

Preparing ActivityMDA

Project NumberFACR-2018-003

OPR—

DTIC ApplicableNo

GIDEP ApplicableNo

Limitation—

Applicable FormsNo

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantYes

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

Supersedes

—

DI-IPSC-81436DI-IPSC-81432

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The Hardware Design Description (HDD) describes the design of a hardware Configuration Item (CI). It describes the CI-wide design decisions and the detailed design of the hardware. The HDD may be supplemented by Interface Design Descriptions (IDDs) (DI-IPSC-81436) and System/Subsystem Design Descriptions (SSDDs) (DI-IPSC-81432), as described below.

The HDD, with its associated IDDs and SSDDs, is used as the basis for implementing the hardware design. It provides the acquirer visibility into the design and provides information needed for design support.

This DID is used when the designer is tasked to define and record the design of a hardware CI. Design pertaining to interfaces may be presented in the HDD or in IDDs.

Design pertaining to systems may be presented in the HDD or SSDDs.

This DID contains the format, content, and intended use information for the HDD. It is intended that all requirements contained herein shall apply to all applicable DoD acquisition programs through all program phases.

Preparation Instructions

1Reference documents.None

2General instructions.

2.1Automated techniques.Use of automated techniques is encouraged. The term "document" in this DID means a collection of data, regardless of its medium.

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

3Format.The contractor's format is acceptable. Format shall be machine-readable by the government.

4Content.The HDD shall contain the following:

4.1Title page or identifier.The document shall include a title page that contains the following information, as applicable: document number, volume number, version/revision number, security markings or other restrictions to document handling, date, title, hardware item 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, distribution statement. For data in a database or other alternative form, this information shall be included on external and internal labels or by equivalent identification methods.

4.2Table of contents.The document shall contain a table of contents with the number, title, and page number of each, titled paragraph, figure, table, and appendix. For data in the 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.

4.3Page numbering/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 desired data can be indexed and accessed.

4.4Response 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, the representation need occur only in the table of contents or equivalent.

4.5Multiple paragraphs and subparagraphs.Any section, paragraph, or subparagraph in this DID may be written as multiple paragraphs or subparagraphs to enhance readability.

4.6Standard data descriptions.If the contract has a data description that will be published in a standard, data-element dictionary, then tailor down this requirement in the CDRL to address receiving the information through the dictionary's entry instead of providing the description through this DID.

4.7Substitution of existing documents.Commercial or other existing documents may be substituted for all or part of this DID's content requirements if they contain the required data.

4.8The HDD shall contain the following document sections:

4.8.1Scope.This section shall contain the following paragraphs.

4.8.1.1Identification.This paragraph shall contain a full identification of the system and the hardware to which this document applies, including, as applicable, identification number(s), title(s), abbreviation(s), version number(s), and release number(s).

4.8.1.2System overview.This paragraph shall briefly state the purpose of the system and the hardware to which this document applies, it shall describe the general nature of the system and hardware; summarize the history of system development, operation, and maintenance; identify the project sponsor, acquirer, user, designer, and support agencies; identify current and planned operating sites; and list other relevant documents.

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

4.8.2Referenced 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 documents not available through normal Government stocking activities.

4.8.3CI-wide design decisions.This section shall be divided into paragraphs that are needed to present CI-wide design decisions, that is, decisions about the CI'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 hardware units that make up the CI. This section shall state when decisions are explicit in the CI requirements or are deferred to the design of the CI's hardware units. Design decisions that respond to requirements designated critical, such as those for safety, security, or privacy, shall be placed in separate paragraphs. If a design decision depends upon system states or modes, this dependency shall be indicated. Design conventions needed to understand the design shall be presented or referenced. Examples of CI-wide design decisions are the following:

4.8.3.1Design decisions regarding inputs the CI will accept and outputs it will produce, including interfaces with other systems.If part or all of this information is given in Interface Design Descriptions (IDDs), they may be referenced.

4.8.3.2Design decisions on CI behavior in response to each input or conditionincluding actions the CI will perform, response times and other performance characteristics, description of physical systems modeled, selected equations, and handling of inputs or conditions exceeding design thresholds.

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

4.8.3.4Other CI-wide design decisions made in response to requirementssuch as selected approach to providing required flexibility, availability, and maintainability.

4.8.4CI detailed design.This section shall be divided into the following paragraphs to describe each hardware unit of the CI. If part or all of the design depends on 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 other paragraphs. Design conventions needed to understand the design shall be presented or referenced. Interface characteristics of hardware units may be described here, in Section 3, or in Interface Design Descriptions (IDDs).

4.8.4.1(Project-unique identifier of a hardware unit, or designator of a group of hardware units).This paragraph shall identify a hardware unit by project-unique identifier and shall describe the unit. The description shall include the following information, as applicable: Alternatively, this paragraph may designate a group of hardware units and identify and describe the hardware units in subparagraphs. Hardware units that contain other hardware units may reference the descriptions of those units rather than repeat information.

4.8.4.1.1Unit design decisions, if any, if not previously indicated.

4.8.4.1.2Any constraints, limitations, or unusual features in the design of the hardware unit.

4.8.4.1.3The software packages used to model and generate detailed engineering drawings of the hardware unit.

4.8.5Requirements traceability.This section shall contain:

4.8.5.1Traceability from each hardware unit identified in this HDD to the CI requirements allocated to it.

4.8.5.2Traceability from each CI requirement to the hardware units to which it is allocated.

4.8.6Notes.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.

4.8.7Appendices.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. Appendixes shall be lettered alphabetically (A, B, etc.).

4.8.8The applicable issue of the documents cited hereinincluding their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.

References

—

Schema v3.0Community-maintained · Verify against ASSIST

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