UML. Unified Modeling Language. Hans-Petter Halvorsen, M.Sc. O. Widder. (2013). geek&poke. Available:

Transcription

1 O. Widder. (2013). geek&poke. Available: UML Unified Modeling Language Hans-Petter Halvorsen, M.Sc.

2 Unified Modeling Language (UML) Examples Class Diagram Use Case Diagram 2

3 Deployment Planning Maintenance Testing Implementation The Software Development Lifecycle (SDLC) Requirements Analysis Design

4 Documents in Software Development Project Start Time 1. Planning (stakeholders, the software team; architects, UX designers, developers) 2. Testing (QA people) High-Level Requirements and Design Documents Detailed Requirements and Design Documents Test Plans Test Documentation WHAT HOW ER Diagram UML Diagrams CAD Drawings How to Test/ What to Test Proof that you have tested and that the software works as expected 3. End-user Documentation (The people that shall actually use the software) System Documentation Installation Guides User Manuals Technical Stuff (Super User/ IT dep.) How to install it How to use it (End User) Project Finish 4. Handover (Business people) Final Report

5 Unified Modeling Language (UML) A modeling language used in software engineering Very popular within OOA, OOD, OOP Developed in the 1990s UML was adapted as an ISO standard in 2000 UML 2.2 has 14 different types of diagrams OOA = Object Oriented Analysis, OOD = Object Oriented Design, OOP = Object Oriented Programming

6 UML Diagrams 6

7 UML Diagrams Klassediagram (Class Diagram) Komponentdiagram (Component Diagram) Produksjonssettingsdiagram (Deployment Diagram) Objektdiagram (Object Diagram) Pakkediagram (Package Diagram) Aktivitetsdiagram (Activity Diagram) Sekvensdiagram (Sequence Diagram) Samhandlingsdiagram (Communication Diagram), forenklet versjon av UML 1.x Collaboration Diagram Bruksmønserdiagram (Use Case Diagram) Tilstandsdiagram (State Machine Diagram) Sammensatt strukturdiagram (Composite Structure Diagram) (UML 2.0) Interaksjonsoversiktsdiagram (Interaction Overview Diagram) (UML 2.0) Tidsforløpsdiagram (Timing Diagram) (UML 2.0) 7

8 UML Diagrams 2 categories: 1. Structure Diagrams 2. Behavior Diagrams Interaction Diagrams (A Subset of Behavior Diagrams) 8

9 Use Case Use Case Example for a Restaurant: A use case is a list of steps, typically defining interactions between a role (known in UML as an "actor") and a system, to achieve a goal. The actor can be a human or an external system. [ 9

10 Use Case Example A use-case diagram for a course registration system 10

11 Use Case Example 11

12 Sequence Diagram 12

13 Class Diagram 13

14 Class Inheritance When a class inherits from another class, it automatically gets all its attributes and methods. If class A inherits from class B, we call class A the superclass and class B the subclass. Inheritance relationship is an is-a relationship between the subclass and the superclass. Although the subclass can override any method it inherits from the superclass, changing its behavior, the intent is to mostly add additional methods. 14

15 Why use UML? Design Forward Design: doing UML before coding. Makes it easier to create the code in a strucured manner Backward Design: doing UML after coding as documentation When doing changes in the Design, make sure to update the Code according to the new Design Code Some Tools can Autogenerate Code from UML diagrams When doing changes in the Code, make sure to update the UML Diagrams 15

16 Use Case and Scrum (Agile) The Team works cloesly together with the Product Owner Less need for detailed descriptions and requirements Agile/Scrum uses User Stories instead (which could be considered as a light version of Use Case) The User Stories are the base for the Product Backlog and the Sprint Backlog 16

17 UML Software MS Visio Enterprise Architect StarUML Rational Rose Visual Studio Enterprise etc. (hundreds different alternatives) 17

18 UML in Visual Studio Enterprise Improving-architecture-through-modeling 18

19 UML Exercise - Solutions Aktør Use Case 19

20 UML Exercise - Solutions + Kjøp Ringetid Et use case (bruksmønsterdiagram) er en beskrivelse av hvordan systemet oppnår et mål av verdi for en aktør. Bruksmønster diagrammer (Use Case diagrams) brukes til å beskrive interaksjonen mellom brukere og systemer. Bruksmønstre beskriver interaksjonen mellom et system og eksterne aktører.

21 Summary It is important to create Design and Specifications (including UML) before you start Coding But UML can also be used to document your code afterwards UML diagrams is a general method/standard to do just that This makes it easier to create structured code A good way to document your code properly. Code refactoring: Use UML as part of the continuous code improvements process 21

22 References Wikipedia. (2013). Unified Modeling Language. Available: I. Sommerville, Software Engineering: Pearson, Wikipedia. (2013). Scrum Development. Available: S. Adams. Dilbert. Available: O. Widder. (2013). geek&poke. Available: B. Lund. (2013). Lunch. Available:

23 Hans-Petter Halvorsen, M.Sc. University College of Southeast Norway Blog: