DOCSLIB.ORG

Brief Introduction to UML 2.0 (For SEG Seminar)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Brief Introduction to UML 2.0 (for SEG seminar) Tian Zhang Nanjing University,China October 2005 Outline Part I : Background Process of UML 2.0 adoption Part II: Overview of UML 2.0 Superstructure Tian Zhang @ Nanjing University 2 Part I OMG's technology adoption process UML 1.4, 1.5, 2.0 UML 2.0 in MDA The current status of UML 2.0 Tian Zhang @ Nanjing University 3 OMG's Technology Adoption Process 1. Optional RFI stage OMG在1999年提出UML的修订信息需求 来自不同领域的26个响应者大多数提议进行重大修订 2. TF issues RFP, evaluates submissions OMG于2000年初发布UML2.0的四部分提案需求 3. Voting to Adopt an OMG specification 4. Finalization - getting ready for prime time 今年10月通过了Superstructure的最终正式版 其余部分仍处于最终修改版阶段 5. The OMG specification maintenance Cycle 6. Retiring Obsolete Specifications Tian Zhang @ Nanjing University 4 UML 2.0 RFPs Superstructure Diagram Interchange Defines user-level constructs to specify structure and behavior of systems (e.g., class diagrams, sequence diagrams) Infrastructure OCL Defines basic constructs to specify UML and to customize it for specific domains (e.g., real-time) Tian Zhang @ Nanjing University 5 UML 2.0 Infrastructure设计目标 定义一个元语言的核心 – 基础结构库(Infra- structureLibrary)通过对此核心的复用，除了 可以定义一个自展的UML元模型之外，还可以 定义其他元模型，包括MOF和CWM； 通过共用核心包，UML和MOF、CWM在体系 结构上保持一致。 Tian Zhang @ Nanjing University 6 Goals of UML 2.0 Superstructure Restructure and refine the language to make it easier to apply, implement and customize Improve support for component-based development specify both platform-independent components (e.g., business components) and platform-specific components (e.g., EJB, COM+) Refine architectural specification capabilities support hierarchical composition of parts with interfaces (compare SDL blocks and processes) Increase the scalability, precision and integration of behavioral diagrams augment sequence diagrams with advanced constructs from MSCs that can be combined and integrated with other behavior update state machines diagrams to make generalizable and able to support a transition-centric view revise activity diagrams to support more flexible parallelism and furnish more I/O options support executable models Review all UML 1.x constructs and diagrams Tian Zhang @ Nanjing University 7 UML 2.0 Superstructure 设计目标 严格地复用Infrastructure中的模型构造物； 既可以描述平台无关构件（如业务构件），也可以描 述平台相关构件（如EJB，COM+等），提高对基于 构件开发和MDA的支持； 支持接口、部件和连接子，及其层次化组合能力，从 而提高对架构的规约能力； 增强行为图的可伸缩性、精确性和集成能力； 支持可执行模型； 审定所有UML1.x的构造物和图，适当地精化、取缔 和逐步淘汰。 Tian Zhang @ Nanjing University 8 UML 2.0, The Current Official Version: UML 2.0 Superstructure formal/05-07-04 is complete - stable since it took its adopted form in October, 2004. UML 2.0 Infrastructure ptc/04-10-14 UML 2.0 Diagram Interchange ptc/05-06-04 UML 2.0 OCL ptc/05-06-06 Pages Statistic Infrastructure : 226 pages Superstructure : 709 pages Diagram Interchange : 82 pages OCL : 185 pages Tian Zhang @ Nanjing University 9 UML 2.0 in MDA MDA的核心规范： • Meta Object Facility • MOF current version 1.4 • Unified Modeling Language • UML current version 1.5 • Common Warehouse Metamodel • CWM current version 1.0 • XML Metadata Interchange • XMI current version 2.1 Tian Zhang @ Nanjing University 10 The Role of UML & MOF in The MDA The following was approved unanimously by 17 participants at the ORMSC: Any modeling language used in MDA must be described in terms of the MOF language, to enable the metadata to be understood in a standard manner, which is a precondition for any ability to perform automated transformations. ORMSC plenary session August 26, 2004 Tian Zhang @ Nanjing University 11 Part II UML 2.0 Superstructure Specification Thirteen diagrams in UML 2.0 Tian Zhang @ Nanjing University 12 UML 2.0 Superstructure UML 1.5 formal/03-03-01 Part I: Structure 1. UML Summary Classes 2. UML Semantics Components Part 1 - Background Composite Structures Part 2 - Foundation Part 3 - Behavioral Elements Deployments Part 4 - General Mechanisms Part II: Behavior Part 5 - Actions Actions 3. UML Notation Guide Activities Part 1 - Background Common Behaviors Part 2 - Diagram Elements Interactions Part 3 – Model Management State Machines Part 4 - General Extension Mechanisms Use Cases Part 5 - Static Structure Diagrams Part III: Supplement Part 6 - Use Case Diagrams Auxiliary Constructs Part 7 - Interaction Diagrams Profiles Part 8 - Collaboration Diagrams Part IV – Annexes Part 9 - Statechart Diagrams A - Diagrams Part 10 - Activity Diagrams B - UML Keywords 4. UML Example Profiles C - Standard Stereotypes 5. UML Model Interchange Tian Zhang @ Nanjing University 13 Language Units The modeling concepts of UML are grouped into language units. For example, the State Machines language unit enables modelers to specify discrete event-driven behavior using a variant of the well-known statecharts formalism. Two benefits : easy to learn and use easy to define compliance levels Tian Zhang @ Nanjing University 14 Compliance Levels Level 0 (L0) - This level is formally defined in the UML Infrastructure. Level 1 (L1) - It adds language units for use cases, interactions, structures, actions, and activities. Level 2 (L2) - It adds language units for deployment, state machine modeling, and profiles. Level 3 (L3) - This level represents the complete UML. Tian Zhang @ Nanjing University 15 Diagrams in UML 2.0 与UML1.x相比，UML 2.0将结构元素和行为元素结合 起来建模的能力大大增强； UML 2.0支持13种图(UML 1.x支持9种图)； Class Diagram Activity Diagram Composite Structure Diagram Communication Diagram Component Diagram Interaction Overview Diagram Deployment diagram State Machine Diagram Object Diagram Sequence Diagram Package Diagram Timing Diagram Use Case Diagram Tian Zhang @ Nanjing University 16 Tian Zhang @ Nanjing University 17 Changes from 1.x Add four diagrams; Renamed two diagrams: 原来的协作图(Collaboration Diagrams)改名为通讯图 (Communication Diagrams) ，但语义并没有丰富到与 顺序图等价的地步； 原来的状态图(Statechart Diagrams)改名为状态机图 (State Machine Diagrams)，解决了1.x中状态图和状态 机的语义重叠、模糊不清的问题。 Tian Zhang @ Nanjing University 18 Thirteen diagrams in UML 2.0 Structure Diagram Class Diagram Composite Structure Diagram Component Diagram Deployment diagram Object Diagram Package Diagram Behavior Diagram Activity Diagram Use Case Diagram State Machine Diagram Communication Diagram Sequence Diagram Interaction Overview Diagram Timing Diagram Tian Zhang @ Nanjing University 19 Composite Structure Diagram One of the most significant new features in UML 2 is the ability to hierarchically decompose a class into an internal structure. This allows you to take a complex object and break it down into parts The core constructs of Composite Structures are: Part Connector Port Tian Zhang @ Nanjing University 20 Example 1 – TV (1) Fig. 1. Two ways of showing a TV viewer and its interfaces Tian Zhang @ Nanjing University 21 Example 1 – TV (2) 内部结构表示出一个类 如何在内部分解成两部 分以及哪些部分支持并 需要哪些不同接口。 该图说明了每一个TV 观众包含一个控制部分 和一个发生器部分。 Fig. 2. Internal view of a component (example suggested by Jim Rumbaugh) Tian Zhang @ Nanjing University 22 Example 1 – TV (3) Fig. 3. A component with multiple ports You can add ports to the external structure ports allow you to group the required and provided interfaces to show logical interactions that a component has with the outside world Tian Zhang @ Nanjing University 23 When to Use Composite Structures Compare with Packages packages are a compile-time grouping composite structures show runtime groupings Natural fit for showing components and how they are broken into parts Much of this notation is used in component diagrams (Martin Flower). Tian Zhang @ Nanjing University 24 Thirteen diagrams in UML 2.0 Structure Diagram Class Diagram Composite Structure Diagram Component Diagram Deployment diagram Object Diagram Package Diagram Behavior Diagram Activity Diagram Use Case Diagram State Machine Diagram Communication Diagram Sequence Diagram Interaction Overview Diagram Timing Diagram Tian Zhang @ Nanjing University 25 Package Diagrams A package is a grouping construct that allows you to take any construct in the UML and group its elements together into higher-level units Each package represents a namespace Use double colons to show package names in UML System::Date Subsystem::Util::Date Tian Zhang @ Nanjing University 26 Packages and Dependencies Fig. 4. Package diagram for an enterprise application Tian Zhang @ Nanjing University 27 Implementing Packages Fig. 5. A package implemented by other packages It's quite common for an interface and its implementation to be in separate packages Tian Zhang @ Nanjing University 28 Implementing Packages This is an example of the pattern Separated Interface. Fig. 6. Defining a required interface in a client package Tian Zhang @ Nanjing University 29 Thirteen diagrams in UML 2.0 Structure Diagram Class Diagram Composite Structure Diagram Component Diagram Deployment diagram Object Diagram Package Diagram Behavior Diagram Activity Diagram Use Case Diagram State Machine Diagram Communication Diagram Sequence Diagram Interaction Overview Diagram Timing Diagram Tian Zhang @ Nanjing University 30 Behavior Diagrams Part II: Behavior 11. Actions 12. Activities 13. Common Behaviors 14. Interactions 15. State Machines 16. Use Cases (cite in Table of Contents) Tian Zhang @ Nanjing University 31 The UML packages that support behavioral modeling, along with the structure packages they depend upon (CompositeStructures and Classes) are shown in the figure above. Tian Zhang @ Nanjing University 32 Thirteen diagrams in UML 2.0 Structure Diagram Class
Recommended publications
  • Communication Diagram.Pdf

    Communication Diagram.Pdf

    TU2943: Information Engineering Methodology Lab Notes, 2009-2010, Faculty of Technology and Information Science, Universiti Kebangsaan Malaysia LAB 5: Interaction Diagram - UML Communication Diagram OBJECTIVES To understand the role of dynamic models in requirement analysis by reading and constructing UML Communication Diagram. INTRODUCTION Communication Diagram (a.k.a. Collaboration Diagram) Communication Diagram provides another way to model a scenario. Essentially is a part of Interaction Diagram (just like Sequence Diagram). Each object is represented by an object icon, and links are used to indicate communication paths on which messages are transmitted. Messages presented in the same way as those in sequence diagram. Formerly known as Collaboration Diagram in UML 1.x specification. Communication Diagram represents a combination of information taken from Use Case, Class and Sequence Diagrams describing both the static structure and dynamic behavior of the system. Comparing and Contrasting: Collaboration and Sequence Both diagrams show the same information: Objects/classes Messages Sequence Conditional Repetition Messages to self Sequence Diagram and Communication Diagram are two views of the same scenario. Collaboration diagrams emphasize who-is-talking-to-who. But the time-ordering of the messages who gets obscured. Sequence diagrams emphasize time-ordering. But the who-is-talking-to-who gets obscured. Use the diagram that you are most comfortable with. Structure and Notation of Communication Diagram Objects are named <an object name>:< its class> . Nor Samsiah Binti Sani 1 TU2943: Information Engineering Methodology Lab Notes, 2009-2010, Faculty of Technology and Information Science, Universiti Kebangsaan Malaysia Either <an object name> or <a class name> can be removed. Collaborations / communications are shown by lines between objects.
  • OMG Systems Modeling Language (OMG Sysml™) Tutorial 25 June 2007

    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.
  • VI. the Unified Modeling Language UML Diagrams

    VI. the Unified Modeling Language UML Diagrams

    Conceptual Modeling CSC2507 VI. The Unified Modeling Language Use Case Diagrams Class Diagrams Attributes, Operations and ConstraintsConstraints Generalization and Aggregation Sequence and Collaboration Diagrams State and Activity Diagrams 2004 John Mylopoulos UML -- 1 Conceptual Modeling CSC2507 UML Diagrams I UML was conceived as a language for modeling software. Since this includes requirements, UML supports world modeling (...at least to some extend). I UML offers a variety of diagrammatic notations for modeling static and dynamic aspects of an application. I The list of notations includes use case diagrams, class diagrams, interaction diagrams -- describe sequences of events, package diagrams, activity diagrams, state diagrams, …more... 2004 John Mylopoulos UML -- 2 Conceptual Modeling CSC2507 Use Case Diagrams I A use case [Jacobson92] represents “typical use scenaria” for an object being modeled. I Modeling objects in terms of use cases is consistent with Cognitive Science theories which claim that every object has obvious suggestive uses (or affordances) because of its shape or other properties. For example, Glass is for looking through (...or breaking) Cardboard is for writing on... Radio buttons are for pushing or turning… Icons are for clicking… Door handles are for pulling, bars are for pushing… I Use cases offer a notation for building a coarse-grain, first sketch model of an object, or a process. 2004 John Mylopoulos UML -- 3 Conceptual Modeling CSC2507 Use Cases for a Meeting Scheduling System Initiator Participant
  • Unified Modeling Language 2.0 Part 1 - Introduction

    Unified Modeling Language 2.0 Part 1 - Introduction

    UML 2.0 – Tutorial (v4) 1 Unified Modeling Language 2.0 Part 1 - Introduction Prof. Dr. Harald Störrle Dr. Alexander Knapp University of Innsbruck University of Munich mgm technology partners (c) 2005-2006, Dr. H. Störrle, Dr. A. Knapp UML 2.0 – Tutorial (v4) 2 1 - Introduction History and Predecessors • The UML is the “lingua franca” of software engineering. • It subsumes, integrates and consolidates most predecessors. • Through the network effect, UML has a much broader spread and much better support (tools, books, trainings etc.) than other notations. • The transition from UML 1.x to UML 2.0 has – resolved a great number of issues; – introduced many new concepts and notations (often feebly defined); – overhauled and improved the internal structure completely. • While UML 2.0 still has many problems, current version (“the standard”) it is much better than what we ever had formal/05-07-04 of August ‘05 before. (c) 2005-2006, Dr. H. Störrle, Dr. A. Knapp UML 2.0 – Tutorial (v4) 3 1 - Introduction Usage Scenarios • UML has not been designed for specific, limited usages. • There is currently no consensus on the role of the UML: – Some see UML only as tool for sketching class diagrams representing Java programs. – Some believe that UML is “the prototype of the next generation of programming languages”. • UML is a really a system of languages (“notations”, “diagram types”) each of which may be used in a number of different situations. • UML is applicable for a multitude of purposes, during all phases of the software lifecycle, and for all sizes of systems - to varying degrees.
  • APECS: Polychrony Based End-To-End Embedded System Design and Code Synthesis

    APECS: Polychrony Based End-To-End Embedded System Design and Code Synthesis

    APECS: Polychrony based End-to-End Embedded System Design and Code Synthesis Matthew E. Anderson Dissertation submitted to the faculty of the Virginia Polytechnic Institute and State University in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Computer Engineering Sandeep K. Shukla, Chair Lamine Mili Alireza Haghighat Chao Wang Yi Deng April 3, 2015 Blacksburg, Virginia Keywords: AADL, CPS, Model-based code synthesis, correct-by-construction code synthesis, Polychrony, code generators, OSATE, Ocarina Copyright 2015, Matthew E. Anderson APECS: Polychrony based End-to-End Embedded System Design and Code Synthesis Matthew E. Anderson (ABSTRACT) The development of high integrity embedded systems remains an arduous and error-prone task, despite the efforts by researchers in inventing tools and techniques for design automa- tion. Much of the problem arises from the fact that the semantics of the modeling languages for the various tools, are often distinct, and the semantics gaps are often filled manually through the engineer's understanding of one model or an abstraction. This provides an op- portunity for bugs to creep in, other than standardising software engineering errors germane to such complex system engineering. Since embedded systems applications such as avionics, automotive, or industrial automation are safety critical, it is very important to invent tools, and methodologies for safe and reliable system design. Much of the tools, and techniques deal with either the design of embedded platforms (hardware, networking, firmware etc), and software stack separately. The problem of the semantic gap between these two, as well as between models of computation used to capture semantics must be solved in order to design safer embedded systems.
  • Sysml Distilled: a Brief Guide to the Systems Modeling Language

    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.
  • Systems Engineering with Sysml/UML Morgan Kaufmann OMG Press

    Systems Engineering with Sysml/UML Morgan Kaufmann OMG Press

    Systems Engineering with SysML/UML Morgan Kaufmann OMG Press Morgan Kaufmann Publishers and the Object Management Group™ (OMG) have joined forces to publish a line of books addressing business and technical topics related to OMG’s large suite of software standards. OMG is an international, open membership, not-for-profi t computer industry consortium that was founded in 1989. The OMG creates standards for software used in government and corporate environments to enable interoperability and to forge common development environments that encourage the adoption and evolution of new technology. OMG members and its board of directors consist of representatives from a majority of the organizations that shape enterprise and Internet computing today. OMG’s modeling standards, including the Unifi ed Modeling Language™ (UML®) and Model Driven Architecture® (MDA), enable powerful visual design, execution and maintenance of software, and other processes—for example, IT Systems Modeling and Business Process Management. The middleware standards and profi les of the Object Management Group are based on the Common Object Request Broker Architecture® (CORBA) and support a wide variety of industries. More information about OMG can be found at http://www.omg.org/. Related Morgan Kaufmann OMG Press Titles UML 2 Certifi cation Guide: Fundamental and Intermediate Exams Tim Weilkiens and Bernd Oestereich Real-Life MDA: Solving Business Problems with Model Driven Architecture Michael Guttman and John Parodi Architecture Driven Modernization: A Series of Industry Case Studies Bill Ulrich Systems Engineering with SysML/UML Modeling, Analysis, Design Tim Weilkiens Acquisitions Editor: Tiffany Gasbarrini Publisher: Denise E. M. Penrose Publishing Services Manager: George Morrison Project Manager: Mónica González de Mendoza Assistant Editor: Matt Cater Production Assistant: Lianne Hong Cover Design: Dennis Schaefer Cover Image: © Masterfile (Royalty-Free Division) Morgan Kaufmann Publishers is an imprint of Eslsevier.
  • UML Cheatsheet

    UML Cheatsheet

    UML Cheatsheet Class Diagram Elements dependency multiplicity association Package::AbstractClass -Attribute : Type 1 -ClassAttribute : Type Parent Child parent child* +Operation(Arg:Type):Type #AbstractOperation * role Association generalization Class visibility 0..1 info <<interface>> Note ChildInfo SubClass Interface realizes qualified association dependency T 1 Interface ParameterizedClass Value key Implementor Operation(Arg: T) Operation2(): T Sequence Diagram Elements Object : Class Object2 object creation call(obj) new incoming message Object3 selfCall callback interaction frame return object destruction loop / alt / opt delete frame type {constraint} callUnderConstraint {alternative} callUnderAlternative (cc) 2006 Lou Franco - Some Rights Reserved - Attribution-NonCommercial-ShareAlike 2.5 (cc) 2006 Lou Franco - Some Rights Reserved - Attribution-NonCommercial-ShareAlike 2.5 http://creativecommons.org/licenses/by-nc-sa/2.5/ http://creativecommons.org/licenses/by-nc-sa/2.5/ Package Diagram Elements dependency Data View Model SQLServer Oracle Object Diagram Elements John : Child name = "John" parent: Parent Mary : Child name = "Mary" Use Case Diagram Elements system boundary actor 1 Library checkout 1 Membership <<include>> Common return start : Date Role Use Case Use Case renewal : Date * LendRecord Role Lendable due : Date <<include>> id 1 returned : Boolean newArrival : Boolean * LendRecord(lendable, member, date) calcDueDate(member): Date isDue() : Boolean Use Case Use Case renew(Date) * Role Book CD 1 Role * Member DVD (cc) 2006
  • What Is Package Diagram? How to Draw Package Diagram?

    What Is Package Diagram? How to Draw Package Diagram?

    Visual Paradigm Tutorial What is Package Diagram? How to Draw Package Diagram? What is Package Diagram? How to Draw Package Diagram? Written Date : July 29, 2014 At the beginning of the project, you only have a limited number of diagrams and everything is simple and beautiful. However, when time flies, more and more diagrams have been created and they start to become unmanageable. As a result, your project becomes hard to navigate and diagrams become difficult to locate when you want to review or make changes. How can we fix it up? We can make use of the Package Diagram to organize your diagrams into different packages. This helps you in categorizing your diagrams according to their natures, making them easier to be navigated and located. The Package Diagram also serves as a catalog for you to jump to the diagram that you want to look at. In this tutorial, we will show you how this can be done. Create Packages for your diagrams First, we need to have our packages ready. To create packages: 1. To create a Package Diagram, select Diagram > New from the toolbar. 2. In the New Diagram window, select Package Diagram and click Next. https://www.visual-paradigm.com/tutorials/packagediagram.jsp Page 1 of 11 Visual Paradigm Tutorial What is Package Diagram? How to Draw Package Diagram? 3. Enter Racing Game Packages as diagram name and click OK to confirm. 4. Click the Package button in diagram tool bar, then click on the blank area of the diagram to create the package. 5. Name the package as Race.
  • Getting Started with Sysml 3 This Chapter Provides an Introduction to Sysml and Guidance on How to Begin Modeling in Sysml

    Getting Started with Sysml 3 This Chapter Provides an Introduction to Sysml and Guidance on How to Begin Modeling in Sysml

    CHAPTER Getting Started with SysML 3 This chapter provides an introduction to SysML and guidance on how to begin modeling in SysML. The chapter provides a brief overview of SysML, and then introduces a simplified version of the language we refer to as SysML-Lite, along with a simplified example, and tool tips on how to capture the model in a typical modeling tool. This chapter also introduces a simplified model-based systems engineering (MBSE) method that is consistent with the systems engineering process described in Chapter 1, Section 1.2. The chapter finishes by describing some of the challenges involved in learning SysML and MBSE. 3.1 SYSML PURPOSE AND KEY FEATURES SysML1 is a general-purpose graphical modeling language that supports the analysis, specification, design, verification, and validation of complex systems. These systems may include hardware, soft- ware, data, personnel, procedures, facilities, and other elements of man-made and natural systems. The language is intended to help specify and architect systems and specify their components that can then be designed using other domain-specific languages such as UML for software design and VHDL and three-dimensional geometric modeling for hardware design. SysML is intended to facilitate the application of an MBSE approach to create a cohesive and consistent model of the system that yields the benefits described in Chapter 2, Section 2.1.2. SysML can represent the following aspects of systems, components, and other entities: n Structural composition, interconnection, and classification n Function-based, message-based, and state-based behavior n Constraints on the physical and performance properties n Allocations between behavior, structure, and constraints n Requirements and their relationship to other requirements, design elements, and test cases 3.2 SYSML DIAGRAM OVERVIEW SysML includes nine diagrams as shown in the diagram taxonomy in Figure 3.1.
  • Standardized Technical Architecture Modeling Conceptual and Design Level

    Standardized Technical Architecture Modeling Conceptual and Design Level

    Standardized Technical Architecture Modeling Conceptual and Design Level Version 1.0 March 2007 Copyright 2007 SAP AG. All Rights Reserved No part of this document may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
  • Towards Fixing Sketchy UML Models by Leveraging Textual Notations: Application to Real-Time Embedded Systems

    Towards Fixing Sketchy UML Models by Leveraging Textual Notations: Application to Real-Time Embedded Systems

    Towards Fixing Sketchy UML Models by Leveraging Textual Notations: Application to Real-Time Embedded Systems Fr´ed´ericJouault and J´er^ome Delatour PRES Universit´eNantes Angers Le Mans (UNAM) TRAME team, ESEO, Angers, France [email protected] Abstract. During the development of real-time embedded system, the use of UML models as blueprints is a common practice with a focus on un- derstandability rather than comprehensiveness. However, further in the development, these models must be completed in order to achieve the necessary validation and verification activities. They are typically per- formed by using several formal tools. Each tool needs models of the sys- tem at a given abstraction level, which are precise and complete enough wrt. how the tool processes them. If UML is appropriate for capturing multiple concerns, its multiple partial views without a global one in- crease the difficulty of locating inconsistency or incompleteness issues. Therefore, ensuring completeness is time consuming, fastidious, and er- ror prone. We propose an approach based on the use of a UML textual syntax closely aligned to its metamodel: tUML. An initial prototype is described, and examples are given. 1 Introduction Using sketchy models is common during software systems development. Such models (also called contemplative models) are just drawings that cannot be au- tomatically processed (e.g., transformed into code, or verified). In the use of such models as blueprints, the focus is on communication rather than on com- pleteness. The UML language is a good candidate for that kind of practice. It is primarily a graphical notation, and it offers a relatively large set of diagrams for representing various concerns.