Stefan Lohmaier
d5cfec9e42
- 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
80 lines
3.1 KiB
Markdown
80 lines
3.1 KiB
Markdown
# Non-Conformity Report
|
|
|
|
| Field | Value |
|
|
|------------------|--------------------------------|
|
|
| NC ID | NC-[XXX] |
|
|
| Date | [YYYY-MM-DD] |
|
|
| Author | [Name] |
|
|
| Status | [Open / In progress / Closed] |
|
|
|
|
---
|
|
|
|
## 1. Reference
|
|
|
|
| Field | Value |
|
|
|-----------------------|-----------------------------------------------|
|
|
| Kind | [Process deviation / Product deviation] |
|
|
| Affected process | [e.g. SWE.4 Implementation, SUP.1 QA] |
|
|
| Affected work product | [e.g. module XY, requirement SWR-042, test plan] |
|
|
| Gitea reference | [Issue link / PR link / wiki page] |
|
|
| Discovered in | [Review / audit / test / CI pipeline] |
|
|
|
|
## 2. Description of deviation
|
|
|
|
[What exactly deviates? Describe concretely. Reference the standard or process specification.]
|
|
|
|
## 3. Severity
|
|
|
|
| Severity | Definition |
|
|
|--------------|------------------------------------------------------------------|
|
|
| [ ] Critical | Safety-relevant or complete absence of a required work product |
|
|
| [ ] Major | Significant deviation that affects quality or compliance |
|
|
| [ ] Minor | Minor deviation, no direct effect on safety or function |
|
|
|
|
**Assigned severity:** [Critical / Major / Minor]
|
|
|
|
## 4. Root-cause analysis
|
|
|
|
[Why did the deviation occur? Possible categories:]
|
|
- Process not known / not trained
|
|
- Process not applicable / unrealistic
|
|
- Oversight / human error
|
|
- Tool error
|
|
- Time pressure / lack of resources
|
|
- Requirement unclear
|
|
|
|
**Description:** [Specific cause]
|
|
|
|
## 5. Corrective action
|
|
|
|
| Field | Value |
|
|
|-----------------------|-----------------------------------------------|
|
|
| Action | [What is done to fix the deviation] |
|
|
| Responsible | [Name] |
|
|
| Due | [YYYY-MM-DD] |
|
|
|
|
### Preventive action (optional)
|
|
|
|
[What is done so that this type of deviation does not occur again?]
|
|
|
|
## 6. Effectiveness check
|
|
|
|
| Field | Value |
|
|
|-----------------------|-----------------------------------------------|
|
|
| Verified by | [Name] |
|
|
| Verification date | [YYYY-MM-DD] |
|
|
| Action effective | [Yes / No] |
|
|
| Evidence | [Gitea issue link / commit / review] |
|
|
|
|
## 7. Closure
|
|
|
|
| Field | Value |
|
|
|-----------------------|-----------------------------------------------|
|
|
| Status | [Closed / Reopened] |
|
|
| Closed by | [Name] |
|
|
| Date | [YYYY-MM-DD] |
|
|
|
|
---
|
|
|
|
*This report is kept as a Gitea issue (label: `non-conformity`).*
|