DSDS Use Cases Definition

2 definitions in this file:

useCases
useCase

Identifies this document block as a use-cases spec.

Scenario-driven use cases. They describe when this artifact is or is not the right choice. Order matters: tools SHOULD keep it for display. Authors SHOULD lead with recommended scenarios.
Min items: 1

The umbrella purpose statement for the artifact — one or two sentences saying what it is for, framing the use cases in items (e.g., 'Buttons trigger immediate actions. They are the primary mechanism for initiating changes within a surface.').

References: richText, useCase

{ "kind": "useCases", "items": [ { "stance": "recommended", "description": "When the user needs to commit a destructive or high-stakes action (e.g., Save, Confirm, Delete) and that action is the primary task on the surface." }, { "stance": "recommended", "description": "When triggering a state change inside the application — submitting a form, opening a dialog, or moving to the next step of a workflow." }, { "stance": "discouraged", "description": "When the action navigates the user to a different page or external URL.", "alternative": { "identifier": "link", "rationale": "Links carry semantic meaning for navigation, are crawlable by assistive technology, and respect the user's default browser behavior (open in new tab, copy URL, etc.)." } } ] }

Describes the scenario. Should be concrete and situation-driven — describe the user's situation, not the artifact's features.

Whether this scenario is one to follow ('recommended') or to avoid ('discouraged').

The recommended alternative artifact for this scenario. Usually given for discouraged scenarios, to point the reader toward a better-suited component, pattern, or token.

References:

richText

[ { "stance": "recommended", "description": "When the user needs to commit a destructive or high-stakes action (e.g., Save, Confirm, Delete) and that action is the primary task on the surface." }, { "stance": "recommended", "description": "When triggering a state change inside the application — submitting a form, opening a dialog, or moving to the next step of a workflow." }, { "stance": "discouraged", "description": "When the action navigates the user to a different page or external URL.", "alternative": { "identifier": "link", "rationale": "Links carry semantic meaning for navigation, are crawlable by assistive technology, and respect the user's default browser behavior (open in new tab, copy URL, etc.)." } }, { "stance": "discouraged", "description": "When the surface needs a long list of inline choices that the user can toggle on and off.", "alternative": { "identifier": "chip", "rationale": "Chips communicate selection and removal affordances. Using a button for each option implies an action rather than a togglable selection." } } ]