Strategy: Use Cases for Human Workflows

This document provides a high-level overview of Use Case documentation for WepNG. For detailed templates and best practices, refer to the Specification Extraction Skill.

[!TIP] Detailed Instructions: See Specification Extraction Skill for templates and step-by-step guidance.

---

1. When to Use

Use Cases are the right format for Explicit Tasks involving:

• Multi-step human-computer interactions
• Decision points requiring human judgment
• UI-driven processes

NOT for: Pure business logic (use Gherkin), State machines (use State Diagrams).

---

2. Format: Cockburn "Fully Dressed Lite"

Section	Content
Summary	ID, Title, Actor, Trigger, Scope
Preconditions	What must be true before starting
Main Success Scenario	Numbered steps: Actor → System
Extensions	Alternative flows (2a, 3b, etc.)
Business Rules	BR-IDs referenced at specific steps

---

3. Template

See: .agent/skills/specification_extraction/templates/use_case_template.md

---

4. Naming Convention

UC-[MODULE]-[XXX]

Examples:

• UC-OMGT-001 – Assign Callback
• UC-BO-003 – Create Fee Configuration

---

5. Area Coverage Approach

Document Use Cases by functional area, not by screen:

• user_tasks/callbacks/ – All callback-related UCs
• user_tasks/orders/ – Order management UCs

---

Related Resources

• Skill: Specification Extraction
• Template: .agent/skills/specification_extraction/templates/use_case_template.md
• Best Practices: Use Case Best Practices