使用案例图Use Case Diagram【国外优秀ppt模板】.pptVIP

Slide 2 (of 48) Use Case Diagram Notations Actors Actors Use Case Diagram– Guidelines Caution Example – Include and Extend Quiz 1 Quiz 2 Granularity of Use Cases Granularity of Use Cases Discussion Exercise Exercise - Solution Use Case Specification Flow of Events / Pathways Flow of Events / Pathways Flow of Events / Pathways Flow of Events / Pathways Types Flow of Events / Pathways Types Flow of Events / Pathways See Example Word Document on Use Case Specification based on Remulak Productions Review Questions Review Question Review Question Review Question Review Question Review Question Review Question Review Question Use Case Diagram - In Class Exercise Further Reading There are TWO(2) mistakes in the diagram done on deliberate purpose: Use case should ideally begin with a verb – video availability enquiry should be named as ‘Enquire video availability’ Customer interacting with scanning device need not be shown as actors are not part of the system. Only interactions between the actor and the use cases is of importance. Use case description serves as a ‘bridge’ between stakeholders of a system and the development team. Use Case Diagram Use Case Specification Programmers look at use case specification to understand complete requirements - SRS Systems analyst produce use case diagram use case specification in consultation with end users Flow of Events Describes how and when use case starts and ends. Does NOT describe user interface details. Is generally a text-based file that is included under its use case in Rational Rose/Visual Paradigm Types of Flow of Events Basic Flow of Events@ Happy Path - is the most common pathway. It usually depicts a perfect situation, in which nothing goes wrong. Alternate Flow of Events @ Alternate Pathway - is a pathway that is still considered a good pathway; it’s just not the most heavily travelled one Exception Flow of Events @ Exception Pathways @ Unhappy Pathway – things don’t always go as planned. An exception is a