feat(i18n): dev-process repo in English

- README.md: full English rewrite
- All 13 vorlagen MD templates hand-translated:
  PID, PM-Plan, QA-Plan, SWE-Plan, Test-Plan,
  SA, SWA, Review-Protokoll, Non-Conformity,
  MISRA-Deviation-Permit, MISRA-Deviation-Record,
  Traceability-Matrix, angebot (quotation)
- Master Word template (slohmaier-doc-template.docx) regenerated
  in English: cover page, document control, TOC headers,
  classification banner all English
- All derived Word vorlagen regenerated from English MD sources

Still to translate: toolstack.md, gitea-aspice-setup.md
This commit is contained in:
Stefan Lohmaier
2026-05-12 03:42:35 -07:00
parent 6e458ae76f
commit d5cfec9e42
25 changed files with 774 additions and 875 deletions
+48 -86
View File
@@ -1,106 +1,68 @@
# Quality Assurance Plan (QA-Plan)
# Quality Assurance Plan (QA Plan)
| Feld | Wert |
|-----------------|-------------------------------|
| Projekt | [Projektname] |
| Datum | [YYYY-MM-DD] |
| Version | [1.0] |
| Status | [Entwurf / Freigegeben] |
| ASIL | [QM / A / B / C / D] |
| Field | Value |
|-----------------|--------------------------------|
| Project | [Project name] |
| Date | [YYYY-MM-DD] |
| Version | [1.0] |
| Status | [Draft / Released] |
---
## 1. QA-Aktivitaeten pro Phase
## 1. Quality goals
| Phase | QA-Aktivitaet | Verantwortlich |
|------------------------|--------------------------------------------------------|----------------|
| Anforderungsanalyse | Review der Anforderungen (Vollstaendigkeit, Konsistenz, Testbarkeit) | QA / Reviewer |
| Architektur | Architektur-Review (Modularitaet, Safety-Konzept) | QA / Reviewer |
| Implementierung | Code-Review (MR-Approval), MISRA-Pruefung (CI) | Reviewer / CI |
| Integration & Test | Test-Review, Coverage-Pruefung, Traceability-Check | QA / CI |
| Verifikation | Gesamtpruefung: alle Kriterien erfuellt? | QA |
| Release | Release-Audit: alle Work Products vollstaendig? | QA |
- [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. Zu pruefende Work Products
## 2. Quality measures
| Work Product | Review-Art | Pruefkriterien |
|----------------------------------|------------------|---------------------------------------------|
| PID | Peer Review | Vollstaendig, konsistent mit Vertrag |
| PM-Plan | Peer Review | Realistisch, Risiken adressiert |
| Software Requirements | Technical Review | Eindeutig, testbar, ASIL zugeordnet |
| Architektur-Dokumentation | Technical Review | Modular, Schnittstellen definiert, Safety-Konzept |
| Quellcode | Peer Review (MR) | MISRA-konform, getestet, lesbar |
| Unit Tests | Peer Review | Abdeckung, Randfaelle, Traceability |
| Testberichte | Peer Review | Pass/Fail dokumentiert, Coverage erreicht |
| MISRA Compliance Report | Peer Review | Abweichungen dokumentiert und genehmigt |
| Traceability-Matrix | QA-Pruefung | Keine Luecken, bidirektional |
| 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-Arten
## 3. Review obligations
| Review-Art | Teilnehmer | Formalitaet | Wann |
|---------------------|-------------------------------|-------------|----------------------------------|
| Peer Review | 1 Reviewer | Niedrig | Jeder MR, Dokument-Aenderungen |
| Technical Review | 2+ Reviewer, inkl. Tech Lead | Mittel | Architektur, Safety-Code, Plaene |
| Inspektion | Moderator + 2+ Reviewer | Hoch | Safety-kritische Artefakte (ASIL C/D) |
| 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 |
Peer Reviews laufen ueber GitLab MR-Approvals. Technical Reviews und Inspektionen werden zusaetzlich mit Review-Protokoll dokumentiert.
## 4. Non-conformity management
## 4. Entry/Exit-Kriterien
Deviations from plans or requirements are documented as a non-conformity (NC):
### Entry-Kriterien (Beginn einer Phase)
- Path: `docs/non-conformities/NC-XXX.docx`
- Severity: Critical / Major / Minor
- Corrective action and verification tracked
- Closure criterion: corrective action verified
| Phase | Entry-Kriterien |
|----------------------|--------------------------------------------------------|
| Architektur | Requirements reviewed und freigegeben |
| Implementierung | Architektur reviewed und freigegeben |
| Integration & Test | Code-Reviews abgeschlossen, Unit Tests gruen |
| Verifikation | Alle Tests durchgefuehrt, Coverage gemessen |
| Release | Alle Exit-Kriterien der Verifikation erfuellt |
## 5. Audit preparation
### Exit-Kriterien (Abschluss einer Phase)
Audit readiness is maintained continuously:
| Phase | Exit-Kriterien |
|----------------------|--------------------------------------------------------|
| Anforderungen | Alle Requirements reviewed, ASIL zugeordnet, testbar |
| Architektur | Architektur reviewed, Schnittstellen definiert |
| Implementierung | MISRA-konform, Unit Tests gruen, Coverage-Ziel erreicht |
| Integration & Test | Integrationstests gruen, keine offenen Critical Findings |
| Verifikation | Traceability vollstaendig, alle Findings geschlossen oder bewertet |
| Release | Alle Work Products vollstaendig, QA-Freigabe erteilt |
- 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
## 5. Non-Conformity-Prozess
## 6. Improvement measures
1. Abweichung wird erkannt (Review, Audit, Test)
2. Non-Conformity Report erstellen (GitLab Issue, Label: `non-conformity`)
3. Schweregrad zuweisen: Critical / Major / Minor
4. Ursachenanalyse durchfuehren
5. Korrekturmassnahme definieren und umsetzen
6. Wirksamkeitspruefung nach Umsetzung
7. Issue schliessen mit Verweis auf Korrekturnachweis
**Eskalation:** Critical Non-Conformities werden sofort an den Auftraggeber gemeldet.
## 6. Reporting an Management
| Report | Haeufigkeit | Inhalt |
|---------------------------|------------------|-------------------------------------------|
| QA-Status-Report | Pro Meilenstein | Offene Findings, NC-Status, Coverage-Stand |
| Meilenstein-Bewertung | Pro Phase-Ende | Entry/Exit-Kriterien geprueft |
| Release-Bewertung | Vor Release | Gesamtbewertung aller QA-Kriterien |
## 7. QA-Metriken
| Metrik | Ziel | Messung |
|---------------------------------|-------------------------|----------------------------------|
| Requirement Coverage | 100% | Anforderungen mit verlinktem Test |
| Code Coverage (Statement) | >= [X]% | gcov/lcov in CI |
| Code Coverage (Branch) | >= [X]% | gcov/lcov in CI |
| MC/DC Coverage (falls ASIL C/D) | >= [X]% | MCDC-Star / kommerziell |
| MISRA Violations | 0 (oder alle genehmigt)| Cppcheck MISRA-Addon in CI |
| Offene Findings (Critical) | 0 vor Release | GitLab Issues |
| Offene Non-Conformities | 0 Critical/Major | GitLab Issues |
| Review-Abdeckung | 100% MRs reviewed | GitLab MR-Approvals |
- Lessons-learned note at each sprint closure under `docs/lessons-learned/`
- Quarterly retrospective with the team
- Updates to this plan are versioned and reviewed
---
*Aenderungen an diesem Plan werden im GitLab-Wiki versioniert.*
*Changes to this plan are versioned in the Gitea wiki.*