Skip to content
Astera Technology

Determine which features survive a missing dependency

Apply per-feature prerequisite sets without declaring the whole service up or down.

List feature prerequisites

Synthetic features: browse needs cache K; receipt view needs K and store D; create needs D and writer W. K/D are available, W unavailable. A feature works only if all its listed prerequisites are available. No substitute path is supplied.

Feature dependency decisions
FeatureRequired setOutcome
BrowseKAvailable
Receipt viewK,DAvailable
CreateD,WUnavailable
Download editable CSV ↓

Evaluate each conjunction

  1. Fix component states
  2. Require every dependency per feature
  3. List enabled and withheld tasks

A successful browse test cannot demonstrate a feature whose dependency set includes W.

How many features remain available?

Show the worked answer

Two of three: browse and receipt view. Create is unavailable because W is missing, despite D being present.

Publish the surviving scope

Filled decision checks
CaseDecisionReason
All service downOverstates unavailable scopeTwo features still pass
All service restored after browseOverstates restorationCreate still blocked
Download editable CSV ↓

Use the same feature matrix in user-task verification after W returns. Record actual create output before enlarging the restored scope.

Related resources