Hardware Design Document (HWDD)

Definition

A hardware design document (HWDD) is the design work product that formally documents the design of the hardware components to be fabricated.

Objectives

The typical objectives of a hardware design document are to:

• Formally documents the design of the hardware components to be fabricated.

Benefits

The typical benefits of a hardware design document are to:

• Enable hardware engineers to fabricate the hardware components.
• Form the basis for hardware unit testing.

Contents

The typical contents of a hardware design document are:

• Hardware Components:
  • Component X Design:
    • Component Description
    • Component Interfaces
    • Component Structure
    • Parts List
• Appendices:
  • Major Issues
  • TBDs
  • Assumptions

Stakeholders

The typical stakeholders of a hardware design document are:

• Producers:
  • Hardware Development Team
• Evaluators:
  • Hardware Inspection Team
• Approvers:
  • Technical Leader
  • Project Manager
  • Customer Representative
• Maintainers:
  • Hardware Development Team
• Users:
  • Hardware Development Team

Phases

A hardware design document is typically developed during the following phases:

• Business Strategy: Not Applicable
• Business Optimization: Not Applicable
• Initiation: Not Applicable
• Construction: Completed
• Delivery: Maintained
• Usage: Maintained
• Retirement: Archived

Preconditions

A hardware design document can typically be started if the following preconditions hold:

• The construction phase is started.
• The hardware development team is staffed and trained.
• The associated conventions (e.g., content and format standard, template) are ready.

Inputs

The typical inputs to a hardware design document include:

• Work Products:
  • System Requirments Specification
  • Domain Model Document
  • Glossary
  • System Architecture Document
  • Contact Center Architecture Document
  • Contact Center Architecture Document
• Stakeholders:
  • Hardware Architect
  • Hardware Engineer

Guidelines

• No hardware design document is required unless a hardware component is to be designed and fabricated as part of the endeavor.

Conventions

Hardware design documents are constrained by the following conventions:

• Work Flow
• Content and Format Standard
• MS Word Template
• XML Template
• Inspection Checklist

Examples

• Example Hardware Design Document