---
esco_uri: http://data.europa.eu/esco/skill/59ea80e1-463a-4dba-82c6-d0b6d577d532
esco_label: "technical drawings"
relation: essential
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
---

# technical drawings — Software Engineer

As a Software Engineer, 'technical drawings' isn’t about architectural blueprints! It translates into the ability to *visualize* and *communicate* system designs – often using UML diagrams (class, sequence, activity), entity-relationship models for databases, or even simple flowcharts. You won't be drafting in AutoCAD, but you *will* use tools like draw.io, Lucidchart, Miro, PlantUML (text-to-diagram) or integrated features within IDEs/collaboration platforms (like VS Code extensions or Figma).  The 'symbols', 'perspectives', and 'notation systems' are these diagramming conventions; knowing them ensures everyone on the team understands the intended logic and data flow.

## Weitere Anreicherung

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