Design Documentation¶
This section contains the normative technical documentation for the Microsoft Fabric Retail Demo. It is separated from the task-focused guides so users can learn, deploy, and present the demo without first navigating implementation contracts.
Start with Architecture when you want a plain technical picture of the components and data flow. Use Requirements to understand the outcomes the solution must achieve. Use Specifications when you need the exact interface, schema, workflow, or failure behavior. Use Security to understand threats, trust boundaries, and controls.
Readers who are new to Fabric can review the plain-language glossary before continuing.
| Area | What it answers |
|---|---|
| Architecture | What components exist, how they connect, and where data moves |
| Requirements | What outcomes and constraints the solution must satisfy |
| Specifications | Exactly how interfaces, schemas, workflows, states, and errors behave |
| Security | What can go wrong and which controls reduce the risk |
Start with the architecture overview for a technical orientation. Use requirements and specifications when implementing or validating a specific capability.