DOCSLIB.ORG

UML Activity Diagrams, State-Machine Diagrams and Modelling Lecture # 2

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
UML Activity Diagrams, State-Machine Diagrams and Modelling Lecture # 2 UML Activity Diagrams, State-Machine Diagrams and Modelling Lecture # 2 Department of Computer Science and Technology University of Bedfordshire Written by David Goodwin, based on the book Applying UML and Patterns (3rd ed.) by C. Larman (2005). Modelling and Simulation, 2012 UML Activity Outline Diagrams, State-Machine Diagrams and Modelling Activity Diagrams Introduction Activity Activity Diagrams - notation Diagrams Introduction How to apply activity diagrams Activity Diagrams - notation Guidelines How to apply activity diagrams Guidelines State-Machine Diagrams State-Machine Diagrams Introduction Introduction State-Machine State-Machine Diagrams - notation Diagrams - How to apply state-machine diagrams notation How to apply state-machine diagrams Further Examples Further Examples UML Activity Diagrams, State-Machine Diagrams and Modelling Activity Diagrams Introduction Activity Diagrams Activity Diagrams - notation How to apply activity diagrams Guidelines State-Machine Diagrams Introduction State-Machine Diagrams - notation How to apply state-machine diagrams Further Examples UML Activity What is an Activity Diagram Diagrams, State-Machine Diagrams and Modelling I An Activity Diagram is on of the Behaviour diargams. I Activity modelling is the sequence and conditions for coordinating lower-level behaviours, rather than which classifiers own those behaviours. Activity Diagrams I These are commonly called control flow and object flow Introduction Activity Diagrams models. - notation How to apply I The behaviours coordinated by these models can be activity diagrams initiated because other behaviours finish executing, Guidelines State-Machine because objects and data become available, or because Diagrams events occur external to the flow. Introduction State-Machine I A UML Activity Diagram shows sequential and parallel Diagrams - notation activities in a process. How to apply state-machine I Useful for modelling: diagrams I Business processes Further Examples I Workflows I Data flows I Complex algorithms UML Activity Basic UML Activity Diagram notation Diagrams, State-Machine Diagrams and Modelling Action It does something. There is automatic transition on its completion. A transition Activity (arrows between actions) supports modelling of Diagrams Introduction control flow. Activity Diagrams - notation Fork One incoming transition, and multiple outgoing How to apply activity diagrams parallel transitions and/or object flows. Guidelines Multiple incoming transitions and/or object State-Machine Join Diagrams flows; one outgoing transitions. The outgoing Introduction State-Machine continuation does not happen until all the Diagrams - notation inputs arrive from all flows. How to apply state-machine Object Node An object produced or used by actions. This diagrams Further allows us to model data flows or object flows. Examples UML Activity Initial and Final Nodes Diagrams, State-Machine Diagrams and Modelling I Initial Node: I An initial node is a control node at which flow starts when the activity is invoked. I An activity may have more than one initial node. Activity Diagrams Introduction Activity Diagrams - notation How to apply activity diagrams Guidelines State-Machine Diagrams I Final Node: Introduction State-Machine I An activity may have more than one activity final node; Diagrams - the first one reached stops all flows in the activity. notation How to apply state-machine diagrams Further Examples UML Activity Action Diagrams, State-Machine Diagrams and Modelling I Action: I An action represents a single step within an activity that is not further decomposed within the activity. I An activity represents a behaviour that is composed of Activity individual elements that are actions. Diagrams Introduction I An action is simple from the point of view of the Activity Diagrams activity containing it, but may be complex in its effect - notation How to apply and not be atomic. activity diagrams I An activity can be reused in many places, whereas an Guidelines instance of an action is only used once at a particular State-Machine point in an activity. Diagrams Introduction I An action will not begin execution until all of its input State-Machine Diagrams - conditions are satisfied. notation How to apply state-machine diagrams Further Examples UML Activity Merge and Decision Nodes Diagrams, State-Machine Diagrams and Modelling I Merge Node: I A merge node is a control node that brings together multiple alternate flows. Activity I It is not used to synchronize concurrent flows but to Diagrams accept one among several alternate flows. Introduction I Activity Diagrams A merge node has multiple incoming edges and a single - notation outgoing edge. How to apply activity diagrams I Decision Node: Guidelines I A decision node accepts tokens on an incoming edge State-Machine Diagrams and presents them to multiple outgoing edges. Introduction I Which of the edges is actually traversed depends on the State-Machine Diagrams - evaluation of the guards on the outgoing edges. notation How to apply state-machine diagrams Further Examples UML Activity Join and Fork Nodes Diagrams, State-Machine Diagrams and Modelling I Join Node: I A join node is a control node that synchronizes multiple flows. I A join node has multiple incoming edges and one Activity outgoing edge. Diagrams Introduction I Fork Node: Activity Diagrams - notation I A fork node is a control node that splits a flow into How to apply multiple concurrent flows. activity diagrams Guidelines I A fork node has one incoming edge and multiple State-Machine outgoing edges. Diagrams Introduction State-Machine Diagrams - notation How to apply state-machine diagrams Further Examples UML Activity Object Node Diagrams, State-Machine Diagrams and Modelling I Object Node: I An object node is an activity node that indicates an Activity instance of a particular classifier, possibly in a particular Diagrams state, may be available at a particular point in the Introduction Activity Diagrams activity. - notation How to apply I Object nodes can be used in a variety of ways, activity diagrams depending on where objects are flowing from and to. Guidelines State-Machine Diagrams Introduction State-Machine Diagrams - notation How to apply state-machine diagrams Further Examples UML Activity Note Diagrams, State-Machine Diagrams and Modelling I Note: Activity Diagrams I A note (comment) gives the ability to attach various Introduction remarks to elements. Activity Diagrams - notation I A comment carries no semantic force, but may contain How to apply information that is useful to a modeller. activity diagrams Guidelines State-Machine Diagrams Introduction State-Machine Diagrams - notation How to apply state-machine diagrams Further Examples UML Activity Buisness Process Modelling Diagrams, State-Machine Diagrams and Modelling Activity I Example: Parcel shipping Diagrams Introduction I The process of shipping a parcel is non-trivial; there are Activity Diagrams many parties involived (customer, driver,. ) and many - notation How to apply steps. activity diagrams I The process can be captured by a Use Case diagram, Guidelines but activity diagrams are great example of \a picture State-Machine Diagrams being worth a thousand words". Introduction I Object nodes are useful for illustrating what is moving State-Machine Diagrams - around. notation How to apply state-machine diagrams Further Examples UML Activity Activity Diagram Parcel shipping Diagrams, State-Machine Diagrams and Modelling Activity Diagrams Introduction Activity Diagrams - notation How to apply activity diagrams Guidelines State-Machine Diagrams Introduction State-Machine Diagrams - notation How to apply state-machine diagrams Further Examples UML Activity Guideline for Activity Modelling Diagrams, State-Machine Diagrams and Modelling I The technique proves most valuable for very complex Activity processes, usually involving many parties. Diagrams Introduction I On a first overview \level 0" diagram, keep all the Activity Diagrams - notation actions at a very high level of abstraction, so that the How to apply activity diagrams diagram is short. Then expand details in sub-diagrams Guidelines at the \level 1" level,. etc. State-Machine Diagrams I Try to make the level of abstraction of action nodes Introduction State-Machine roughly equal withn a diagram (Very different levels of Diagrams - abstraction might be a node labelled \Deliver Order" notation How to apply state-machine and a node labelled \Calculate Tax"). diagrams Further Examples UML Activity Diagrams, State-Machine Diagrams and Modelling Activity Diagrams Introduction State-Machine Activity Diagrams - notation How to apply Diagrams activity diagrams Guidelines State-Machine Diagrams Introduction State-Machine Diagrams - notation How to apply state-machine diagrams Further Examples UML Activity What is a State-Machine Diagram Diagrams, State-Machine Diagrams and Modelling I State-Machine Diagrams specify state machines. I As with Activity Diagrams, UML State-Machine Diagrams show a dynamic flow. Activity Diagrams I The UML includes notation to illustrate events and Introduction states of things (transactions, Use Cases, Activity Diagrams - notation people,. etc.). How to apply activity diagrams I An event is a significant or noteworthy occurence e.g. a Guidelines telephone receiver is taken off the hook. State-Machine Diagrams I A state is the condition of an object at a moment in Introduction time e.g. a telephone is in the state of being \idle" State-Machine Diagrams - after the receiver is place on the hook
Load more

Recommended publications
  • Activity Diagram Inheritance1
    Activity Diagram Inheritance1 Arnd Schnieders, Frank Puhlmann Hasso-Plattner-Institute for IT Systems Engineering at the University of Potsdam {schnieders, puhlmann}@hpi.uni-potsdam.de Abstract This paper outlines the ongoing work on the realization of a flexible inheritance mechanism for Activity Diagrams that assures the maintenance of syntactical correctness for the derived Activity Diagrams. The objective is to support the reuse of process models especially by applying Activity Diagram inheritance as a variability mechanism in the context of product line oriented software development. Keywords: Activity Diagrams, domain engineering, process inheritance, variability mechanism 1. Introduction In industry similar products are frequently developed and produced as product lines. One of the main advantages is a gain of efficiency in development and production since parts, which are common for several product line members, can be reused optimally. This approach has been transferred successfully to software development and is also known by the name domain engineering. Variability mechanisms are thereby important for the effectiveness of domain engineering. A great number of variability mechanisms has already been published [5, 9, 11, 13, 18]. Unfortunately, existing variability mechanisms only refer to the static aspects of a software system’s design while the impact of variability mechanisms on the process view on the system has been strongly neglected. Therefore, the first contribution of this paper is to contribute to closing this gap by making the important variability mechanism inheritance available for process design models in order to derive process model variants. The second contribution of this paper is to show how the defined process inheritance mechanism is realized concretely for UML 2.0 Activity Diagrams.
    [Show full text]
  • Uml.Sty, a Package for Writing UML Diagrams in LATEX
    uml.sty, a package for writing UML diagrams in LATEX Ellef Fange Gjelstad March 17, 2010 Contents 1 Syntax for all the commands 5 1.1 Lengths ........................................ 5 1.2 Angles......................................... 5 1.3 Nodenames...................................... 6 1.4 Referencepoints ................................. 6 1.5 Colors ......................................... 6 1.6 Linestyles...................................... 6 2 uml.sty options 6 2.1 debug ......................................... 6 2.2 index.......................................... 6 3 Object-oriented approach 7 3.1 Colors ......................................... 10 3.2 Positions....................................... 10 4 Drawable 12 4.1 Namedoptions .................................... 12 4.1.1 import..................................... 12 5 Element 12 5.1 Namedoptions .................................... 12 5.1.1 Reference ................................... 12 5.1.2 Stereotype................................... 12 5.1.3 Subof ..................................... 13 5.1.4 ImportedFrom ................................ 13 5.1.5 Comment ................................... 13 6 Box 13 6.1 Namedoptionsconcerninglocation . ....... 13 6.2 Boxesintext ..................................... 14 6.3 Named options concerning visual appearance . ......... 14 6.3.1 grayness.................................... 14 6.3.2 border..................................... 14 1 6.3.3 borderLine .................................. 14 6.3.4 innerBorder.................................
    [Show full text]
  • OMG Systems Modeling Language (OMG Sysml™) Tutorial 25 June 2007
    OMG Systems Modeling Language (OMG SysML™) Tutorial 25 June 2007 Sanford Friedenthal Alan Moore Rick Steiner (emails included in references at end) Copyright © 2006, 2007 by Object Management Group. Published and used by INCOSE and affiliated societies with permission. Status • Specification status – Adopted by OMG in May ’06 – Finalization Task Force Report in March ’07 – Available Specification v1.0 expected June ‘07 – Revision task force chartered for SysML v1.1 in March ‘07 • This tutorial is based on the OMG SysML adopted specification (ad-06-03-01) and changes proposed by the Finalization Task Force (ptc/07-03-03) • This tutorial, the specifications, papers, and vendor info can be found on the OMG SysML Website at http://www.omgsysml.org/ 7/26/2007 Copyright © 2006,2007 by Object Management Group. 2 Objectives & Intended Audience At the end of this tutorial, you should have an awareness of: • Benefits of model driven approaches for systems engineering • SysML diagrams and language concepts • How to apply SysML as part of a model based SE process • Basic considerations for transitioning to SysML This course is not intended to make you a systems modeler! You must use the language. Intended Audience: • Practicing Systems Engineers interested in system modeling • Software Engineers who want to better understand how to integrate software and system models • Familiarity with UML is not required, but it helps 7/26/2007 Copyright © 2006,2007 by Object Management Group. 3 Topics • Motivation & Background • Diagram Overview and Language Concepts • SysML Modeling as Part of SE Process – Structured Analysis – Distiller Example – OOSEM – Enhanced Security System Example • SysML in a Standards Framework • Transitioning to SysML • Summary 7/26/2007 Copyright © 2006,2007 by Object Management Group.
    [Show full text]
  • Rational Unified Process - an Overview Uppsala, 2009-02-10
    Rational Unified Process - an overview Uppsala, 2009-02-10 Mikael Broomé Consultant M.Sc. LTH 10 years in Software Development 4 different RUP implementations Project Manager Mentor for Project Managers Applying more and more of agile mindset and techniques E-Mail: [email protected] 2 1 Agenda Why a process for developing software? What is RUP? What is the “RUP-way” of developing software? How is RUP packaged? Advantages by using RUP? Challenges when using RUP? Relation to other processes? 3 A good project delivers the right solution: satisified Users satisfied Sponsor delivers in time delivers on budget 4 2 Challenges Common challenges in software development projects: Capture the “right” requirements. Requirement changes. Different parts of the system do not fit together. Small changes causes big problems. Low quality and poor performance. Major problems identified late in projects. Lack of communication. Difficult to estimate time and cost. Management of environment, platforms and tools. 5 It’s all about (lack of) communication 6 3 Agenda Why a process for developing software? What is RUP? What is the “RUP-way” of developing software? How is RUP packaged? Advantages by using RUP? Challenges when using RUP? Relation to other processes? 7 What is RUP and UML? RUP is a process for development of software that describes what should be performed (activities) who should do it (roles) what the result should be (artifacts). UML is a notation with defined symbols that is worked out by OMG (Object Management Group) is used to make drawings (for example in software development). 8 4 Agenda Why a process for developing software? What is RUP? What is the “RUP-way” of developing software? How is RUP packaged? Advantages by using RUP? Challenges when using RUP? Relation to other processes? 9 JW2 RUP’s Six Best practices 1.
    [Show full text]
  • EB GUIDE Documentation Version 6.1.0.101778 EB GUIDE Documentation
    EB GUIDE documentation Version 6.1.0.101778 EB GUIDE documentation Elektrobit Automotive GmbH Am Wolfsmantel 46 D-91058 Erlangen GERMANY Phone: +49 9131 7701-0 Fax: +49 9131 7701-6333 http://www.elektrobit.com Legal notice Confidential and proprietary information. ALL RIGHTS RESERVED. No part of this publication may be copied in any form, by photocopy, microfilm, retrieval system, or by any other means now known or hereafter invented without the prior written permission of Elektrobit Automotive GmbH. ProOSEK®, tresos®, and street director® are registered trademarks of Elektrobit Automotive GmbH. All brand names, trademarks and registered trademarks are property of their rightful owners and are used only for description. Copyright 2015, Elektrobit Automotive GmbH. Page 2 of 324 EB GUIDE documentation Table of Contents 1. About this documentation ................................................................................................................ 15 1.1. Target audiences of the user documentation ......................................................................... 15 1.1.1. Modelers .................................................................................................................. 15 1.1.2. System integrators .................................................................................................... 16 1.1.3. Application developers ............................................................................................... 16 1.1.4. Extension developers ...............................................................................................
    [Show full text]
  • Network Visualization with R Katherine Ognyanova, POLNET 2015 Workshop, Portland OR
    Network visualization with R Katherine Ognyanova, www.kateto.net POLNET 2015 Workshop, Portland OR Contents Introduction: Network Visualization2 Data format, size, and preparation4 DATASET 1: edgelist ......................................4 DATASET 2: matrix .......................................5 Network visualization: first steps with igraph 5 A brief detour I: Colors in R plots8 A brief detour II: Fonts in R plots 11 Back to our main plot line: plotting networks 12 Plotting parameters ........................................ 12 Network Layouts ......................................... 17 Highlighting aspects of the network ............................... 24 Highlighting specific nodes or links ............................... 27 Interactive plotting with tkplot ................................. 29 Other ways to represent a network ............................... 30 Plotting two-mode networks with igraph ............................ 31 Quick example using the network package 35 Interactive and animated network visualizations 37 Interactive D3 Networks in R .................................. 37 Simple Plot Animations in R .................................. 38 Interactive networks with ndtv-d3 ................................ 39 Interactive plots of static networks............................ 39 Network evolution animations............................... 40 1 Introduction: Network Visualization The main concern in designing a network visualization is the purpose it has to serve. What are the structural properties that we want to highlight?
    [Show full text]
  • Sysml, the Language of MBSE Paul White
    Welcome to SysML, the Language of MBSE Paul White October 8, 2019 Brief Introduction About Myself • Work Experience • 2015 – Present: KIHOMAC / BAE – Layton, Utah • 2011 – 2015: Astronautics Corporation of America – Milwaukee, Wisconsin • 2001 – 2011: L-3 Communications – Greenville, Texas • 2000 – 2001: Hynix – Eugene, Oregon • 1999 – 2000: Raytheon – Greenville, Texas • Education • 2019: OMG OCSMP Model Builder—Fundamental Certification • 2011: Graduate Certification in Systems Engineering and Architecting – Stevens Institute of Technology • 1999 – 2004: M.S. Computer Science – Texas A&M University at Commerce • 1993 – 1998: B.S. Computer Science – Texas A&M University • INCOSE • Chapters: Wasatch (2015 – Present), Chicagoland (2011 – 2015), North Texas (2007 – 2011) • Conferences: WSRC (2018), GLRCs (2012-2017) • CSEP: (2017 – Present) • 2019 INCOSE Outstanding Service Award • 2019 INCOSE Wasatch -- Most Improved Chapter Award & Gold Circle Award • Utah Engineers Council (UEC) • 2019 & 2018 Engineer of the Year (INCOSE) for Utah Engineers Council (UEC) • Vice Chair • Family • Married 14 years • Three daughters (1, 12, & 10) 2 Introduction 3 Our Topics • Definitions and Expectations • SysML Overview • Basic Features of SysML • Modeling Tools and Techniques • Next Steps 4 What is Model-based Systems Engineering (MBSE)? Model-based systems engineering (MBSE) is “the formalized application of modeling to support system requirements, design, analysis, verification and validation activities beginning in the conceptual design phase and continuing throughout development and later life cycle phases.” -- INCOSE SE Vision 2020 5 What is Model-based Systems Engineering (MBSE)? “Formal systems modeling is standard practice for specifying, analyzing, designing, and verifying systems, and is fully integrated with other engineering models. System models are adapted to the application domain, and include a broad spectrum of models for representing all aspects of systems.
    [Show full text]
  • UML 2 Toolkit, Penker Has Also Collaborated with Hans- Erik Eriksson on Business Modeling with UML: Business Practices at Work
    UML™ 2 Toolkit Hans-Erik Eriksson Magnus Penker Brian Lyons David Fado UML™ 2 Toolkit UML™ 2 Toolkit Hans-Erik Eriksson Magnus Penker Brian Lyons David Fado Publisher: Joe Wikert Executive Editor: Bob Elliott Development Editor: Kevin Kent Editorial Manager: Kathryn Malm Production Editor: Pamela Hanley Permissions Editors: Carmen Krikorian, Laura Moss Media Development Specialist: Travis Silvers Text Design & Composition: Wiley Composition Services Copyright 2004 by Hans-Erik Eriksson, Magnus Penker, Brian Lyons, and David Fado. All rights reserved. Published by Wiley Publishing, Inc., Indianapolis, Indiana Published simultaneously in Canada No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning, or otherwise, except as permitted under Section 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, Inc., 222 Rose- wood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8700. Requests to the Pub- lisher for permission should be addressed to the Legal Department, Wiley Publishing, Inc., 10475 Crosspoint Blvd., Indianapolis, IN 46256, (317) 572-3447, fax (317) 572-4447, E-mail: [email protected]. Limit of Liability/Disclaimer of Warranty: While the publisher and author have used their best efforts in preparing this book, they make no representations or warranties with respect to the accuracy or completeness of the contents of this book and specifically disclaim any implied warranties of merchantability or fitness for a particular purpose.
    [Show full text]
  • Plantuml Language Reference Guide (Version 1.2021.2)
    Drawing UML with PlantUML PlantUML Language Reference Guide (Version 1.2021.2) PlantUML is a component that allows to quickly write : • Sequence diagram • Usecase diagram • Class diagram • Object diagram • Activity diagram • Component diagram • Deployment diagram • State diagram • Timing diagram The following non-UML diagrams are also supported: • JSON Data • YAML Data • Network diagram (nwdiag) • Wireframe graphical interface • Archimate diagram • Specification and Description Language (SDL) • Ditaa diagram • Gantt diagram • MindMap diagram • Work Breakdown Structure diagram • Mathematic with AsciiMath or JLaTeXMath notation • Entity Relationship diagram Diagrams are defined using a simple and intuitive language. 1 SEQUENCE DIAGRAM 1 Sequence Diagram 1.1 Basic examples The sequence -> is used to draw a message between two participants. Participants do not have to be explicitly declared. To have a dotted arrow, you use --> It is also possible to use <- and <--. That does not change the drawing, but may improve readability. Note that this is only true for sequence diagrams, rules are different for the other diagrams. @startuml Alice -> Bob: Authentication Request Bob --> Alice: Authentication Response Alice -> Bob: Another authentication Request Alice <-- Bob: Another authentication Response @enduml 1.2 Declaring participant If the keyword participant is used to declare a participant, more control on that participant is possible. The order of declaration will be the (default) order of display. Using these other keywords to declare participants
    [Show full text]
  • Sysml Distilled: a Brief Guide to the Systems Modeling Language
    ptg11539604 Praise for SysML Distilled “In keeping with the outstanding tradition of Addison-Wesley’s techni- cal publications, Lenny Delligatti’s SysML Distilled does not disappoint. Lenny has done a masterful job of capturing the spirit of OMG SysML as a practical, standards-based modeling language to help systems engi- neers address growing system complexity. This book is loaded with matter-of-fact insights, starting with basic MBSE concepts to distin- guishing the subtle differences between use cases and scenarios to illu- mination on namespaces and SysML packages, and even speaks to some of the more esoteric SysML semantics such as token flows.” — Jeff Estefan, Principal Engineer, NASA’s Jet Propulsion Laboratory “The power of a modeling language, such as SysML, is that it facilitates communication not only within systems engineering but across disci- plines and across the development life cycle. Many languages have the ptg11539604 potential to increase communication, but without an effective guide, they can fall short of that objective. In SysML Distilled, Lenny Delligatti combines just the right amount of technology with a common-sense approach to utilizing SysML toward achieving that communication. Having worked in systems and software engineering across many do- mains for the last 30 years, and having taught computer languages, UML, and SysML to many organizations and within the college setting, I find Lenny’s book an invaluable resource. He presents the concepts clearly and provides useful and pragmatic examples to get you off the ground quickly and enables you to be an effective modeler.” — Thomas W. Fargnoli, Lead Member of the Engineering Staff, Lockheed Martin “This book provides an excellent introduction to SysML.
    [Show full text]
  • UML 2 Activity and Action Models
    JOURNAL OF OBJECT TECHNOLOGY Online at www.jot.fm. Published by ETH Zurich, Chair of Software Engineering ©JOT, 2003 Vol. 2, No. 4, July-August 2003 UML 2 Activity and Action Models Conrad Bock, National Institute of Standards and Technology This is the first in a series introducing the activity model in the Unified Modeling Language, version 2 (UML 2), and how it integrates with the action model [1]. The series is a companion to the standard, providing additional background, rationale, examples, and introducing concepts in a logical order. This article covers motivation and architecture for the new models, basic aspects of UML 2 activities and actions, and introduces the general notion of behavior in UML 2. 1 BACKGROUND A focus of recent developments in UML has been on procedures and processes. UML 1.5 introduced a model for parameterized procedures defined by control and data flow to complement the existing state and interaction models [2]. For the first time UML supports first-class procedures that can be used as methods on objects or independently of objects, as occurs when modeling, for example, function libraries with popular programming languages. It also facilitates application of UML by modelers who do not use object-orientation (OO) routinely, such as system engineers and enterprise modelers, and provides them a path to incrementally adopt OO as needed [3]. The flexibility to combine OO with functional approaches considerably widens and integrates the potential applications of UML. UML 1.1 UML 1.3 UML 1.5 UML 2.0 1997 1999 2001 2003 Figure 1: UML Timeline UML 1.5 also inherited from earlier versions a form of state machine that was notationally modified to appear as a flow diagram, called the activity diagram.
    [Show full text]
  • UML Profile for Communicating Systems a New UML Profile for the Specification and Description of Internet Communication and Signaling Protocols
    UML Profile for Communicating Systems A New UML Profile for the Specification and Description of Internet Communication and Signaling Protocols Dissertation zur Erlangung des Doktorgrades der Mathematisch-Naturwissenschaftlichen Fakultäten der Georg-August-Universität zu Göttingen vorgelegt von Constantin Werner aus Salzgitter-Bad Göttingen 2006 D7 Referent: Prof. Dr. Dieter Hogrefe Korreferent: Prof. Dr. Jens Grabowski Tag der mündlichen Prüfung: 30.10.2006 ii Abstract This thesis presents a new Unified Modeling Language 2 (UML) profile for communicating systems. It is developed for the unambiguous, executable specification and description of communication and signaling protocols for the Internet. This profile allows to analyze, simulate and validate a communication protocol specification in the UML before its implementation. This profile is driven by the experience and intelligibility of the Specification and Description Language (SDL) for telecommunication protocol engineering. However, as shown in this thesis, SDL is not optimally suited for specifying communication protocols for the Internet due to their diverse nature. Therefore, this profile features new high-level language concepts rendering the specification and description of Internet protocols more intuitively while abstracting from concrete implementation issues. Due to its support of several concrete notations, this profile is designed to work with a number of UML compliant modeling tools. In contrast to other proposals, this profile binds the informal UML semantics with many semantic variation points by defining formal constraints for the profile definition and providing a mapping specification to SDL by the Object Constraint Language. In addition, the profile incorporates extension points to enable mappings to many formal description languages including SDL. To demonstrate the usability of the profile, a case study of a concrete Internet signaling protocol is presented.
    [Show full text]