CPS 311 Chapter Notes - Chapter 3: Build Automation, Use Case Diagram
11 Dec 2016
School
Department
Course
Professor
Document Summary
Identify: classes, objects, semantics (methods, relationships (sequence, diagrams, implement classes, objects. Main flow variant, error sequences system interacting with outside actors short, simple o o useful activity not just one or two lines. Identifying use cases verb phrase name o ex) place order, cancel order, select ticket, assemble part, produce forecast to find use cases identify system boundaries, actors. Actor person, thing, other system interacting with system role o o o o external to system gets value from system started by primary actor actor"s point of view. Identify use cases: what actors do primary flows seconard (alt) flows. Who/what o uses the system provides/gets info to/from system installs/starts/stops system o: maintains system o o triggers storage, retrieval notified re state changes external events changing system state other systems interacting report generation. Use case diagram shows all relevant user cases actors outside box association icon connects actor-uc. Not flow of events ^ some use cases require includes/extends
