Files
dev-process/vorlagen/MISRA-Deviation-Record-vorlage.md
T
Stefan Lohmaier d5cfec9e42 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
2026-05-12 03:42:35 -07:00

71 lines
3.0 KiB
Markdown

# MISRA Deviation Record
| Field | Value |
|------------------|--------------------------------|
| Deviation ID | DEV-[XXX] |
| Date | [YYYY-MM-DD] |
| Author | [Name] |
---
## 1. Rule
| Field | Value |
|-------------------|----------------------------------------------------|
| Rule number | [e.g. Rule 11.3] |
| Category | [Required / Advisory / Mandatory] |
| Rule text | [Exact text of the MISRA rule] |
| Standard | [MISRA C:2012 / MISRA C:2023] |
## 2. Location
| Field | Value |
|-------------------|----------------------------------------------------|
| File | [e.g. src/drivers/watchdog.c] |
| Line(s) | [e.g. 142-145] |
| Function | [e.g. wdg_set_timeout()] |
| Git commit | [commit hash] |
| Gitea reference | [PR link or issue link] |
## 3. Rationale
[Why is the deviation technically acceptable in this specific case?]
Possible rationales:
- Hardware access requires type conversion
- Compiler-specific behaviour is defined and tested
- Alternative implementation would be disproportionately complex
- Rule is not safety-relevant in this context
**Specific rationale:** [Fill in here]
## 4. Risk assessment
| Aspect | Assessment |
|---------------------------|-----------------------------------------------|
| Safety relevance | [None / Low / Medium / High] |
| Fault potential | [Description of potential faults] |
| Mitigation | [Which tests / measures cover the code] |
| Residual risk | [Assessment of the residual risk] |
## 5. Reference to deviation permit
| Field | Value |
|-----------------------|-----------------------------------------------|
| Permit exists | [Yes / No] |
| Permit ID | [PER-XXX or "n/a"] |
If no permit exists: this deviation is a single-case approval.
## 6. Approval
| Field | Value |
|-------------------|----------------------------------------------------|
| Approved by | [Name, role] |
| Date | [YYYY-MM-DD] |
| Evidence | [Gitea PR approval / signature] |
---
*This record is kept in the repository under `docs/misra/` or as a Gitea issue.*