# Quality Assurance Plan (QA Plan)

| Field           | Value                          |
|-----------------|--------------------------------|
| Project         | [Project name]                 |
| Date            | [YYYY-MM-DD]                   |
| Version         | [1.0]                          |
| Status          | [Draft / Released]             |

---

## 1. Quality goals

- [Goal 1, e.g. "100% MISRA Required compliance"]
- [Goal 2, e.g. "Statement coverage ≥ 90% for ASIL-D"]
- [Goal 3, e.g. "Zero critical static-analysis findings on release"]

## 2. Quality measures

| Measure                  | Tool / Method                | Frequency        | Owner    |
|--------------------------|------------------------------|------------------|----------|
| Traceability check       | `doorstop check`             | every push       | dev      |
| MISRA check              | Cppcheck + MISRA addon       | every push       | dev      |
| Static analysis          | Cppcheck, clang-tidy         | every push       | dev      |
| Unit tests               | CppUTest                     | every push       | dev      |
| Coverage                 | gcov / lcov                  | every push       | dev      |
| Peer review              | Gitea PRs                    | every change     | reviewer |
| Architecture review      | Technical review             | on changes       | TL       |

## 3. Review obligations

| Artefact                       | Review type        | Min. approvers |
|--------------------------------|---------------------|-----------------|
| Requirements                   | Technical review    | 1               |
| Architecture element           | Technical review    | 2               |
| Code (QM / ASIL-A/B)           | Peer review         | 1               |
| Code (ASIL-C/D)                | Technical review    | 2               |
| Plans and reports              | Peer review         | 1               |
| MISRA deviation permit         | Technical lead      | 1               |

## 4. Non-conformity management

Deviations from plans or requirements are documented as a non-conformity (NC):

- Path: `docs/non-conformities/NC-XXX.docx`
- Severity: Critical / Major / Minor
- Corrective action and verification tracked
- Closure criterion: corrective action verified

## 5. Audit preparation

Audit readiness is maintained continuously:

- Git history is the audit trail (no direct push to `main`)
- Documents are versioned in the repo
- Traceability matrices are generated on every CI run
- MISRA records and deviation permits are stored under `misra/`
- Test and coverage reports are stored as CI artefacts

## 6. Improvement measures

- Lessons-learned note at each sprint closure under `docs/lessons-learned/`
- Quarterly retrospective with the team
- Updates to this plan are versioned and reviewed

---

*Changes to this plan are versioned in the Gitea wiki.*