Rule #2: Don’t confuse use cases with user stories If there were too many steps, then a new use case would have been the appropriate action to take. If new actors and goals are introduced, it is ideal to create different use cases even though the steps may seem similar. In addition, there are relatively few steps involved in this alternative course to warrant creating a new use case. The reason being that the alternative path still concerns the same actor, system, and use case goal (complete customer profile). We chose to go with option 2 and created the alternative path. Create an alternative path in this use case.Create a new use case to indicate the email route.Customer emails System Admin for credentials resetĪs shown in this use case example, there is more than one way to provide personal information to complete a customer profile. We could have done one of two things to illustrate this: System Admin User enters personal information emailed by customerģa1. System Admin User accesses “customer information” functionalityġb2. System Admin enters customer informationġb1. User emails personal information to System Adminġb. System presents a confirmation screen informing the user that the information has been savedġa1. User enters personal details into form and clicks saveĥ.
System verifies customer and displays personal details entry formĤ. User logs in using credentials provided by System Adminģ. Input personal information into ABC Corp online portalĬustomer has login credentials provided by ABC Corp System AdminĢ. In part 1 of this blog series, we had the following use case example: Is the path an alternative to the main path?.Is the path achieving the same goal with the same actor?.Rule #1: Follow a straight path to achieve a use case goalĪ use case should be as concise as possible when another possible route becomes evident, consider the following: In this entry, we will cover the five most important rules for creating use cases. In a previous blog entry we introduced you to use case types and use case presentation methods (textual use cases or use case diagrams).
0 kommentar(er)
