![a b c
[i>0] op1()
[i<=0] op2()
*op3()
Figure 30, Examples of conditions and
iterators in sequence diagrams.](https://image.slidesharecdn.com/modellingwithuml-191121021932/85/Modelling-with-uml-31-320.jpg)
![[fire & highPriority]
[not fire & highPriority]
[lowPriority]
Notify
Fire Chief
Open
Incident
Notify
Police Chief
Allocate
Resources
Figure 37, Example of decision in
the OpenIncident process.](https://image.slidesharecdn.com/modellingwithuml-191121021932/85/Modelling-with-uml-38-320.jpg)
Modelling with uml
- 1. Modelling with Unified Modelling Language (UML) By, D. B. Naga Muruga, B.E Mechanical Engineering, Sriram Engineering College
- 2. WatchUser WatchRepairPerson ReadTime SetTime ChangeBattery SimpleWatch Figure 1, A UML use case diagram describing the functionality of a simple watch.
- 3. Figure 2, A UML class diagram describing the elements of a simple watch. 1 2 1 1 1 1 1 2 SimpleWatch Display Battery TimePushButton
- 4. Figure 3, A UML sequence diagram for the SimpleWatch. :SimpleWatch :Time:Display pressButton1() blinkHours() blinkMinutes() pressButton2() incrementMinutes() refresh() pressButtons1And2() commitNewTime() stopBlinking() pressButton1() :WatchUser
- 5. button1&2Pressed button1Pressed button2Pressed button2Pressed button2Pressed button1Pressed button1&2Pressed Increment Minutes Increment Hours Blink Hours Blink Seconds Blink Minutes Increment Seconds Stop Blinking Figure 4, A UML statechart diagram for SetTime use case of the SimpleWatch.
- 6. Open Incident Allocate Resources Coordinate Resources Document Incident Archive Incident Figure 5, An example of a UML activity diagram.
- 7. Airplane All blueprints Scale model Electrical Fuel Flight simulator Figure 6, A Model is an abstraction describing a subset of a System. A View depicts selected aspects of a Model. Views and Models of a single System may overlap each other.
- 8. Book Chapter N composed-of Booch Book Chapter composed-of UML 1 * Figure 7, Example of describing a model with two different notations.
- 9. Watch time date CalculatorWatch SetDate(d) EnterCalcMode() InputNumber(n) calculatorState Figure 8, A UML class diagram depicting two classes: Watch and CalculatorWatch. CalculatorWatch is a refinement of Watch, providing calculator functionality normally not found in normal Watches.
- 10. OrganicCompound Benzene Figure 9, An example of abstract class.
- 11. Watch CalculatorWatch simpleWatch1291:Watch calculatorWatch1515 :CalculatorWatch «instanceOf» «instanceOf» Figure 10, A UML class diagram depicting instances of two classes.
- 12. pressButton2() getTime() getTimeDelta() :WatchUser GMTTime GMTTime :SimpleWatch :TimeZone:Time Figure 11, Examples of message sends.
- 13. Application Domain Solution Domain Application Domain Model System Model Aircraft TrafficController FlightPlan Airport MapDisplay FlightPlanDatabase SummaryDisplay TrafficControl TrafficControl Figure 12, The application domain model represents entities of the environment which are relevant to an air traffic control system (e.g., aircraft, traffic controllers).
- 14. Report Emergency FieldOfficer DispatcherOpenIncident AllocateResources FRIEND Figure 13, An example of a UML use case diagram: Incident initiation in an accident management system.
- 15. OpenIncident AllocateResources HelpDispatcher «include» «include» Figure 14, An example of an «include» relationship.
- 16. Figure 15, An example of an «extend» relationship. OpenIncident AllocateResources ConnectionDown «extend» «extend»
- 17. Authenticate Authenticate Authenticate WithPassword WithCard Figure 16, An example of a generalization relationship.
- 18. EmergencyReport Incident FieldOfficer name:String badgeNumber:Integer Dispatcher name:String badgeNumber:Integer author incidentsGenerated reportsGenerated initiator reports 1 * 1 * 1..* 1 Figure 17, An example of a UML class diagram: classes that participate in the ReportEmergency use case.
- 19. report_1291 incident_1515bob:FieldOfficer name = “Bob D.” badgeNumber = 132 john:Dispatcher name = “John D.” badgeNumber = 12 alice:FieldOfficer name = “Alice W.” badgeNumber = 23 Figure 18, An example of a UML object diagram: objects that participate in the warehouseOnFire scenario.
- 20. Figure 19, Example of a one- directional association. Polygon Point **
- 21. IncidentFieldOfficer name:String badgeNumber:Integer Allocates role:String notificationTime:Time resources incident 1 1..* Figure 20, An example of an association class.
- 22. Incident FieldOfficer name:String badgeNumber:Integer Allocation role:String notificationTime:Time resources incident 1 1..* 1 1 Figure 21, Alternative model for Allocation.
- 23. * * PoliceStation * * 1 1 1 1 State Directory County PoliceOfficer File Township Figure 22, Examples of aggregations.
- 24. Figure 23, Examples of multiplicity. FieldOfficer IncidentReport ** FireUnit FireTruck *1 PoliceOfficer 11 owner property author report BadgeNumber
- 25. Figure 24, Example of a hierarhical file system. Directory FileSystemElement File 1 *
- 26. Figure 25, Example of a nonhierarchical file system. Directory FileSystemElement File * *
- 27. Figure 26, Example of how a qualified association uses reduces multiplicity. Directory Filefilename Directory File filename 1 Without qualification With qualification * 0..11
- 28. EmergencyReport Incident FieldOfficer Dispatcher author initiator reportsGenerated incidents 1 * 1 * 1..* 1 PoliceOfficer name:String badgeNumber:Integer Figure 27, An example of a generalization.
- 29. Incident assignResource(r) close() Figure 28, Examples of operations provided by the Incident class.
- 30. :SimpleWatch :Time:Display pressButton1() blinkHours() blinkMinutes() pressButton2() incrementMinutes() refresh() pressButtons1And2() commitNewTime() stopBlinking() pressButton1() :WatchUser Figure 29, Example of a sequence diagram: setting the time on 2Bwatch.
- 31. a b c [i>0] op1() [i<=0] op2() *op3() Figure 30, Examples of conditions and iterators in sequence diagrams.
- 32. Figure 31, Example of a collaboration diagram: Setting the time on 2Bwatch. :2BwatchInput :2BwatchTime :2BwatchDisplay 1:p ressButtons1And2() 1.1: blinkHours() 3.1:i ncrementMinutes() 3.2:r efresh() 4.1:c ommitNewTime() :2BwatchOwner 2:pressButton1() 3:pressButton2() 4:pressButtons1And2() 2.1:blinkMinutes() 4.2:stopBlinking()
- 33. Active Inactive Closed Archived incidentHandled incidentDocumented incidentArchived Figure 32, A UML statechart diagram for the Incident class.
- 34. MeasureTime SetTime pressButtonsLAndR pressButtonsLAndR/beep after 2 min. DeadBattery after 20 years after 20 years Figure 33, Statechart diagram for 2Bwatch set time function.
- 35. Figure 34, Internal transitions associated with the SetTime state. SetTime entry/blink hours exit/stop blinking pressButton1/blink next number pressButton2/increment current number MeasureTime do/count ticks MeasureTime pressBothButtons pressBothButtons/beep after 2 min. after 20 years after 20 years
- 36. SetTime BlinkHours BlinkMinutes BlinkSeconds BlinkYear BlinkMonth BlinkDay b2/incr hour b2/incr min. b2/incr sec. b2/incr year b2/incr mo. b2/incr day b1 b1 b1 b1 b1b1 Figure 35, Refined statechart associated with the SetTime state.
- 37. Document Incident Archive Incident Handle Incident Figure 36, A UML activity diagram for Incident.
- 38. [fire & highPriority] [not fire & highPriority] [lowPriority] Notify Fire Chief Open Incident Notify Police Chief Allocate Resources Figure 37, Example of decision in the OpenIncident process.
- 39. Archive Incident Open Incident Document Incident Allocate Resources Coordinate Resources Figure 38, An example of complex transitions in a UML activity diagram.
- 40. Archive Incident Dispatcher FieldOfficer Open Incident Document Incident Allocate Resources Coordinate Resources Figure 39, An example of swimlanes in a UML activity diagram.
- 41. Report Emergency FieldOfficer DispatcherOpenIncident AllocateResources ArchiveIncident SearchArchive ManageUsers ManageTerminals Librarian SysAdmin SysAdministrationIncidentArchive IncidentManagement Figure 40, Example of packages: use cases of FRIEND organized by actors.
- 42. FieldOfficer Dispatcher Librarian SysAdmin IncidentArchive SysAdministration IncidentManagement Figure 41, Example of packages.
- 43. DispatcherStation EmergencyReport Incident FieldOfficer Dispatcher FieldStation Figure 42, Example of packages.
- 44. EmergencyReport DispatcherStation Incident FieldOfficer Dispatcher FieldStation The EmergencyReport class is defined in FieldStation and used in both stations. Figure 43, An example of a note. Notes can be attached to a specific element in a diagram.
- 45. «entity» «entity» «boundary» «boundary» «control» Year Month ChangeDateControl LCDDisplayBoundary ButtonBoundary «entity» Day Figure 44, Examples of stereotypes.
- 46. EmergencyReport Incident reports 1..* {ordered by time of receipt} Figure 45, An example of constraint. 1