---
esco_uri: http://data.europa.eu/esco/skill/17924c75-45f4-4593-afac-eea0d51f04b5
esco_label: "defence standard procedures"
relation: optional
onet_soc: 15-1252.00
source: model-knowledge
confidence: high
qa_count: 0
generator: gemma3:27b (prompt-designed and spot-checked by Claude)
generated: 2026-07-10
---

# defence standard procedures — Software Engineer

For a Software Engineer working on defence systems, 'defence standard procedures' isn’t about *building* defences – it’s about rigorously adhering to pre-defined processes documented in standards like STANAGs (NATO Standardization Agreements) or similar national/organizational equivalents. Daily this translates into specific coding practices (MISRA C/C++ for safety-critical code, secure coding guidelines), documentation requirements far exceeding typical commercial software (traceability matrices linking requirements to design, implementation, and testing), and strict configuration management using tools like Git with enforced branching strategies and code review processes. It means understanding *why* a process exists – often related to interoperability with allied systems or ensuring resilience against specific threats – not just blindly following it.

## Weitere Anreicherung

Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).
