DOCSLIB.ORG

Introduction to OMG's Unified Modeling Language (UML) a Little

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Introduction to OMG's Unified Modeling Language (UML) a Little 07.02.2006 Introduction to OMG's Unified Modeling Language (UML) Dominic Hillenbrand CES - Chair for Embedded Systems (Prof. Dr. Jörg Henkel) Department of Computer Science University of Karlsruhe Chair for Embedded Systems Universität Karlsruhe (TH) <your Name> WS 2005-06 Software Engineering for Embedded Systems A Little History Late 1960s: ¾ Emergence of OO programming languages (Simula-67 language) ¾ Appearance of first OOA&D methodologies 1980s and early 1990s: ¾ Smalltalk (1972) ¾ Many competing general development methods and modelling languages (over 50) Alan Curtis Kay ¾ The “methods wars” „The best way to predict the Excursion: Structured Analysis & future is to Design together with structured invent it." programming preceded the OO- paradigm! Chair for Embedded Systems Universität Karlsruhe (TH) Dominic Hillenbrand WS 2005-06 1 07.02.2006 Software Engineering for Embedded Systems How things got started The Three Amigos and their three prominent key methods (mid 1990s): ¾ Grady Booch (Booch ’93 “OO Analysis and Design) ¾ Rumbaugh (Object Modelling Technique) ¾ Ivar Jacobson (OO Software Engineering) Chair for Embedded Systems Universität Karlsruhe (TH) Dominic Hillenbrand WS 2005-06 Software Engineering for Embedded Systems More Background 1995: Rumbaugh, Booch and Jacobson join forces in Rational: ¾ Develop the (Rational) Unified Process ¾ Develop the Unified Modelling Language (UML) Object Management Group (OMG): ¾ not-for-profit consortium ¾ produces and maintains computer industry specifications ¾ flagship specification is the multi- platform Model Driven Architecture (MDA) Chair for Embedded Systems Universität Karlsruhe (TH) Dominic Hillenbrand WS 2005-06 2 07.02.2006 Software Engineering for Embedded Systems What is UML? UML is a language –semantics& syntax ¾ Not a methodology! (like RUP; Waterfall & Spiral-Model) UML can be used to ¾ specify ¾ visualize ¾ document software artifacts Built upon fundamental OO concepts “industry’s best” engineering practices 13 types of diagrams Usually textual specifications in automobile industry. Chair for Embedded Systems Universität Karlsruhe (TH) Dominic Hillenbrand WS 2005-06 Software Engineering for Embedded Systems Properties of UML Covers a very broad scope ¾ not all modeling capabilities are useful in all domains or applications! ¾ E.g. business vs. embedded modeling Structured in a modular fashion ¾ Ability to select only language parts of interest. ¾ User need only be concerned about language parts actually used. ¾ Great flexibility, but: • Tool fragmentation possible • Limited model interchange Chair for Embedded Systems Universität Karlsruhe (TH) Dominic Hillenbrand WS 2005-06 3 07.02.2006 Software Engineering for Embedded Systems Example: Language Parts State Machine language unit ¾ Specification of discrete event- driven behavior (often found in embedded systems) Activities language unit ¾ Specification of workflow behavior ¾ (very useful for business related modeling) Chair for Embedded Systems Universität Karlsruhe (TH) Dominic Hillenbrand WS 2005-06 Software Engineering for Embedded Systems UML – What for? Modeling (Designing before coding!) ¾ Analogous to blueprints in other engineering disciplines. Raising the Level of Abstraction Reverse-engineer old source code into a UML diagrams Model Driven Architecture (MDA) ¾ platform-independent (PIM) or platform- specific (PSM) ¾ OMG-standardized mappings to produce one or more Platform-Specific Models (PSMs) • E.g. target several RTOS systems Chair for Embedded Systems Universität Karlsruhe (TH) Dominic Hillenbrand WS 2005-06 4 07.02.2006 Software Engineering for Embedded Systems Excursion: OMG’s MDA Chair for Embedded Systems Universität Karlsruhe (TH) Dominic Hillenbrand WS 2005-06 Software Engineering for Embedded Systems What can you model with UML? Structure Diagrams include the Class Diagram, Object Diagram, Component Diagram, Composite Structure Diagram, Package Diagram, and Deployment Diagram. Behavior Diagrams include the Use Case Diagram (used by some methodologies during requirements gathering); Activity Diagram, and State Machine Diagram. Interaction Diagrams, all derived from the more general Behavior Diagram, include the Sequence Diagram, Communication Diagram, Timing Diagram, and Interaction Overview Diagram. Chair for Embedded Systems Universität Karlsruhe (TH) Dominic Hillenbrand WS 2005-06 5 07.02.2006 Software Engineering for Embedded Systems UML 2.0 UML 2.0 Superstructure stable since October 2004 The superstructure defines the ¾ six structure diagrams ¾ three behavior diagrams ¾ four interaction diagrams ¾ and the elements that comprise them Still work in progress: ¾ UML 2.0 Infrastructure ¾ UML 2.0 Object Constraint Language (OCL) ¾ UML 2.0 Diagram Interchange UML 1.5 is still the “current” version UML 2.0 is a major update Chair for Embedded Systems Universität Karlsruhe (TH) Dominic Hillenbrand WS 2005-06 Software Engineering for Embedded Systems UML and related Specifications Unified Modeling Language ¾ Superstructure (version 2.0, August 2005, 709 pages) • Defines user level constructs required for UML 2.0 ¾ Infrastructure (version 2.0, November 2004, 226 pages) ¾ Diagram Interchange (version 2.0, June 2005, 82 pages) ¾ OCL 2.0 Specification (version 2.0, June 2005, 185 pages) ¾ MOF 2.0/XMI Mapping Specification (version 2.1, September 2005, 120 pages) ¾ Meta Object Facility (MOF) Specification (version 1.4, April 2002, 358 pages) ¾ UML Profile for Schedulability, Performance, and Time Specification (version 1.1 , January 2005, 235 pages) Chair for Embedded Systems Universität Karlsruhe (TH) Dominic Hillenbrand WS 2005-06 6 07.02.2006 Software Engineering for Embedded Systems All finalized UML Specifications are available online - for free - http://www.omg.org/technology/documents/modeling _spec_catalog.htm Chair for Embedded Systems Universität Karlsruhe (TH) Dominic Hillenbrand WS 2005-06 Software Engineering for Embedded Systems UML Profiles and Related Specifications UML Profile for CORBA® UML Profile for CORBA Component Model (CCM) UML Profile for Enterprise Application Integration (EAI) UML Profile for Enterprise Distributed Object Computing (EDOC) UML Profile for QoS and Fault Tolerance UML Profile for Schedulability, Performance, and Time UML Testing Profile UML Human-Usable Textual Notation (HUTN) Hint: UML Profiles (subsets of UML tailored for specific purposes) Chair for Embedded Systems Universität Karlsruhe (TH) Dominic Hillenbrand WS 2005-06 7 07.02.2006 Software Engineering for Embedded Systems Hewlett-Packard 7irene Kennedy Carter I-Logix 88solutions Klasse Objecten IBM Adaptive KLOCwork Advanced Concepts IONA Center LLC Lockheed Martin Jaczone Alcatel MEGA International Kabira Technologies Artisan Mercury Computer WebGain Borland Motorola Ceira Technologies X-Change Technologies MSC.Software Commissariat à Gentleware L'Energie Atomique Northeastern University Intellicorp Computer Associates Oracle TNI-Valiosys Compuware Popkin Software DaimlerChrysler Unisys Proforma Domain Architects University of Embarcadero Project Technology Kaiserslautern Technologies Sims Associates Enea Business University of Kent SOFTEAM Software VERIMAG Sun Microsystems Telelogic Ericsson Syntropy Ltd. Thales Group France Telecom Fujitsu Fraunhofer FOKUS Chair for Embedded Systems Universität Karlsruhe (TH) Dominic Hillenbrand WS 2005-06 Software Engineering for Embedded Systems UML 2.0 Tools Altova UModel 2005, ARTiSAN's Real-time Studio, Borland Together 2006 for Eclipse, Computas' Metis with UML 2.0 Template, Embarcadero Describe, IBM Rational Software Architect and Modeler, I-Logix Rhapsody, MetaMatrix MetaBase Modeler, Mia Software (Sodifrance) Model-in-Action, No Magic's MagicDraw UML, OMONDO EclipseUML Studio, Pathfinder Solutions' PathMATE 5.2, Open Source StarUML sponsored by Plastic Software, Sparx Systems Enterprise Architect, Sun Microsystems' Java Studio Enterprise, Pattern Weaver Ver. 2.0 Technologic Arts Inc. (Japanese), Telelogic's TAU Developer and TAU Architect, Gentleware's Poseidon for UML, Visual Paradigm's Smart Development Environment tool series Chair for Embedded Systems Universität Karlsruhe (TH) Dominic Hillenbrand WS 2005-06 8 07.02.2006 Software Engineering for Embedded Systems Tools continued Risk: Overview may be lost – “Tool leads” ! Tool categories: ¾ Graphics Editors (e.g. PowerPoint) • Very limited support ¾ Notation specific editors (e.g. Visio, Dia) • Pre-built configurable “graphic blocks” ¾ Notation specific editors + semantic support (e.g. Omondo) • Code Generation ¾ Full blown CASE Tools (e.g. Rational Rose) • Focus on methodology and/or domain (e.g. real-systems) • Central Repository (Versioning) • XMI Data Exchange • Different views • MDA support Chair for Embedded Systems Universität Karlsruhe (TH) Dominic Hillenbrand WS 2005-06 Software Engineering for Embedded Systems Why care about UML internals? UML adoption in embedded real-time systems has increased Why? ¾ Software Engineering principles, tools, defined processes have reached the manufacturing companies. Those products are safety- critical! So, do not relay on intuition when you design or review Every line & box has a UML diagrams! formally defined meaning! Chair for Embedded Systems Universität Karlsruhe (TH) Dominic Hillenbrand WS 2005-06 9 07.02.2006 Software Engineering for Embedded Systems Infrastructure Architecture InfrastructureLibrary defines: ¾ a metalanguage core used to define a
Load more

Recommended publications
  • UML Tutorial: Part 1 -- Class Diagrams
    UML Tutorial: Part 1 -- Class Diagrams. Robert C. Martin My next several columns will be a running tutorial of UML. The 1.0 version of UML was released on the 13th of January, 1997. The 1.1 release should be out before the end of the year. This col- umn will track the progress of UML and present the issues that the three amigos (Grady Booch, Jim Rumbaugh, and Ivar Jacobson) are dealing with. Introduction UML stands for Unified Modeling Language. It represents a unification of the concepts and nota- tions presented by the three amigos in their respective books1. The goal is for UML to become a common language for creating models of object oriented computer software. In its current form UML is comprised of two major components: a Meta-model and a notation. In the future, some form of method or process may also be added to; or associated with, UML. The Meta-model UML is unique in that it has a standard data representation. This representation is called the meta- model. The meta-model is a description of UML in UML. It describes the objects, attributes, and relationships necessary to represent the concepts of UML within a software application. This provides CASE manufacturers with a standard and unambiguous way to represent UML models. Hopefully it will allow for easy transport of UML models between tools. It may also make it easier to write ancillary tools for browsing, summarizing, and modifying UML models. A deeper discussion of the metamodel is beyond the scope of this column. Interested readers can learn more about it by downloading the UML documents from the rational web site2.
    [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]
  • Using Telelogic DOORS and Microsoft Visio to Model and Visualize
    Using DOORS & Visio to Model and Visualize Complex Business Processes Bob Sherman - [email protected] [email protected] Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes - v1.0 © 2005 Galactic Solutions Group LLC – Authors: Bob Sherman ([email protected]), [email protected] 1 © Telelogic AB Agenda • The Unmet Need • The Solution – Strategy: Business Driven Application Lifecycle – Tactics: Business Modeling via DOORS & VISIO – Tactics: DOORS/VISIO Integration • Case Study Results Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes - v1.0 © 2005 Galactic Solutions Group LLC – Authors: Bob Sherman ([email protected]), [email protected] 2 © Telelogic AB Chronic IT Project Problems Top IT Project Problems • User/Stakeholder Engagement Outages • Unclear Objectives • Incomplete or Changing Requirements *Standish Group Chaos Studies Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes - v1.0 © 2005 Galactic Solutions Group LLC – Authors: Bob Sherman ([email protected]), [email protected] 3 © Telelogic AB Chronic IT Project Problems Rework • 35-65% of project budget *Standish Group spent on rework. • ~50% of rework is due to requirements errors * IEEE & University of Southern California Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes - v1.0 © 2005 Galactic Solutions Group LLC – Authors:
    [Show full text]
  • Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes
    Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes “The Business Driven Application Lifecycle” Bob Sherman Procter & Gamble Pharmaceuticals [email protected] Michael Sutherland Galactic Solutions Group, LLC [email protected] Prepared for the Telelogic 2005 User Group Conference, Americas & Asia/Pacific http://www.telelogic.com/news/usergroup/us2005/index.cfm 24 October 2005 Abstract: The fact that most Information Technology (IT) projects fail as a result of requirements management problems is common knowledge. What is not commonly recognized is that the widely haled “use case” and Object Oriented Analysis and Design (OOAD) phenomenon have resulted in little (if any) abatement of IT project failures. In fact, ten years after the advent of these methods, every major IT industry research group remains aligned on the fact that these projects are still failing at an alarming rate (less than a 30% success rate). Ironically, the popularity of use case and OOAD (e.g. UML) methods may be doing more harm than good by diverting our attention away from addressing the real root cause of IT project failures (when you have a new hammer, everything looks like a nail). This paper asserts that, the real root cause of IT project failures centers around the failure to map requirements to an accurate, precise, comprehensive, optimized business model. This argument will be supported by a using a brief recap of the history of use case and OOAD methods to identify differences between the problems these methods were intended to address and the challenges of today’s IT projects.
    [Show full text]
  • Course Structure & Syllabus of B.Tech Programme In
    Course Structure & Syllabus of B.Tech Programme in Information Technology (From the Session 2015-16) VSSUT, BURLA COURSE STRUCTURE FIRST YEAR (COMMON TO ALL BRANCHES) FIRST SEMESTER SECOND SEMESTER Contact Contact Theory Hrs. Theory Hrs. CR CR Course Course Subject L .T .P Subject L. T. P Code Code Mathematics-I 3 - 1 - 0 4 Mathematics-II 3 - 1 - 0 4 Physics/Chemistry 3 - 1 - 0 4 Chemistry/ Physics 3 - 1 - 0 4 Engineering Computer /CS15- CS15- Mechanics/Computer 3 - 1 - 0 4 Programming/Engineering 3 - 1 - 0 4 008 008/ Programming Mechanics Basic Electrical Engineering/ Basic Electronics/Basic 3 - 1 - 0 4 3 - 1 - 0 4 Basic Electronics Electrical Engineering English/Environmental Environmental 3 - 1 - 0 4 3 - 1 - 0 4 Studies Studies/English Sessionals Sessionals Physics Laboratory/ Chemistry Lab/ Physics 0 - 0 - 3 2 0 - 0 - 3 2 Chemistry Lab Laboratory Workshop-I/Engineering Engineering Drawing/ 0 - 0 - 3 2 0 - 0 - 3 2 Drawing Workshop-I Basic Electrical Engineering Basic Electronics Lab/Basic 0 - 0 - 3 2 0 - 0 - 3 2 Lab/Basic Electronics Lab Electrical Engineering Lab Business Communication Programming Lab/ /CS15- CS15- and Presentation Skill/ 0 - 0 - 3 2 Business Communication 0 - 0 - 3 2 984 984/ Programming Lab and Presentation Skill Total 15-5-15 28 Total 15-5-15 28 SECOND YEAR THIRD SEMESTER FOURTH SEMESTER Contact Contact Theory Hrs. Theory Hrs. CR CR Course Subject L .T .P Course Code Subject L. T. P Code Mathematics-III Computer Organization 3 - 1 - 0 4 CS15-007 and Architecture 3 - 1 - 0 4 Digital Systems 3 - 1 - 0 4 CS15-032 Theory
    [Show full text]
  • Generating Text with a Theorem Prover
    Generating Text with a Theorem Prover Ivfin I. Garibay School of Computer Science University of Central Florida Orlando, FL [email protected] Statechart Abstract ~ Theoreml The process of documenting designs is tedious and Content Planning Question tree + Tree transformations often error-prone. We discuss a system that au- , _?_T;_J Text Planning i Hypermxt~s implicittext planner(user)[ tomatically generates documentation for the single step transition behavior of Statecharts with particu- I.oa!izatioo Tomp,ato I lar focus on the correctness of the result in the sense that the document will present all and only the facts Hyper-t exit Document corresponding to the design being documented. Our approach is to translate the Statechart into Figure 1: Conceptual view Of the system. a propositional formula, then translate this formula into a natural language report. In the later transla- spective, this problem is distinguished in that the tion pragmatic effects arise due to the way the in- formal correctness of the document being generated formation is presented. Whereas such effects can be is crucial while felicitousness of the style is rela- difficult to quantify, we account for them within an tively unimportant. This leads us to a solution abstract framework by applying a series of transfor- based on formally verifiable theorem-proving tech- mations on the structure on the report while pre- niques which allows us to approach strategic NLG is- serving soundness and completeness of the logical sues within a highly abstract and conceptually clear content. The result is an automatically generated framework. hypertext report that is both logically correct and, The system takes a statechart in the form of a to a relatively high degree of confidence, free of mis- labeled directed graph and translates it into a set leading implicatures.
    [Show full text]
  • Early Verification and Validation in Model-Based Design
    ® ® Early Verification and Validation in Model-Based Design Amory Wakefield Technical Marketing The MathWorks © 2008 TheMathWorks, Inc. ® ® Introductions I spend most of my time: A. Creating specifications and requirements (systems and software) B. Implementation based on specification and requirements created by somebody else (generating, writing, deploying, debugging code) C. Both D. None of the above 2 ® ® Address the Entire Development Process RequirementsRequirements Design System V&V Requirements Validation Environment Robustness Testing Modeling Standards Checking Physical Components Component V&V Algorithms Design Verification Model Testing G e H t e Coverage and Test Generation G a a n e nd r e n - e r Property Proving e n a ra t te e e G Code Verification Digital Embedded Code Correctness Electronics Software Processor-In-The Loop Testing VHDL, Verilog C, C++ FPGA ASIC MCU DSP Integration Testing Software Integration Testing Integration Hardware-in-the-Loop Testing Hardware Connectivity Implement 3 ® ® Methods for Verification and Validation Traceability Requirements to model and code Model to code Modeling and Coding Standards Modeling standards checking Coding standards checking Testing Model testing in simulation Processor-in-the-loop Proving Proving design properties Proving code correctness 4 ® ® Increasing Confidence in Your Designs Confidence Traceability Modeling and Coding Model and Code Proving Design Standards Checking Testing Properties and Code Correctness Verification Method 5 ® ® Traceability System V&V Comp. V&V Integration Functional Requirements Design Environment Physical Components Tracing RequirementsÙModel Simulink Verification and Validation Algorithms H G e Tracing ModelÙSource Code G an t e e d a n ne - r e ra e r t n a e t Real-Time Workshop Embedded Coder e e G Digital Embedded Electronics Software Tracing RequirementsÙSource Code VHDL, Verilog C, C++ Simulink Verification and Validation FPGA ASIC MCU DSP Integration Implement 6 ® ® Tracing RequirementsÙModel System V&V Comp.
    [Show full text]
  • Case No COMP/M.4747 Œ IBM / TELELOGIC REGULATION (EC)
    EN This text is made available for information purposes only. A summary of this decision is published in all Community languages in the Official Journal of the European Union. Case No COMP/M.4747 – IBM / TELELOGIC Only the English text is authentic. REGULATION (EC) No 139/2004 MERGER PROCEDURE Article 8(1) Date: 05/03/2008 Brussels, 05/03/2008 C(2008) 823 final PUBLIC VERSION COMMISSION DECISION of 05/03/2008 declaring a concentration to be compatible with the common market and the EEA Agreement (Case No COMP/M.4747 - IBM/ TELELOGIC) COMMISSION DECISION of 05/03/2008 declaring a concentration to be compatible with the common market and the EEA Agreement (Case No COMP/M.4747 - IBM/ TELELOGIC) (Only the English text is authentic) (Text with EEA relevance) THE COMMISSION OF THE EUROPEAN COMMUNITIES, Having regard to the Treaty establishing the European Community, Having regard to the Agreement on the European Economic Area, and in particular Article 57 thereof, Having regard to Council Regulation (EC) No 139/2004 of 20 January 2004 on the control of concentrations between undertakings1, and in particular Article 8(1) thereof, Having regard to the Commission's decision of 3 October 2007 to initiate proceedings in this case, After consulting the Advisory Committee on Concentrations2, Having regard to the final report of the Hearing Officer in this case3, Whereas: 1 OJ L 24, 29.1.2004, p. 1 2 OJ C ...,...200. , p.... 3 OJ C ...,...200. , p.... 2 I. INTRODUCTION 1. On 29 August 2007, the Commission received a notification of a proposed concentration pursuant to Article 4 and following a referral pursuant to Article 4(5) of Council Regulation (EC) No 139/2004 ("the Merger Regulation") by which the undertaking International Business Machines Corporation ("IBM", USA) acquires within the meaning of Article 3(1)(b) of the Council Regulation control of the whole of the undertaking Telelogic AB ("Telelogic", Sweden) by way of a public bid which was announced on 11 June 2007.
    [Show full text]
  • Real Time UML
    Fr 5 January 22th-26th, 2007, Munich/Germany Real Time UML Bruce Powel Douglass Organized by: Lindlaustr. 2c, 53842 Troisdorf, Tel.: +49 (0)2241 2341-100, Fax.: +49 (0)2241 2341-199 www.oopconference.com RealReal--TimeTime UMLUML Bruce Powel Douglass, PhD Chief Evangelist Telelogic Systems and Software Modeling Division www.telelogic.com/modeling groups.yahoo.com/group/RT-UML 1 Real-Time UML © Telelogic AB Basics of UML • What is UML? – How do we capture requirements using UML? – How do we describe structure using UML? – How do we model communication using UML? – How do we describe behavior using UML? • The “Real-Time UML” Profile • The Harmony Process 2 Real-Time UML © Telelogic AB What is UML? 3 Real-Time UML © Telelogic AB What is UML? • Unified Modeling Language • Comprehensive full life-cycle 3rd Generation modeling language – Standardized in 1997 by the OMG – Created by a consortium of 12 companies from various domains – Telelogic/I-Logix a key contributor to the UML including the definition of behavioral modeling • Incorporates state of the art Software and Systems A&D concepts • Matches the growing complexity of real-time systems – Large scale systems, Networking, Web enabling, Data management • Extensible and configurable • Unprecedented inter-disciplinary market penetration – Used for both software and systems engineering • UML 2.0 is latest version (2.1 in process…) 4 Real-Time UML © Telelogic AB UML supports Key Technologies for Development Iterative Development Real-Time Frameworks Visual Modeling Automated Requirements-
    [Show full text]
  • Fakulta Informatiky UML Modeling Tools for Blind People Bakalářská
    Masarykova univerzita Fakulta informatiky UML modeling tools for blind people Bakalářská práce Lukáš Tyrychtr 2017 MASARYKOVA UNIVERZITA Fakulta informatiky ZADÁNÍ BAKALÁŘSKÉ PRÁCE Student: Lukáš Tyrychtr Program: Aplikovaná informatika Obor: Aplikovaná informatika Specializace: Bez specializace Garant oboru: prof. RNDr. Jiří Barnat, Ph.D. Vedoucí práce: Mgr. Dalibor Toth Katedra: Katedra počítačových systémů a komunikací Název práce: Nástroje pro UML modelování pro nevidomé Název práce anglicky: UML modeling tools for blind people Zadání: The thesis will focus on software engineering modeling tools for blind people, mainly at com•monly used models -UML and ERD (Plant UML, bachelor thesis of Bc. Mikulášek -Models of Structured Analysis for Blind Persons -2009). Student will evaluate identified tools and he will also try to contact another similar centers which cooperate in this domain (e.g. Karlsruhe Institute of Technology, Tsukuba University of Technology). The thesis will also contain Plant UML tool outputs evaluation in three categories -students of Software engineering at Faculty of Informatics, MU, Brno; lecturers of the same course; person without UML knowledge (e.g. customer) The thesis will contain short summary (2 standardized pages) of results in English (in case it will not be written in English). Literatura: ARLOW, Jim a Ila NEUSTADT. UML a unifikovaný proces vývoje aplikací : průvodce ana­lýzou a návrhem objektově orientovaného softwaru. Brno: Computer Press, 2003. xiii, 387. ISBN 807226947X. FOWLER, Martin a Kendall SCOTT. UML distilled : a brief guide to the standard object mode•ling language. 2nd ed. Boston: Addison-Wesley, 2000. xix, 186 s. ISBN 0-201-65783-X. Zadání bylo schváleno prostřednictvím IS MU. Prohlašuji, že tato práce je mým původním autorským dílem, které jsem vypracoval(a) samostatně.
    [Show full text]
  • The Unified Modeling Language Reference Manual
    The Unified Modeling Language Reference Manual The Unified Modeling Language Reference Manual James Rumbaugh Ivar Jacobson Grady Booch ADDISON-WESLEY An imprint of Addison Wesley Longman, Inc. Reading, Massachusetts • Harlow, England • Menlo Park, California Berkeley, California • Don Mills, Ontario • Sydney Bonn • Amsterdam • Tokyo • Mexico City Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book and Addison-Wesley was aware of a trademark claim, the designations have been printed in initial caps or all caps. Unified Modeling Language, UML, and the UML cube logo are trademarks of the Object Management Group. Some material in this book is derived from the Object Management Group UML Specification documentation. Used by permission of the Object Management Group. The authors and publisher have taken care in the preparation of this book but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. The publisher offers discounts on this book when ordered in quantity for special sales. For more information, please contact: AWL Direct Sales Addison Wesley Longman, Inc. One Jacob Way Reading, Massachusetts 01867 (781) 944-3700 Visit AW on the Web: www.awl.com/cseng/ Library of Congress Cataloging-in-Publication Data Rumbaugh, James. The unified modeling language reference manual / James Rumbaugh, Ivar Jacobson, Grady Booch. p. cm. — (The Addison-Wesley object technology series) Includes bibliographical references and index.
    [Show full text]
  • Software & Systems Process Engineering Metamodel
    Date : October 2007 Software & Systems Process Engineering Metamodel Specification, v2.0 (Beta 2) OMG Adopted Specification with change bars OMG Document Number: ptc/2007-08-07 Standard document URL: http://www.omg.org/spec/SPEM/2.0/Beta2/PDF Associated Schema Files: (original .zip files: ptc/07-08-08, ptc/07-08-09) http://www.omg.org/spec/SPEM/20071101/SPEM2-Process-Behavior-Content.merged.cmof http://www.omg.org/spec/SPEM/20071101/Infrastructure.cmof http://www.omg.org/spec/SPEM/20071101/LM.cmof http://www.omg.org/spec/SPEM/20071101/SoftwareProcessEngineeringMetamodel.cmof http://www.omg.org/spec/SPEM/20071101/SPEM2-Method-Content.cmof http://www.omg.org/spec/SPEM/20071101/SPEM2-Process-Behavior-Content.cmof http://www.omg.org/spec/SPEM/20071101/SPEM2.cmof http://www.omg.org/spec/SPEM/20071101/SPEM2.merged.cmof http://www.omg.org/spec/SPEM/20071101/SPEM2-Method-Content.merged.cmof http://www.omg.org/spec/SPEM/20071101/SPEM 2.0 Base Plugin Profile.xmi http://www.omg.org/spec/SPEM/20071101/SPEM 2.0 UML2 Profile.xmi Copyright © 2004-2007, Adaptive Ltd. Copyright © 2004-2007, Fujitsu Copyright © 2004-2007, Fundacion European Software Institute Copyright © 2004-2007, International Business Machines Corporations Copyright © 1997-2007, Object Management Group Copyright © 2004-2007, Softeam USE OF SPECIFICATION - TERMS, CONDITIONS & NOTICES The material in this document details an Object Management Group specification in accordance with the terms, conditions and notices set forth below. This document does not represent a commitment to implement any portion of this specification in any company's products. The information contained in this document is subject to change without notice.
    [Show full text]