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

Slides:



Advertisements
Similar presentations
UML Use Case Diagram / Use Case Text / Activity Diagram
Advertisements

©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 12Slide 1 Software Design l Objectives To explain how a software design may be represented.
7M701 1 Information Systems Modelling and Design with.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 9 Slide 1 Appendix 3 Object-Oriented Analysis and Design.
A Brief Introduction. Acknowledgements  The material in this tutorial is based in part on: Concurrency: State Models & Java Programming, by Jeff Magee.
CS3773 Software Engineering Lecture 03 UML Use Cases.
7M701 1 Activity Diagram. 7M701 2 Example 7M701 3 Activity Diagram: what is it? Describes activities and flows of data or decisions between activities.
UML: An Introduction.
Object-Oriented Analysis and Design
Bouwkundige Informatiesystemen ADMS 2006 UML part 1 Jan Dijkstra - 25 september 2006 ADMS-BIS.
Introduction To System Analysis and Design
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
UML Overview Unified Modeling Language Basic Concepts.
Unified Modeling (Part I) Overview of UML & Modeling
Bouwkundige Informatiesystemen ADMS 2004 UML part 1 Jan Dijkstra - 2 augustus 2004.
Class Diagram & Object Diagram
Use Case Modelling.
7M822 UML Activity Diagrams 6 October 2008.
7M822 UML Introduction 7 September 2010.
© Copyright Eliyahu Brutman Programming Techniques Course.
Itntroduction to UML, page 1 Introduction to UML.
UML Notations Activity diagrams State diagrams Class diagrams Use-case diagrams.
7M822 UML Interaction Diagrams 25 November 2010.
SE-565 Software System Requirements More UML Diagrams.
7M822 UML Sequence Diagrams 5 October 2009.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Introduction To System Analysis and design
UML Unified Markup Language Ziya Karakaya Atılım University, Computer Engineering
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
Introduction to the Unified Modeling Language “The act of drawing a diagram does not constitute analysis or design. … Still, having a well-defined and.
Introduction to UML By: Prof. Aiman Hanna Department of Computer Science, Concordia University, Montreal, Canada.
Unified Modeling Language, Version 2.0
Introduction To System Analysis and Design
Software development process ธนวัฒน์ แซ่ เอียบ. The development process Process –set of rules which define how a development project. Methodology and.
Requirements Artifacts Precursor to A & D. Objectives: Requirements Overview  Understand the basic Requirements concepts and how they affect Analysis.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
1 Devon M. Simmonds University of North Carolina, Wilmington CSC450 Software Engineering WorkFlow Modeling with Activity Diagrams.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
Copyright © 2013 Curt Hill UML Unified Modeling Language.
 What is Modeling What is Modeling  Why do we Model Why do we Model  Models in OMT Models in OMT  Principles of Modeling Principles of Modeling 
Course Instructor: Kashif Ihsan 1. Chapter # 3 2.
Michael Schloh von Bennewitz 1. Oktober 2002 The Unified Modeling Language Overview of theory and practice of the OMG Unified Modeling.
Introduction to UML CS A470. What is UML? Unified Modeling Language –OMG Standard, Object Management Group –Based on work from Booch, Rumbaugh, Jacobson.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 UML 1 UML unified modeling language 1994 first attempts - largely theoretical 1997 UML.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Week 04 Object Oriented Analysis and Designing. What is a model? A model is quicker and easier to build A model can be used in simulations, to learn more.
CSCI 3428: Software Engineering Tami Meredith UML Unified Modeling Language.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
1 BTS330 Visual Modeling. What is Visual Modeling? 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship.
CSCI 383 Object-Oriented Programming & Design Lecture 7 Martin van Bommel.
CS 501: Software Engineering Fall 1999 Lecture 15 Object-Oriented Design I.
UML. Model An abstract representation of a system. Types of model 1.Use case model 2.Domain model 3.Analysis object model 4.Implementation model 5.Test.
Software Engineering: Models David Millard
Introduction to Unified Modeling Language (UML) By Rick Mercer with help from The Unified Modeling Language User Guide, Grady Booch, James Rumbaugh, Ivar.
SWE 214 (071) Introduction to UML Slide 1 Introduction to UML.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 14 Slide 1 Object-Oriented Design.
1 An Overview of UML. 2 The Unified Modeling Language UML is a graphical language used by software engineers to model software systems during development.
UML (Unified Modeling Language)
GOVT. ENGINEERING COLLEGE, AJMER. A SEMINAR PRESENTATION ON UNIFIED MODELING LANGUAGE(UML) SUBMITTED TO:-PRESENTED BY:- Dr. REENA DADHICHPALLAVI VASHISTHA.
Use Cases UML. Use Cases What are Use Cases?  A statement of the functionality users expect and need, organized by functional units  Different from.
Introduction to UML.
Introduction to the Unified Modeling Language
Activity and State Transition Diagram
Introduction to UML.
Software Design Lecture : 15.
Appendix 3 Object-Oriented Analysis and Design
Presentation transcript:

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

Subjects

ADMS-BIS UML Introduction

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.

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

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.

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).

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

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

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)

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

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.

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

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.

ADMS-BIS UML: graphical notations 1

ADMS-BIS UML: graphical notations 2

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

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

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

ADMS-BIS Use Case diagram

ADMS-BIS Class Diagram

ADMS-BIS Object diagram

ADMS-BIS Sequence diagram

ADMS-BIS Activity diagram

ADMS-BIS Component diagram

ADMS-BIS Deployment diagram

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

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

ADMS-BIS Activity Diagram

ADMS-BIS Example

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

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

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

ADMS-BIS UML Activity symbols

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

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

ADMS-BIS Branch & Merge

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

ADMS-BIS Forks, Joins & conditional Threads

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).

ADMS-BIS Solution Exercise 1

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.

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.

ADMS-BIS Solution Exercise 2

ADMS-BIS Date2date example: scenario’s

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

ADMS-BIS Date2date : Inloggen abonnee – activity diagram

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

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

ADMS-BIS Use Case diagram ‘NS Ticket service’

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)

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

ADMS-BIS Microsoft Visio

ADMS-BIS Microsoft Visio Install Microsoft Visio via n_diensten/ dan: PC Software InstallatiePC Software Installatie Grafische ApplicatiesGrafische Applicaties MS Visio ProfessionalMS Visio Professional

ADMS-BIS

Task UML part 1

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)