<!-- owner: RStack developed by Richardson Gunde -->

# Requirement Analysis Skill

## Classification Framework
- **Functional (FR)**: What the system must DO
- **Non-Functional (NFR)**: How the system must PERFORM
- **Constraints**: Limits on the solution

## Prioritization (MoSCoW)
- CRITICAL: System unusable without it
- HIGH: Significant business value
- MEDIUM: Nice-to-have for Phase 1
- LOW: Future consideration

## Actor Identification
- End Users (customers, patients, students, etc.)
- Operators (admin, managers, staff)
- System Actors (schedulers, APIs, background jobs)
- External Parties (third-party services, regulators)

## Implicit Requirements (Always Add)
- User authentication and session management
- Audit logging for sensitive operations
- Input validation on all user inputs
- Data backup and recovery strategy
- Role-based access control (RBAC)
- Error handling and user-friendly error messages
- Responsive design for mobile users
