APSCA Workshop Discovery Definitions

A major, stable business capability that organizes the system into meaningful, long-lived areas.

Defines "what the system does" at the highest level. Anchor points for organizing epics.

A coherent workflow or responsibility that groups related user stories under a feature.

Represents "how" a feature is delivered. Groups stories that share context.

A verifiable business rule or constraint that the system must enforce.

Captures "what must be true" regardless of implementation. Must remain valid even if UI, workflow, or technology changes. Traces to artifacts.

A document or specification describing business rules or reference data.

Authoritative source for requirements. Describes sources of truth, not system behavior. Policies, rules, or catalogs the system respects.

A user-centered capability with acceptance criteria and test intent. Derived from Epics and Requirements.

Atomic unit of delivery. Describes what a user can do with verification criteria.

A planned delivery milestone that binds versions to a specific date.

Answers "what shipped when?" Timeline overlay tracking delivery events.