Requirements Analysis

Conduct a systematic requirements analysis for [PRODUCT/SYSTEM/PROJECT].

**Context:**
- Project goal: [GOAL]
- Stakeholders: [INVOLVED PARTIES]
- Technical context: [TECH STACK / PLATFORM]
- Constraints: [BUDGET, TIME, LEGAL]

**Analysis steps:**

**1. Requirements Elicitation**
Structure requirements into:
- Functional requirements (what should the system do?)
- Non-functional requirements (how should it do it?)
  - Performance, scalability, security, usability, availability
- Business requirements
- Technical constraints

**2. Requirements Structuring**
Formulate requirements using the SMART principle:
- Specific, Measurable, Achievable, Relevant, Time-bound
- User stories: "As a [role] I want [feature] so that [benefit]"
- Acceptance criteria (definition of done)

**3. Prioritization (MoSCoW)**
- Must have: essential for MVP
- Should have: important but not a showstopper
- Could have: nice-to-have
- Won't have (this time): explicitly excluded

**4. Dependencies & Conflicts**
- Technical dependencies between requirements
- Conflict potential between stakeholder interests
- Clarification needs and open questions

**5. Requirements Traceability**
- Map each requirement to a strategic goal
- Ensure testability of each requirement

Create a clear backlog as a summary.

Replace placeholders in [square brackets]: [PRODUCT/SYSTEM/PROJECT][GOAL][INVOLVED PARTIES][TECH STACK / PLATFORM][BUDGET, TIME, LEGAL][role][feature][benefit]