User Stories
The User Stories pattern creates elements and a diagram that shows how to model a User Story including a Persona and external Acceptance Criteria. Details of the User Story can be added to the element's notes or alternatively a linked document can be created if more structured content needs to be added.

Figure 1. Shows a Person and a User Story with external Acceptance Criteria that have been connected to the User Story. 
Discussion
The purpose of the pattern is to allow an Agile team member or other stakeholder to create a User Story including associated Acceptance Criteria. The details of the User Story can be completed using the elements notes or alternatively they can be detailed in a linked document. The story attempts to capture a need articulated by a user and written in their language. They can be used for prioritization, estimation and planning.

User Stories are typically defined throughout an initiative and when iterative processes are being utilized the Stories are commonly defined at the beginning of a Sprint. 

The following is a list of some things you may want to do when working with this pattern.
·	Change the name of the diagram to suit the initiative.
Change the name of the User Story to suit the initiative.
Add detailed notes that describe aspects of the story in more detail.
Change the names and details of the Acceptance Criteria.
	Add an alternate image to represent the Persona.

The following is a list of some of the next steps available when applying the pattern.
Add a linked document to the User Story element if more detailed text is required.
·	Add detailed requirements to the User Story either as internal or external elements that help to provide more detail for the implementation teams.
Create Trace relationships between the User Story and other up-process and down-process elements in the model. 
Reference
The following help topics will assist you learn about how to work with this pattern.
User Stories
User Story
Linked Documents
External and Internal Requirements
Business Analysis Body of Knowledge (BABOK)
Traceability Tools
Documentation

The following are some of the tools that will be helpful when working with this pattern.
Image Manager
The Image Manager is a tool for managing images such as photos and screen shots and other pictures in a variety of formats. Often when observations are made an analyst will take one or more photos of a user in situ in their work environment. An analyst might also capture screen shots of the current applications the user is working with. All these digital assets can be imported into the Image Manager and then applied to elements in diagrams as an alternate image. Alternatively a picture contained in the Clipboard can be pasted directly into a diagram. For more details see the Image Manager help topic.
Linked Documents
Linked Documents provide a way of incorporating extensive and highly formatted documentation for an element. While an elements notes are a useful place to provide brief and visible information about an element a Linked Document can be used to create extensive documentation for an element including all the features you available in a typical word processing tool such as: Paragraph Formatting, Header and Footers, Table Images, Tables of contents and much more. For more details see the Linked Documents help topic.
Document Generator
The Document Generator is a powerful facility in Enterprise Architect that allows a Database Engineer or other stakeholder to create high quality corporate or technical documentation directly from the model, suitable for internal or external audiences. For more details see the Documentation help topic or the more general topic on Model Publishing.
Element Discussions
The Element Discussion facility is a fully featured collaboration tool allowing modelers and model viewers and reviewers to communicate with each other directly inside the repository. Modelers using the full client or occasional viewers using WebEA can both post and reply to discussions and communicate and engage in chat. For more details see the Element Discussions help topic.
Specification View
The Specification View can be used as a way of working with any element type in a spreadsheet or word process view. It is particularly useful when there are a large number of elements as is typically the case when describing a system of any appreciable size. For more details see the Specification View help topic.
Relationship Matrix
The Relationship Matrix provides a spreadsheet like view of two groups of elements and the relationships that exist between them. It can be a used as a powerful analysis mechanism to visually indicate how elements are related to each other and to discover which elements are missing relationships. For more details see the Relationship Matrix  help topic.
Traceability Window
The Traceability Window automatically displays the relationships that exist between Use Cases and other model elements including up-process and down-process elements. The traceability tree view can be conveniently expanded to see deeper relationships and elements displayed in the window can be located in all diagrams in which they appear. For more details see the Traceability Window  help topic.

© 2000 - 2018  Sparx Systems Pty Ltd.  All rights Reserved.