Document Type

​

Overview

• Work item creation constraints — which work item types are allowed in each document
• Module folder location — automatic placement in Requirements, Design, Risks, or Testing spaces
• PowerSheet querying — document filters enable selective RTM traceability views
• Risksheet attachment — risk analysis modules reference risksheet.json configurations by document type
• Traceability relationships — document type drives valid link roles between work items

​

Document Type Enumeration

​

Property Table

​

V-Model Document Flow

​

Document Type Usage Patterns

​

Requirements Cascade (Top-Down Traceability)

• Contains: Customer Requirement work items
• Role: Voice of the customer; captures high-level needs and operational context
• Traces to: System Requirements (via ‘refines’ link role)
• Validated by: Validation Test Cases in Test Specifications

• Contains: System Requirement work items
• Role: System-level functional requirements derived from customer needs
• Default document type for all system requirements
• Traces: Refines Customer Requirements, refined by Subsystem Requirements
• Verified by: System Verification Test Cases in Test Specifications

• Contains: Subsystem Requirement work items (one per engineering subsystem)
• Role: Subsystem-level functional requirements enabling parallel team development
• Traces: Refined by Design Requirements
• Scoped by: System Element (subsystem or component)
• Verified by: Subsystem Verification Test Cases

• Contains: Design Requirement work items with subType classification (Electrical, Mechanical, Software, Labeling, Usability)
• Role: Implementation-level specifications; bridges requirements to design/test
• Traces: Refines Subsystem Requirements; refined by Characteristics
• Scoped by: System Element (component or subcomponent)
• Verified by: Design Verification Test Cases; assessed in FMEA analysis via Characteristics

​

Risk Analysis Documents (Risksheet-Enabled)

• Contains: Hazard, Harm, Failure Mode, Risk Record, Risk Control work items
• Role: Central repository for all risk assessment tables (HAZID, FMEA, Control Plans)
• Risksheet attachment: Defines table structure, column formulas, cell decorators, progress tracking
• Usage: Multiple independent Risksheet modules can exist in one document (HAZID in rows 1-20, SFMEA in rows 21-50, etc.)
• Typical documents:
  • “HAZID - AEB System” — initial hazard identification and ASIL allocation
  • “System FMEA - ECU Processing Subsystem” — failure mode analysis at subsystem level
  • “Component DFMEA - Camera Module” — design-level failure modes
  • “Process FMEA - Sensor Assembly” — manufacturing/assembly process failures
  • “Control Plan - Sensor Assembly” — measurement and reaction plan for characteristics

​

Traceability & Engineering Data Documents

• Contains: Characteristic work items with target values, tolerances, acceptance criteria
• Role: Engineering characteristics catalog; links to Design Requirements and assessed by Failure Modes
• Example: “Camera Module - Design Characteristics” contains 12 characteristics (lens focal length, sensor sensitivity, response time, etc.)

• Contains: Function work items describing system/subsystem behavioral capabilities
• Role: Functional decomposition; each function assessed by Failure Modes in FMEA
• Example: “AEB System Functions” contains obstacle detection, threat assessment, brake actuation, fallback functions

• Contains: Verification Test Case and Validation Test Case work items
• Role: Right side of V-model; establishes verification/validation evidence
• Traces: Verifies Design/System/Subsystem/Customer Requirements
• Example: “System Verification Specification - AEB” contains test procedures for obstacle detection range, braking response time, sensor fusion accuracy

​

PowerSheet Matrices (Read-Only Views)

• Contains: No work items — purely visualization layer
• Role: Dynamic traceability matrices rendered via RTM model expansion queries
• Examples:
  • “Whole RTM Sheet” — complete system traceability from Customer Requirements to Test Cases
  • “Component RTM - Camera Module” — filtered to single component’s requirements and tests
  • “System Verification Sheet” — Design Requirements to Verification Test Cases

​

Generic & Legacy Documents

• Contains: Any work item type or unstructured content
• Role: Catch-all for guides, process documentation, meeting notes, legacy imports
• Traceability: Does not participate in RTM queries or Risksheet workflows
• Recommendation: Avoid for new projects; migrate legacy content to appropriate standard types

​

Document Type Constraints & Validation

​

Work Item Creation Constraints

​

Auto-Placement via Entity Factory

# Example: Design Verification Sheet expansion creates new tests in Testing folder
expansion:
  - path: "verificationTestCases"
    entityFactory:
      createIn: "Testing/DesignVerificationSpecification"
      workItemType: "VerificationTestCase"

1. Selects the target document type (testsSpecification)
2. Navigates to the configured module folder (Testing)
3. Creates the work item in the correct document (DesignVerificationSpecification)

​

Document Type Filtering in PowerSheet

# Example: System Verification Sheet shows only tests from Testing/SystemVerificationSpecification
expansion:
  - columns:
    - field: "description"
    - field: "linkedWorkItems"
      documentFilters: 
        - documentType: "testsSpecification"
          moduleName: "SystemVerificationSpecification"

​

Risksheet Configuration Attachment

{
  "name": "System FMEA - AEB Sensor Subsystem",
  "documentType": "sfmea-risksheet",
  "columns": [
    {
      "id": "systemElement",
      "title": "System Element",
      "type": "string",
      "level": 1,
      "expand": true
    },
    {
      "id": "function",
      "title": "Function",
      "type": "workItemLink",
      "level": 2,
      "workItemType": "Function"
    },
    {
      "id": "failureMode",
      "title": "Failure Mode",
      "type": "workItemLink",
      "level": 2,
      "workItemType": "FailureMode"
    },
    {
      "id": "fmSeverity",
      "title": "S",
      "type": "enum",
      "enum": "fmea-severity"
    },
    {
      "id": "premitigationFMOccurrence",
      "title": "O",
      "type": "enum",
      "enum": "fmea-occurrence"
    },
    {
      "id": "premitigationDetection",
      "title": "D",
      "type": "enum",
      "enum": "fmea-detection"
    },
    {
      "id": "premitigationAP",
      "title": "Action Priority",
      "type": "calculated",
      "formula": "calculateActionPriority(fmSeverity, premitigationFMOccurrence, premitigationDetection)"
    }
  ]
}

​

Related Pages

• Document Types and Modules — conceptual overview of TestAuto2 document organization
• RTM Domain Model — entity types and relationships that documents constrain
• Work Item Types — detailed reference for all work item types by document category
• Workflows — document state transitions and approval workflows