BUS 362 Chapter Notes - Chapter 4: Use Case
Document Summary
Use cases are used to explain and document the interaction that is required between the user a(cid:374)d the syste(cid:373) to a(cid:272)(cid:272)o(cid:373)plish the user"s task. Use cases are created to help the development tea(cid:373) fully u(cid:374)dersta(cid:374)d the steps that i(cid:374)(cid:448)ol(cid:448)ed i(cid:374) a(cid:272)(cid:272)o(cid:373)plishi(cid:374)g the user"s goals. It helps us understand the functional requirements of the new system. We need to know and understand what the user needs to accomplish with the system. Use cases will help analysts develop a more detailed understanding of the new systems functional requirements. Use cases are very in understanding exceptions, special cases, and error handling requirements in the new system. A use case depicts a set of activities performed to produce some output result. Each use case describes how an event triggers actions performed by the system and the user. The name should be as simple, yet descriptive as possible. A trigger can be external, or temporal which refers to it being time-based.