4.1 — Analysing Requirements and Use Cases

CCAO-F Domain 4 · Task 4.1

What You Need to Know

Claude structures; the human validates and owns the result.

Structure from Mess

Real requirements arrive as complaint threads, meeting notes, survey comments. Claude clusters them into themes, separates what people asked for from what they appear to need, surfaces incompatible demands, and names what nobody mentioned.

A Theme Is a Hypothesis

A theme Claude names is a hypothesis about your input, not a finding about your business. The people whose requirements it describes must confirm it before anything gets designed on top.

The Shape of a Strong Candidate

• Language-shaped work (drafting, summarising, reformatting, explaining, comparing)
• Material needed is material you can provide
• Output can be checked by someone competent to check it
• High volume, or the blank page is the expensive part

Weak candidates need authority to decide, depend on information Claude has no access to, or are relationship work rather than document work.

The Checker Test

If you couldn’t tell whether the answer was wrong, you’re not ready to use Claude on that task. Without a checker, a wrong output passes as easily as a right one. High stakes call for a competent checker in the process, not abandoning the drafting help.

Key Concept: When Claude’s freshly clustered themes are on the table, take them back to the people who own the requirements before design begins.

Exam Traps

• Adopting Claude’s themes as validated findings because they arrived quickly and read plausibly
• Handing Claude the decision along with the analysis
• Ruling work out as too important for Claude to touch