Skip to content

Restructure use-case template to proper use-case format#35

Open
Artur- wants to merge 2 commits into
mainfrom
use-case-is-use-case
Open

Restructure use-case template to proper use-case format#35
Artur- wants to merge 2 commits into
mainfrom
use-case-is-use-case

Conversation

@Artur-
Copy link
Copy Markdown
Member

@Artur- Artur- commented May 23, 2026

Replace the user-story/use-case hybrid with a Jacobson-style template: Goal, Actors, Preconditions, Trigger, numbered Main Flow, Alternative Flows, Postconditions, Business Rules. Drop Acceptance Criteria — the flows and rules are the acceptance criteria.

Update new-use-case interview to cover the new sections and use-case-tests coverage requirements to reference flows and rules instead of AC.

Addresses #33.

Replace the user-story/use-case hybrid with a Jacobson-style template:
Goal, Actors, Preconditions, Trigger, numbered Main Flow, Alternative
Flows, Postconditions, Business Rules. Drop Acceptance Criteria — the
flows and rules are the acceptance criteria.

Update new-use-case interview to cover the new sections and use-case-tests
coverage requirements to reference flows and rules instead of AC.

Addresses #33.
Tests now group by use case (UC0NN class in a per-UC folder, methods
named after Main Flow / AF-N / BR-N) rather than splitting by view
tech or mirroring the main package. The use-case template loses the
named test class and the Vaadin-specific route table — those are
implementation details the harness owns, not spec.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant