1. Conquering Complex and Changing Systems Object-Oriented Software Engineering Chapter 2, Modeling with UML

2. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 2 Overview  What is modeling?  What is UML?  Use case diagrams  Class diagrams  Sequence diagrams  Activity diagrams  Summary

3. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 3 Systems, Models, and Views  A model is an abstraction describing system or a subset of a system  A view depicts selected aspects of a model  A notation is a set of graphical or textual rules for representing views

4. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 4 Systems, Models, and Views Airplane Flightsimulator Scale Model Blueprints Electrical Wiring

5. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 5 Why model software? Software is already an abstraction: why model software?  Software is getting larger  NT 5.0 ~ 40 million lines of code  A single programmer cannot manage this amount of code.  Code is often not directly understood by those who did not develop it  We need simpler representations for complex systems  Modeling is a means for dealing with complexity

6. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 6 Concepts and Phenomena  Phenomenon: An object in a domain as you perceive it, e.g.:  The lecture you are attending  My black watch  Concept: The common properties of phenomena, e.g.:  Lectures on software engineering  Black watches  A concept is a 3-tuple:  Its Name distinguishes it from other concepts.  Its Members are the phenomena represented by the concept.  Its Purpose is the set of properties that characterize its members.

7. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 7  Abstract: Classification of phenomena into concepts  Model: Develop abstractions to answer specific questions about a set of phenomena, ignoring irrelevant details. MembersName Clock Purpose A device that measures time. Concepts and Phenomena

8. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 8 Class  Class: An abstraction in the context of OO languages  Like an abstract data type, a class encapsulates both state (variables) & behavior (methods)  Unlike abstract data types, classes can be defined in terms of other classes using inheritance Watch time date CalculatorWatch SetDate(d) EnterCalcMode() InputNumber(n) calculatorState

9. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 9 Object-Oriented Modeling UML Package

10. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 10 Application and Solution Domain  Application Domain (Requirements Analysis):  The environment in which the system is operating  Solution Domain (System Design, Object Design):  The available technologies to build the system

11. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 11 What is UML?  UML (Unified Modeling Language)  A language for modeling object-oriented (OO) software.  It is the convergence of notations from 3 OO methods:  OMT (James Rumbaugh)  OOSE (Ivar Jacobson)  Booch (Grady Booch)  Reference: “The Unified Modeling Language User Guide”, Addison Wesley, 1999.  Supported by several CASE tools  Rational ROSE  Together/J ...

12. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 12 UML and This Course  You can model 80% of most problems with 20% of UML  We look at that 20%

13. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 13 UML First Pass  Use case diagrams  Describe the function of the system as seen by the user.  Class diagrams  Describe the system’s static structure: Objects, Attributes, & Associations.  Sequence diagrams  Describe the dynamic behavior between actors & the system & between the system’s objects.  Statechart diagrams  Describe the dynamic behavior of an individual object as a finite state machine.  Activity diagrams  Model the dynamic behavior of a system as a flowchart.

14. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 14 UML First Pass: Use Case Diagrams WatchUserWatchRepairPerson ReadTime SetTime ChangeBattery Actor Use case Package SimpleWatch Use case diagrams represent the functionality of the system from user’s point of view

15. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 15 UML First Pass: Class Diagrams Battery load() 1 2 Time now() PushButton state push() release() 1 1 1 1 1 2 blinkIdx blinkSeconds() blinkMinutes() blinkHours() stopBlinking() referesh() LCDDisplay SimpleWatch Class Association Multiplicity Attributes Operations Class diagrams represent the structure of the system

16. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 16 UML First Pass: Sequence Diagram Object Message Activation Sequence diagrams represent the behavior as interactions blinkHours() blinkMinutes() incrementMinutes() refresh() commitNewTime() stopBlinking() pressButton1() pressButton2() pressButtons1And2() pressButton1() :WatchUser :Time:LCDDisplay:SimpleWatch

17. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 17 button1&2Pressed button1Pressed button2Pressed button1Pressed button1&2Pressed Increment Minutes Increment Hours Blink Hours Blink Seconds Blink Minutes Increment Seconds Stop Blinking UML First Pass: Statechart Diagrams State Initial state Final state Transition Event

18. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 18 Other UML Notations Other UML notations may be introduced in subsequent lectures.  Implementation diagrams  Component diagrams  Deployment diagrams  For System Design  Object Constraint Language (OCL)  For Object Design

19. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 19 UML Core Conventions  Rectangles are classes or instances  Ovals are functions or use cases  Instance names are underlined  myWatch:SimpleWatch  Joe:Firefighter  Class names are not underlined  SimpleWatch  Firefighter

20. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 20 UML Second Pass: Use Case Diagrams Used during requirements elicitation to represent external behavior  Actors represent roles, that is, a type of user of the system  Use cases represent a sequence of interaction for a type of functionality  The use case model is the set of all use cases.  It is a complete description of the functionality of the system & its environment Passenger PurchaseTicket

21. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 21 Actors  An actor models an external entity that communicates with the system:  User  External system  Physical environment  An actor has a unique name & an optional description.  Examples:  Passenger: A person in the train  GPS satellite: Provides the system with GPS coordinates Passenger

22. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 22 Use Case A use case represents a class of functionality provided by the system as an event flow. A use case consists of:  Unique name  Participating actors  Entry conditions  Flow of events  Exit conditions  Special requirements PurchaseTicket

23. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 23 Use Case Example Name: Purchase ticket Participating actor: Passenger Entry condition:  Passenger standing in front of ticket distributor.  Passenger has sufficient money to purchase ticket. Exit condition:  Passenger has ticket. Event flow: 1. Passenger selects the number of zones to be traveled. 2. Distributor displays the amount due. 3. Passenger inserts money, of at least the amount due. 4. Distributor returns change. 5. Distributor issues ticket. Anything missing ? Exceptional cases!

24. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 24 The > Relationship  > relationships represent exceptional or seldom invoked cases.  Exceptional event flows are factored out of the main event flow for clarity.  Use cases representing exceptional flows can extend more than 1 use case.  The direction of an > relationship is to the extended use case Passenger PurchaseTicketTimeOut > NoChange > OutOfOrder > Cancel >

25. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 25 Passenger PurchaseSingleTicketPurchaseMultiCardNoChange > Cancel > CollectMoney > The > Relationship  An > relationship represents behavior that is factored out of the use case.  An > represents behavior that is factored out for reuse.  The direction of a > relationship is to the using use case.

26. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 26 Class Diagrams  Class diagrams represent the structure of the system.  Class diagrams are used  during requirements analysis to model problem domain concepts  during system design to model subsystems & interfaces  during object design to model classes. Enumeration getZones() Price getPrice(Zone) TariffSchedule * * Trip zone:Zone price:Price

27. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 27 Classes  A class represent a concept.  A class encapsulates state (attributes) and behavior (operations).  Each attribute has a type.  Each operation has a signature.  The class name is the only mandatory information. zone2price getZones() getPrice() TariffSchedule Table zone2price Enumeration getZones() Price getPrice(Zone) TariffSchedule Name Attributes Operations Signature TariffSchedule

28. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 28 Instances  An instance represents a phenomenon.  An instance name is underlined & can contain the class name.  The attributes are represented with their values. zone2price = { {‘1’,.20}, {‘2’,.40}, {‘3’,.60}} tariff_1974:TariffSchedule

29. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 29 Actor vs. Instances  What is the difference between an actor, a class & an instance?  Actor:  An entity outside the system to be modeled, interacting with the system (“Pilot”)  Class:  An abstraction modeling an entity in the problem domain, inside the system to be modeled (“Cockpit”)  Object:  A specific instance of a class (“Joe, the inspector”).

30. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 30 Associations  Associations denote relationships between classes.  The multiplicity of an association end denotes how many objects the source object can legitimately reference. Enumeration getZones() Price getPrice(Zone) TarifSchedule * price zone TripLeg *

31. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 31 1-to-1 and 1-to-Many Associations 1-to-1 association 1-to-many association * draw() Polygon x:Integer y:Integer Point 1 Has-capital name:String Country name:String City 11

32. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 32 Aggregation  An aggregation is a special case of association denoting a “consists of” hierarchy.  The aggregate is the class containing the components classes. 1 Exhaust SystemMufflerTailpipe 0..2

33. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 33 Composition  A solid diamond denote composition, a strong form of aggregation where components cannot exist without the aggregate. 3 TicketMachine ZoneButton

34. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 34 Generalization  Generalization is an inheritance relationship.  Child classes inherit the parent class’s attributes & operations.  Generalization simplifies the model by eliminating redundancy. Button ZoneButtonCancelButton

35. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 35 From Problem Statement to Code Problem Statement A stock exchange lists many companies. Each company is identified by a ticker symbol Class Diagram Java Code public class StockExchange { public Vector m_Company = new Vector(); }; public class Company { public int m_tickerSymbol; public Vector m_StockExchange = new Vector(); }; * StockExchange tickerSymbol Company * lists

36. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 36 UML Sequence Diagrams  Used during requirements analysis  To refine use case descriptions  to find additional objects (“participating objects”)  Used during system design  to refine subsystem interfaces  Classes are represented by columns  Messages are represented by  Activations are represented by  Lifelines are represented by selectZone() pickupChange() pickUpTicket() insertCoins() Passenger TicketMachine

37. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 37 UML Sequence Diagrams: Nested Messages  An arrow’s source indicates is activation that sent the message  An activation is as long as all nested activations selectZone() Passenger ZoneButton TariffScheduleDisplay lookupPrice(selection) displayPrice(price) price Dataflow …to be continued...

38. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 38 Sequence Diagram Observations  UML sequence diagrams represent behavior in terms of interactions.  Class diagrams represent structure.  Used to find participating objects.  Time consuming to build but worth the investment.

39. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 39 Activity Diagrams  An activity diagram shows flow control within a system  An activity diagram is a special case of a state chart diagram in which states are activities (“functions”)  Two types of states:  Action state:  Cannot be decomposed any further - atomic  Happens “instantaneously” with respect to the level of abstraction used in the model  Activity state:  Can be decomposed further  The activity is modeled by another activity diagram

40. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 40 Activity Diagram: Modeling Decisions

41. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 41 Activity Diagrams: Modeling Concurrency  Synchronization of multiple activities  Splitting the flow of control into multiple threads Synchronization Splitting Archive Incident Open Incident Document Incident Allocate Resources Coordinate Resources Concurrent Activities

42. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 42 Activity Diagrams: Swimlanes  Actions may be grouped into swimlanes to denote the object or subsystem that implements them. Archive Incident Dispatcher FieldOfficer Open Incident Document Incident Allocate Resources Coordinate Resources

43. Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 43 Summary  UML provides a wide variety of notations for representing many aspects of software development  Powerful, but complex language  Can be misused to generate unreadable models  Can be misunderstood when using too many exotic features  We concentrate only on a few notations:  Functional model: use case diagram  Object model: class diagram  Dynamic model: sequence diagrams, statechart & activity diagrams