1. ADMS-BIS Bouwkundige Informatiesystemen ADMS 2006 UML part 1 Jan Dijkstra - 9 oktober 2006 ADMS-BIS

2. Subjects

3. ADMS-BIS UML Introduction

4. ADMS-BIS Information system design with UML Having knowledge of the visual modelling language UML in the field of ICT. Gain a clear understanding of applying this knowledge for specifying, constructing, visualizing and documenting software-intensive systems.

5. ADMS-BIS Study Matter Ian Sommerville Software Engineering, 6 th edition – Ch.6 Addison Wesley Dean Leffingwell & Don Widrig Managing Software Requirements, 2 nd edition Addison Wesley Grady Booch, James RumBaugh & Ivar Jacobson The Unified Modeling Lnaguage – Covers UML 2.0, 2 nd edition Addison Wesley Martin Fowler UML Distilled, 3 nd edition Addison Wesley Fowler & Scott UML beknopt, 2 nd edition Addison Wesley Sander Hoogendoorn Pragmatisch modelleren met UML 2.0 Addison Wesley

6. ADMS-BIS About UML UML offers a standard way to write a system’s blueprints, including conceptual things such as business processes and system functions as well as database schemas. UML is a modelling language, a notation used to express and document designs.

7. ADMS-BIS What is the UML? The Unified Modelling Language (UML) is the successor to the wave of object-oriented analysis and design (OOA&D) methods that appeared in the late ’80s and early ’90s. It unifies the methods of Booch, Rumbaugh (OMT), and Jacobson (3 amigo’s).

8. ADMS-BIS Data and Processes Traditional, the division between data and processes –were structured separately, –and functions made use of data For OO –an object contains data and processes encapsulation information hiding –avoiding domino effect adaptations –more simple and cheaper maintenance

9. ADMS-BIS Domain modelling Traditional, functional decomposition was the strategy –adaptations are difficult For OO –domain modelling independent of the required functions objects encapsulates functionality It is easier to make adaptations and extensions

10. ADMS-BIS UML is for modelling Building models of complex systems because one cannot comprehend such a system in its entirely. At this, a model –is a simplification of reality –is a set of blueprints of a system –is an abstraction of something for the purpose of understanding it before building it –may be expressed a different level of expression (no single model is sufficient)

11. ADMS-BIS UML is for visualizing An explicit model facilitates communication. UML symbols are based on well-defined semantics.

12. ADMS-BIS UML is for specifying and constructing Specifying means building models that are precise, unambiguous and complete. UML addresses the specification of all the important analysis, design, and implementation decisions made in developing and deploying a software system.

13. ADMS-BIS UML is for documenting UML addresses the documentation of a systems architecture and all of its details.

14. ADMS-BIS UML is a language UML is a visual language for software blueprints –with a vocabulary and rules for communication; –and a focus on conceptual and physical representations.

15. ADMS-BIS UML: graphical notations 1

16. ADMS-BIS UML: graphical notations 2

17. ADMS-BIS UML Models, Views and Diagrams A diagram is a view into a model –presented from the aspect of a particular stakeholder –and provides a partial representation of the system

18. ADMS-BIS UML Views Design view Interaction view Implementa- tion view Deployment view Use Case view vocabulary functionality behaviour performance scalability throughput system assembly configuration management system topology distribution delivery installation physicallogical

19. ADMS-BIS UML Diagrams Structure diagram –Class diagram –Object diagram –Component diagram –Composite structure diagram –Deployment diagram –Artifact diagram Behaviour diagram –Use Case diagram –Sequence diagram –Communication diagram –State diagram –Activity diagram

20. ADMS-BIS Use Case diagram

21. ADMS-BIS Class Diagram

22. ADMS-BIS Object diagram

23. ADMS-BIS Sequence diagram

24. ADMS-BIS Activity diagram

25. ADMS-BIS Component diagram

26. ADMS-BIS Deployment diagram

27. ADMS-BIS UML: what we will cover Use case diagrams –Documenting the system’s behaviour from the user’s viewpoint, requirements capture Activity diagrams –Describing the sequencing of activities with support for both conditional and parallel behaviour Class diagrams –Describing the type of objects in a system and the static relationships between them

28. ADMS-BIS UML steps 1.Examine the necessities of the information system  use cases & use case text with flow description by activity diagram  Use Case Diagram & Activity Diagram UML1 2.Object-oriented domain analysis  decomposition of the problem field in concepts, attributes and associations that may be of relevance to the information system  Class Diagram (including Object Diagram) UML2

29. ADMS-BIS Activity Diagram

30. ADMS-BIS Example

31. ADMS-BIS Activity Diagram: what is it? Describes activities and flows of data or decisions between activities Provides a very broad view of business processes Can be used to break out the activities that occur within a use case Good for showing parallel threads

32. ADMS-BIS Activity Diagram: what is it? Describes activities and flows of data or decisions between activities Can be used to break out the activities that occur within a use case

33. ADMS-BIS Activity Diagram: when to use it? When describing work flow across many use cases When analysing a use case, and assigning scenario’s When dealing with multi-threaded applications

34. ADMS-BIS UML Activity symbols

35. ADMS-BIS Action State In a conceptual diagram an activity is a task that needs to be done – either by a human or a computer In a specification-perspective diagram or an implementation-diagram, an activity is a method on a class

36. ADMS-BIS Sequential Branching A sequential branch is represented as a diamond –It may have one incoming transition and two or more outgoing transitions –Guards are associated with each transition

37. ADMS-BIS Branch & Merge

38. ADMS-BIS Forking and Joining Concurrent activities within an activity diagram are modelled with the use of synchronised bars Joins and Forks should balance

39. ADMS-BIS Forks, Joins & conditional Threads

40. ADMS-BIS Exercise 1 Activity Diagram Make an activity diagram of the following situation: At a course administration department a student makes a request for registering a course. Prior to an actual registration, the foreknowledge of the student is checked. Concurrent, there is a check whether the course is full or not. If the foreknowledge of the student is ok, there is a registration if possible. Otherwise, the possibilities for a special regulation will be explored. Is a special regulation possible, there is a registration too (if possible).

41. ADMS-BIS Solution Exercise 1

42. ADMS-BIS Swim lanes The activities of an activity diagram may be performed by different groups. Each zone or lane represents the responsibilities of a particular group.

43. ADMS-BIS Exercise 2 Activity Diagram Make an activity diagram including swimlanes of the following situation: A client places an order for a product at a company. The sales department will process the order and subsequently the stockroom assembles the ordered goods and dispatches the order. As a result of the order and after the message of the stockroom that the order is dispatched, a receipt and an invoice are sending parallel to the client. The sales department prepares the invoice. If, subsequently, the client has paid the invoice, the sales department completes the order.

44. ADMS-BIS Solution Exercise 2

45. ADMS-BIS Date2date example: scenario’s

46. ADMS-BIS Use CaseInloggen abonnee Actors Abonnee, bezoeker Description Pre-conditions Checken op geldigheid actor als abonnee ---- Basic flow 1.Valideer aantal ongeldige logins 2.Toon webpagina login 3.Actor voert login en password in 4.Actor bevestigt 5.Applicatie valideert login 6.Markeer actor als abonnee Extension / Exception flow 1a Login ongeldig 1a 1 Aantal ongeldige logins >2, stop 5a Login ongeldig 5a 1 Verhoog aantal ongeldig logins, herhaal 1 Post-conditions Actor is bekend als abonnee en is ingelogd Date2date : Inloggen abonnee – use case text

47. ADMS-BIS Date2date : Inloggen abonnee – activity diagram

48. ADMS-BIS Key point Activity diagrams are useful for –Business Process Redesign –Work Flow Modeling –Analysing Use Cases

49. ADMS-BIS NS Ticket service Make an activity diagram for the actor ‘Traveller’. Describe an use case. Take ticket Destination Single / Retour No Reduction / 40% reduction 2e class / 1e class

50. ADMS-BIS Use Case diagram ‘NS Ticket service’

51. ADMS-BIS Use CaseBuy OV Ticket ActorsTraveller PreconditionsTraveller has a valid pass Description1.Ticket device expects destination code 2.Traveller enters destination code 3.Extension point: NS ticket 4.Ticket device checks code and calculates the charge. Shows destination code & fare. Activates ticket machine for paying 5.Traveller pays (use case: Pay ticket) 6.Ticket device print and supplies ticket 7.Traveller takes ticket ExtensionDestination code = NS station. 3a. Ticket device expects ticket type 3b. Traveller enters Single/Return, Discount Y/N, Class ExceptionsTraveller interrupt the interaction or walk away Traveller enters an incorrect destination code Payment is not finished off successful ResultTraveller has ticket. (NS can look forward to the payment)

52. ADMS-BIS Make an activity diagram for the actor ‘Traveller’

53. ADMS-BIS Microsoft Visio

54. ADMS-BIS Microsoft Visio Install Microsoft Visio via http://w3.tue.nl/nl/diensten/dienst_ict/producten_e n_diensten/ dan: PC Software InstallatiePC Software Installatie Grafische ApplicatiesGrafische Applicaties MS Visio ProfessionalMS Visio Professional

55. ADMS-BIS

57. Task UML part 1

58. ADMS-BIS Task (opdracht) deelresultaat 2 Starting point: IS of your subject Make Use Case Diagram of the intended information system Describe the use cases with a use case text Make activity diagrams of the descriptions of the scenario’s of the use cases (from the use case text)