What’s A Use Case?
A use case is a set of five requirements for a task or set of tasks: • A description of interactions between the user (normally referred to as the actor) • The system the user is interacting with • The scope of the interaction • Dependencies associated with the interaction • The goal The use case covers branches, error messages and edge conditions; the main reason for use cases is they are used as a communication tool with developers so they know exactly what’s going on with the system, and how the system should react. The use case will also list dependencies like “user must be signed in.” When you describe a use case, use active tone i.e. Register as a user, Pay for merchandise, Read mail are typical examples of how I would describe a task the user would take, and I may describe every interaction that user would make in completing that task. Paying for merchandise may include error messages like: • Invalid credit card • Address doesn’t match credit card • Name doesn’t match credit car
Related Questions
- Can Wexxar case/tray packaging machines be retrofitted with new product changes?
- Can Wexxar case/tray packaging machines be retrofitted with new product changes?
- What is a "lack of informed consent" medical malpractice case?
- What is a "lack of informed consent" medical malpractice case?
- What are the chances of settling my case "out of court"?
- What’s A Use Case?
