Overview

Introduction

Use cases document how Personas interact with the Arda platform to achieve their operational goals. Each use case describes a distinct user-facing behavior — a specific thing a person needs to do with the system — and one or more scenarios that realize that behavior under different conditions or through different interaction paths.

Use cases are the primary vehicle for specifying and communicating product behavior. They connect the stated goals of each persona to the functional capabilities that serve those goals, and they provide the traceability link between product intent, design specifications, and implemented features.

Use cases are organized into a four-level taxonomy: Domain > Area > Use Case > Scenario. Domains are the top-level functional groupings of the platform. Areas are coherent capability groups within a domain. Use cases are distinct user-facing behaviors within an area. Scenarios are specific realizations of a use case — variations by entry point, state, or interaction path. Each element in the taxonomy carries a stable, immutable identifier defined by the Naming Convention for this section.

Functional Domain Taxonomy

The Arda platform is organized into twelve functional domains. The table below lists each domain with its code, name, a brief description, and a link to its use case sub-section.

Domain	Name	Description
`OAM`	Operation, Administration, and Maintenance	System management: tenants, users, configuration, billing
`REF`	Reference Data	Master data: items, suppliers, contacts
`RES`	Resources	Trackable assets: facilities, kanban cards, loops
`PRO`	Procurement	Order queue, purchase orders, receiving
`APP`	Application	Dashboard, navigation, layout
`GEN`	General Behaviors	Cross-cutting UX: list views, entity media, error handling
`SAC`	Shop Access	Physical device interfaces: PDF rendering
`FND`	Foundation	Shared libraries (no use cases)
`FUL`	Fulfillment	Demand orders and shipping (planned)
`OPS`	Operations	Manufacturing processes (planned)
`WFI`	Workflows and Integrations	Cross-domain choreography (planned)
`UNC`	Unclassified	Stories awaiting triage

Coverage Summary

The table below summarizes the current documented coverage by domain. Counts reflect primary use cases classified to each domain; cross-references from other domains are not double-counted. The PRO domain has the most complete coverage as it was the first domain to receive systematic classification. SAC contains only back-references to use cases classified under the domains that trigger PDF generation.

Domain	Active Areas	Use Cases	Scenarios
OAM	3 (CFG, ACT, IAM)	21	28
REF	3 (ITM, SPL, BA)	30	35
RES	2 (FAC, KC)	9	14
PRO	4 (E2E, OQ, PO, RCV)	26	75
APP	2 (DSH, NAV)	9	12
GEN	4 (MEDIA, LST, ERR, INT)	16	28
SAC	1 (PDF)	cross-refs only	—
FND	—	none	—
FUL	—	planned	—
OPS	—	planned	—
WFI	—	planned	—
UNC	—	none	—

Scenario Types

Each scenario in the taxonomy carries a type code that describes the form of the documented artifact. The type is metadata — it is not part of the immutable identifier and may change as the nature of an element is better understood.

The current type codes are:

US — User Story. Written in the “As a… I want… so that…” form. Captures a user need from the persona’s perspective.
UC — Use Case. An actor-goal behavioral specification describing interaction steps, pre- and post-conditions, and alternative paths.
FS — Functional Scenario. A design rule, data rule, or system behavior constraint. Typically describes what the system must do rather than what a user does.

The type code set is intentionally open. Additional codes may be introduced as new artifact types emerge. For the full identifier format, numbering rules, and immutability rules, see the Naming Convention page.