---
esco_uri: http://data.europa.eu/esco/skill/f28617ad-afdd-4041-814c-216153a38998
esco_label: "analyse software specifications"
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
---

# analyse software specifications — Software Engineer

As a Software Engineer, 'analysing software specifications' isn’t about *reading* requirements; it’s about proactively identifying what’s missing, ambiguous, or technically infeasible *before* you start coding. Daily tasks involve dissecting documents (user stories, BRDs, API contracts) to pinpoint functional needs ('the system must allow users to reset passwords') and non-functional ones ('the system must handle 1000 concurrent users'). You'll often create clarifying questions for Product Owners/Business Analysts – not just 'what', but also 'how much?', 'under what conditions?', and 'what are the edge cases?'. Tools used include requirements management systems (Jira, Azure DevOps), modelling tools (UML diagrams if applicable), and even simple spreadsheets to track open questions.

## Weitere Anreicherung

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