ITM 305 Chapter Notes - Chapter 3: Functional Decomposition, Use Case Diagram, Business Process
Document Summary
Chapter 3: identifying user stories and use cases. **identifying use cases is the key to defining functional requirements** One-sentence description of a work-related task done by a user to achieve some goal/result. Identify features that must be present at completion of task. Template: as a i want to so that . Activity that the system performs, usually in response to a request by a user. Analysts decompose the system into a set of use cases (functional decomposition) Most common in industry; simple and effective. Identify all of potential categories of users of system. Interview and ask to describe the tasks the computer can help them with. Identify the events that occur to which the system does when the event occurs. Event: something that occurs at a specific time and place, can be described, should be remembered by the system. An event that occurs outside the system (initiated by an external agent/actor)