Files

T

Stefan Lohmaier 247b8311f3 refactor(i18n): rename vorlagen/ -> templates/, *-vorlage -> *-template

Final German naming cleanup in dev-process:
- vorlagen/                            -> templates/
- vorlagen-word/                       -> templates-word/
- tools/generate_word_vorlagen.sh      -> tools/generate_word_templates.sh
- *-vorlage.md / *-vorlage.docx        -> *-template.md / *-template.docx
- Review-Protokoll-vorlage.*           -> Review-Minutes-template.*
- angebot-vorlage.*                    -> quote-template.*
- angebot-beispiel.html                -> quote-example.html

All references in README.md, toolstack/toolstack.md, build_word_template.py,
and generate_word_templates.sh updated. The master Word style template
(slohmaier-doc-template.docx) was already English-named.

The dev-process repo is now fully English in both content and structure.

2026-05-12 12:09:06 -07:00

3.1 KiB

Raw Blame History

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).

3.1 KiB Raw Blame History