Please enable JavaScript.
Coggle requires JavaScript to display documents.
Identifying User Stories and Use Cases - Coggle Diagram
Identifying User Stories and Use Cases
User Stories
focus on the goals of user
approach to identify
favored by agile system development methodology
agile philosophy: work directly with users and avoid too much documentation
usually one short sentence stating what a user doees as part of his or her work
focus: simplicity, value added, user collaboration
standard template "As a <role played>, I want to <goal or desire> so that <reason or benefit>
acceptance criteria
features that must be present in the final system for the user to be satisfied
used by analyst to clarify expectations of users and verify user is looking at the user story at the appropriate level of analysis
In meetings, analysts encourage stakeholders to write out each user story on an index card or shared whiteboard app
Use Cases
focus on the goals of user
activity system performs in response to request by user
two techniques to identify
user goal technique
technique to identify use cases by determining specific goals or objectives to be completed by the system for the user
steps:
1) identify all potential users of new system
2) classify potential users in terms of their functional role (e.g, sales, shipping, marketing)
3) further classify users by organizational level (e.g, operational, management, executive)
4) interview users to determine specific goals
5) create list of preliminary use cases organized by type of users
6) look for duplicates, resolve for inconsistencies
7) identify where different types of users need the same use cases
8) review completed list with users and interested stakeholders
overarching objectives
identify system gap to improve user's performance and productivity
subsidiary goals
streamlining tasks users currently performs or enable users to perform new tasks that are not possible or practical with the current system
event decomposition technique
technique to identify uses cases by determining the business events to which the system must respond
appropriate level of detail to identify use cases
Elementary Business Processes (EBP)
appropriate level of detail to identify use cases
fundamental task in
a
business process.
usually performed by one person in response to a business event. It leaves system and data In stable and consistent state