User Journeys & Acceptance Criteria in Flowriter
Last updated
Last updated
Flowriter automatically writes documentation based on the content and logic in a Story's flowchart. It produces these documents:
User Journeys, and
Acceptance Criteria.
User Journeys outline the steps and decisions users make to achieve their goals, and inform the Acceptance Criteria.
Flowriter analyzes and assesses all possible paths that a user or system may take when interacting with the feature, based on the flowchart structure to produce the User Journeys:
User Journey mapping is important. It helps the feature owner understand if all possible tasks that a user or system need to complete are considered in the documentation. They are also useful for preparing Test Plans to ensure that the final feature implementation is correct and has full test coverage.
A Story's Acceptance Criteria is automatically generated, and consists of two (2) parts:
Role, Goal, and Benefit statement
Gherkin -style Scenarios within an overall Feature statement
This summarizes the overall feature described in the flowchart and identified User Journeys, and is presented in this format:
As a [user/system/...] ... I want to ... So that ...
These defines how the feature should behave based on User Journeys. These criteria are generated in Gherkin, a structured format that can be read by both humans and scripts.
