# Requirements Template

## Fields

### BUSINESS_PROBLEM (mandatory)
What business problem or opportunity does this address?
- Must be stated from a business perspective, not a technical one.
- A correct answer describes a real-world problem, gap, or need.
- INVALID: describing a solution, deliverable, or technical artifact.
- INVALID: "We need DnAML definitions for a Gold Layer."
- VALID: "The sales team cannot analyze order profitability by region in a single view."

### DECISION_SUPPORTED (mandatory)
Which business decisions will this result enable, and who makes them?
- Names a concrete decision and a concrete decision-maker.
- INVALID: "The output will be consumed by BI tools."
- VALID: "The sales director decides which customer segments to prioritize each month."

### SUCCESS_CRITERIA (mandatory)
How will the user verify the result is correct and complete?
- Measurable and testable from a business perspective — without reading code or schemas.
- INVALID: "All DnAML definitions are written and syntactically valid."
- VALID: "The sales team can answer questions A, B, C without additional data manipulation."

### SCOPE_OUT (mandatory)
What is explicitly NOT part of this phase?
- Even if nothing is excluded, this must be stated explicitly.

### CONSTRAINTS (mandatory)
What rules, naming conventions, or limitations must be respected?
- Technical, organizational, regulatory, or timing constraints.
- Even if there are no special constraints, this must be stated explicitly.

### OPEN_ITEMS (optional)
What is still unclear or will be decided during the project?
- May be empty.
