IFB103 Lecture Notes - Lecture 10: Activity Diagram, Class Diagram
Document Summary
Uml: activity and sequence diagrams - week 10. Initial node: the beginning of a set of actions, final node, stops all flows in activities, decision node, represents a test condition. Making an appointment: when making an appointment, the employee receives the call, checks the availability of the selected date, and registers the appointment. The flow will go one way or the other but not both. Having one single final node is a matter of style. Join: brings back together the sequence of execution (synchronisation) As a recommendation, every fork should have a join. Swimlanes: show who is responsible for a collection of activities. We use swimlanes where there are at least to actors and we need to separate their activities. Sequence diagrams are related but very different from activity diagrams: a(cid:272)ti(cid:448)it(cid:455) diag(cid:396)a(cid:373)s des(cid:272)(cid:396)i(cid:271)e (cid:271)eha(cid:448)iou(cid:396) f(cid:396)o(cid:373) the use(cid:396)s(cid:859) poi(cid:374)t of (cid:448)ie(cid:449) how they interact with the system.