Development Framework
=====================

This demo project applies a traceability-driven development framework based on TDD and V-Model practices.

It is intended to showcase how Toor Connect structures firmware development and traceability in practice.

Toor Connect: `www.toorconnect.com <https://www.toorconnect.com>`_

Framework Intent
----------------

- Demonstrate an end-to-end firmware method from client intent to verification artifacts.
- Keep requirements, architecture, detailed design, verification, and implementation explicitly linked.
- Provide a practical baseline that can be adapted to different sectors and standards.

Core Principles
---------------

- **TDD-oriented implementation:** implementation is guided by tests and detailed design.
- **V-Model alignment:** definition stages are paired with verification stages.
- **Incremental elaboration:** requirements guide architecture, and architecture guides detailed design.
- **Continuous traceability:** every level references upstream intent and downstream verification.

Lifecycle Steps
---------------

.. list-table::
   :header-rows: 1
   :class: dd-fullwidth-table dd-no-filter

   * - Step
     - Purpose
     - Main Output
   * - 1. Client Intent
     - Capture goals, constraints, safety expectations, and integration context.
     - Shared technical brief.
   * - 2. Requirements
     - Define measurable, classified, testable requirements with acceptance criteria.
     - Traceable requirement baseline.
   * - 3. Architecture
     - Define components, interfaces, connections, and ADR decisions.
     - Traceable architecture baseline.
   * - 4. Detailed Design
     - Define SW units, relations, interface realizations, static and dynamic behavior.
     - Traceable detailed design baseline.
   * - 5. Verification
     - Define unit, integration, and acceptance plans and test cases.
     - Traceable verification baseline.
   * - 6. Implementation & Execution
     - Implement firmware and execute tests with evidence and defect closure.
     - Verified implementation baseline.

Traceability Backbone
---------------------

- Requirements trace to architecture components and SW interfaces.
- Architecture traces to SW units, SW unit relations, and interface realizations.
- Verification traces to requirements, SW interfaces, SW unit relations, SW units, and sequences/timing budgets.
- Quality Assurance checks enforce core traceability consistency across the model.

Adaptability To Sector Standards
--------------------------------

- The framework is sector-agnostic and can be tailored to different ISO/regulatory contexts.
- Adaptation is mainly done by tuning required rigor:
  - Evidence depth
  - Review gates
  - Verification scope and acceptance criteria strictness
- The workflow remains stable while schemas/checks can be extended per domain needs.

Review & Approval Gates
-----------------------

.. list-table::
   :header-rows: 1
   :class: dd-fullwidth-table dd-no-filter

   * - Gate
     - Scope
     - Entry Criteria
     - Exit Criteria
     - Approver
   * - G1 Requirements Baseline
     - Requirement set and acceptance criteria quality.
     - Client intent and constraints captured.
     - Requirements classified, measurable, and reviewed.
     - Systems Lead
   * - G2 Architecture Baseline
     - Components, interfaces, and connections.
     - Requirements baseline approved.
     - Architecture traceability to requirements validated.
     - Architecture Lead
   * - G3 Detailed Design Baseline
     - SW units, relations, interface realizations, dynamic behavior.
     - Architecture baseline approved.
     - Detailed design traceability and consistency validated.
     - Software Lead
   * - G4 Verification Baseline
     - Unit, integration, and acceptance plans/cases.
     - Detailed design baseline approved.
     - Verification coverage and links validated.
     - Verification Lead
   * - G5 Release Baseline
     - Release notes, QA readiness, and baseline decision.
     - Verification baseline approved.
     - Release readiness checks pass and findings accepted.
     - Project Owner