Generated User Story Components
When you model a Process and provide text and images where prompted, these details are automatically assembled to generate a high-quality user story.
The following are the components of a well-defined user story and the syntax that is well-formed.
User Story Title
In agile development, user stories use a template that includes an actor, an action, and an objective. For example:
As a bank customer, I want to set up automatic account transfers online, so that I can self-manage my funds.
User-story titles are automatically generated from task details.
Given-When-Then and Acceptance Criteria
In behavior-driven development (BDD), a user story includes one or more scenarios that follow the Given-When-Then form.
In a user story preview, the Acceptance Criteria section and (if User-System Process mode is enabled) the three Given, When, and Then panels are assembled from a task's details and its adjacent system task details.
With the Given-When-Then format, when a task is performed (the "when"), a system response can act as the pre-existing state before the user task (that is, the "given"), or a resulting system state after it (the "then").
By providing consistently phrased and well-formed system responses while modeling the Process, the resulting acceptance criteria is comprehensive and clear.
User stories with multiple scenarios are generated from system decision points. The details of the different scenarios are generated from the condition names of system decision point conditions.
