DOCSLIB.ORG

Model to Code Generation of UML/Sysml Activity Diagrams for ARM Cortexm Mcus

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Model to Code Generation of UML/Sysml Activity Diagrams for ARM Cortexm Mcus Model to code generation of UML/SysML activity diagrams for ARM CortexM MCUs MohammadHossein AskariHemmat A Thesis in The Department of Electrical and Computer Engineering Presented in Partial Fulfillment of the Requirements for the Degree of Master Of Applied Science at Concordia University Montreal,´ Quebec,´ Canada April 2015 c MohammadHossein AskariHemmat, 2015 CONCORDIA UNIVERSITY School of Graduate Studies This is to certify that the thesis prepared By: MohammadHossein AskariHemmat Entitled: Model to code generation of UML/SysML activity diagrams for ARM CortexM MCUs and submitted in partial fulfilment of the requirements for the degree of Master of Applied Science (Electrical & Computer Engineering) complies with the regulations of this University and meets the accepted standards with respect to originality and quality. Signed by the final examining committee: Dr. Zahangir Kabir Chair Chair’s name Dr. Samar Abdi Examiner Examiner’s name Dr. Mohammad Mannan Examiner Examiner’s name Dr. Mounir Boukadoum Co-Supervisor Co-Supervisor’s name Dr. Otmane Ait Mohamed Supervisor Supervisor’s name Approved by Chair of the ECE Department 2015 Dean of Engineering ABSTRACT Model to code generation of UML/SysML activity diagrams for ARM CortexM MCUs MohammadHossein AskariHemmat The complexity in embedded systems has been increased in the last years. To over- come the system complexity various methodologies have been presented. Both in industry and academia, Model-Based design has been accepted to be the best solution to solve this problem. Model-Based Design is a technique for developing embedded system applications and cyber-physical systems based on a hierarchy of reusable design blocks. SysML/UML activ- ity diagrams are widely used for the modelling and analysis of complex systems, and they have become the de facto standard for software and embedded systems. Previously in our group, we formalized SysML activity diagrams by developing a calculus called New Activity Calculus (NuAC). In this work, we redefined NuAC terms to support RTX (Keil Real-Time Operating System) and present an automated SysML/UML activity diagram to RTX code generator, using mapping rules expressed in NuAC. To achieve this goal, we proposed a set of mapping rules that were used in mapping a SysM- L/UML activity diagram into a suitable code to be executed on ARM CortexM processor family. To automate the process of code generation, we presented a JAVA application that uses the proposed rules to automatically generate the RTX code from the input activity di- agram model. To demonstrate the capability of the developed tool, we use it to implement a train con- trol algorithm on an ARM Cortex-M4 device. The implemented model is run on the target platform and the correct functionality of the system is verified. iii To my loving family iv ACKNOWLEDGEMENTS First and foremost, I would like to thank the almighty ALLAH for his blessing to finish this research. I would like to express my deepest gratitude to my supervisor, Dr. Otmane Ait Mohamed, for his excellent guidance, caring, patience, and providing me with an excellent atmosphere for doing research. This thesis would not have been possible without his guidance and sup- port. I also want to thank Dr. Mounir Boukadoum, for co-supervising my research work and for giving his valuable comments on my research. I would like to thank all my fellow researchers and colleagues in Hardware Verification Group (HVG) at Concordia University. Without their guidance, support and continual en- couragements, this thesis would not have been possible. I would like to take this opportunity to thank Regroupement Stratgique en Microsystmes du Qubec (ReSMiQ) for their financial supports. Without their financial supports I would not have been able to continue my research work. Last but not least, I thank my family for their constant moral support and their prayers. They are the people who are closest to me and suffered most for my higher study in abroad. Their support was invaluable in completing this thesis. v TABLE OF CONTENTS LIST OF TABLES . viii LIST OF FIGURES . ix LIST OF ACRONYMS . xi 1 Introduction 1 1.1 Motivation . 1 1.2 Related Works . 2 1.2.1 MATLAB and Simulink based modeling . 2 1.2.2 Modeling based on AutoFocus3 . 3 1.2.3 Modeling and Analysis of Real Time and Embedded systems . 4 1.2.4 A Formal Verification Framework for BlueSpec System Verilog . 6 1.3 Proposed Methodology . 7 1.4 Thesis Contribution . 8 1.5 Thesis Outline . 9 2 Preliminaries 11 2.1 SysML and UML modeling languages . 11 2.1.1 Unified Modeling Language . 11 2.1.2 System Modeling Language . 13 2.1.3 Activity Diagrams . 15 2.1.4 SysML/UML based Modeling tools . 18 IBM Rational Rhapsody . 18 Enterprise Architecture . 19 Topcased . 19 2.2 Keil RTX RTOS . 20 2.2.1 RTX Threads . 22 2.3 Conclusion . 23 vi 3 Mapping Methodology 25 3.1 Implementation and Verification Framework . 25 3.2 SysML Activity Diagrams Formalization . 26 3.3 JAVA Application Unit . 34 3.4 Summary . 38 4 Application 40 4.1 BART Case Study . 40 4.1.1 BART system overview . 40 4.1.2 Simulation and Verification in AF3 . 48 4.1.3 Implementation . 52 4.2 Thread Management in JPEG Encoder . 56 4.3 Summary . 61 5 Conclusion and Future work 63 5.1 Conclusion . 63 5.2 Future Work . 64 A BART train controller code 65 Bibliography 70 vii LIST OF TABLES 2.1 Technical information of CMSIS-RTOS RTX[34] . 24 3.1 Formalization of SysML Activity Diagram Artifacts . 27 4.1 Dublin to Daly City track properties . 43 4.2 Worst Case Scenario Distance parameters . 48 4.3 Worst Case Scenario Distance calculations . 49 viii LIST OF FIGURES 1.1 Verification artifacts and activities in AF3 . 4 1.2 Architecture of MARTE profile [43] . 5 1.3 Probabilistic Decision in SysML activity diagram . 6 1.4 Join two thread in SysML/UML activity diagram . 8 1.5 Mapping flowchart . 8 2.1 The taxonomy of UML structure and behavior diagrams [29] . 12 2.2 Relation between SysML and UML [32] . 14 2.3 The taxonomy of SysML structure [30] . 15 2.4 Activity Diagram Syntax . 16 2.5 Probabilistic Decision in SysML activity diagram . 18 2.6 Thread State and State Transitions[34] . 23 3.1 SysML to RTX verification and implementation framework . 26 3.2 SysMLToRTX.java Java application . 34 3.3 Simplified SysMLToRTX java application Class diagram . 35 4.1 The map of the BART transit system . 41 4.2 The Dublin/Pleasa track in BART transit system. 42 4.3 BART system modeled in AF3 . 50 4.4 TrainController module in AF3 . 51 4.5 Overview of verification platform . 52 4.6 Communication Packet Format . 52 4.7 Abstracted Computer Station model . 53 4.8 Simulation of BART train control system . 54 4.9 Calculation result from ComputerStation algorithm implemented in the FRDM board . 54 ix 4.10 Train Position over time . 55 4.11 Train acceleration over time . 56 4.12 Train Velocity over time . 56 4.13 Zigzag ordering of JPEG image components[47] . 58 4.14 JPEG Encoder pipeline . 58 4.15 Not scheduled JPEG encoder . 59 4.16 Not scheduled JPEG encoder output log file . 60 4.17 A scheduled JPEG encoder algorithm . 61 4.18 A scheduled JPEG encoder algorithm Output log . 62 x LIST OF ACRONYMS AATC Advance Automatic Train Control AF3 AutoFOCUS3 BART Bay Area Rapid Transit BSV Bluespec SystemVerilog CMSIS Cortex Microcontroller Software Interface Standard DCT Discrete Cosine Transform ESL Electronic System Level INCOSE International Council on Systems Engineering RTX Real Time eXecutive UML Unified Modeling Language MBSE Model Based System Engineers NuAC New Activity Calculus OMG Object Management Group OMT Object Modeling Technique PRISM PRobabilistIc Symbolic Model checker RTOS Real-Time Operating System SysML Systems Modeling Language WCSD Worst Case Scenario Distance xi Chapter 1 Introduction 1.1 Motivation The complexity in embedded systems has been increased in the last years. New heteroge- neous systems which combine different domains are more common. Aircrafts, automobiles, cell phones, medical equipment is an example where domains such as electronics, commu- nication, software, mechanics, physics, mathematics and medicine are part of the systems development today. The International Council on Systems Engineering (INCOSE)[1] iden- tified Model-Based Systems Engineering (MBSE) [2] as the key driver for effective and efficient system development in the future. Model-Based Design [3] is a technique for embedded system applications that reduces system complexity by creating a hierarchy of individual design blocks. OMG(Object Management Group) Systems Modeling Language (SysML) [4] was developed in order to support effective communication among the parties involved by means of a standardized graphical notation. SysML [5] is a standard modeling language used for system applications. It reuses a subset of UML packages [6]. Mainly, it covers four aspects of system modeling: structure, behavior, requirement, and parametric diagrams. SysML is composed of several diagram types (use case, activity, sequence and so on). Particularly, SysML activity diagrams[9] are graphical representations of work-flows of 1 step-wise activities and actions with support for choice, iteration and concurrency. In order to execute the SysML model in an embedded hardware platform, the SysML model needs to be mapped to low level C code. In this thesis, our main goal is to generate an executable C code from a SysML activity diagram model. Particularly, we are interested to automatically generate code for ARM CortexM processor family [10] from a SysML activity diagram model. To achieve this goal, a set of mapping rules are proposed that maps a SysML activity diagram into a correct code to be executed on ARM CortexM processor family.
Load more

Recommended publications
  • 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]
  • 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]
  • 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]
  • Umple Tutorial: Models 2020
    Umple Tutorial: Models 2020 Timothy C. Lethbridge, I.S.P, P.Eng. University of Ottawa, Canada Timothy.Lethbridge@ uottawa.ca http://www.umple.org Umple: Simple, Ample, UML Programming Language Open source textual modeling tool and code generator • Adds modeling to Java,. C++, PHP • A sample of features —Referential integrity on associations —Code generation for patterns —Blending of conventional code with models —Infinitely nested state machines, with concurrency —Separation of concerns for models: mixins, traits, mixsets, aspects Tools • Command line compiler • Web-based tool (UmpleOnline) for demos and education • Plugins for Eclipse and other tools Models T3 Tutorial: Umple - October 2020 2 What Are we Going to Learn About in This Tutorial? What Will You Be Able To Do? • Modeling using class diagrams —AttriButes, Associations, Methods, Patterns, Constraints • Modeling using state diagrams —States, Events, Transitions, Guards, Nesting, Actions, Activities —Concurrency • Separation of Concerns in Models —Mixins, Traits, Aspects, Mixsets • Practice with a examples focusing on state machines and product lines • Building a complete system in Umple Models T3 Tutorial: Umple - October 2020 3 What Technology Will You Need? As a minimum: Any web browser. For a richer command-line experience • A computer (laptop) with Java 8-14 JDK • Mac and Linux are the easiest platforms, but Windows also will work • Download Umple Jar at http://dl.umple.org You can also run Umple in Docker: http://docker.umple.org Models T3 Tutorial: Umple - October 2020 4
    [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]
  • Sketching Process Models by Mining Participant Stories
    Sketching Process Models by Mining Participant Stories Ana Ivanchikj and Cesare Pautasso Software Institute, USI, Lugano, Switzerland [email protected] Abstract. Producing initial process models currently requires gather- ing knowledge from multiple process participants and using modeling tools to produce a visual representation. With traditional tools this can require significant effort and thus delay the feedback cycle where the initial model is validated and refined based on participants' feedback. In this paper we propose a novel approach for process model sketching by applying existing process mining techniques to a sample process log obtained directly from the process participants. To that end, we spec- ify a simple natural language-like domain-specific language to represent process traces or fragments of process traces. We also illustrate the ar- chitecture of a live modeling tool, the Sketch Miner, implementing the proposed approach. The tool produces a draft visual representation of the control flow which is updated in real-time as the traces are written down. The draft model generated by the tool can later be refined and completed by the business analysts using traditional tools. Keywords: Draft Process Model · Process Mining · Process Require- ments · Textual Modelling DSL 1 Introduction One of the identified challenges of business process management in a recent sur- vey is the involvement of people with different skills and background [1], such as process participants with business domain knowledge, the business analysts with process modelling knowledge, and the software engineers with IT background. In the requirements gathering phase for the implementation of a new process in Process Aware Information Systems (PAIS), or when trying to model/improve existing processes, the people with detailed knowledge about the AS-IS or TO- BE business process are the participants in the process.
    [Show full text]
  • Measuring and Understanding Consistency at Facebook
    Existential Consistency: Measuring and Understanding Consistency at Facebook Haonan Lu∗†, Kaushik Veeraraghavan†, Philippe Ajoux†, Jim Hunt†, Yee Jiun Song†, Wendy Tobagus†, Sanjeev Kumar†, Wyatt Lloyd∗† ∗University of Southern California, †Facebook, Inc. Abstract 1. Introduction Replicated storage for large Web services faces a trade-off Replicated storage is an important component of large Web between stronger forms of consistency and higher perfor- services and the consistency model it provides determines mance properties. Stronger consistency prevents anomalies, the guarantees for operations upon it. The guarantees range i.e., unexpected behavior visible to users, and reduces pro- from eventual consistency, which ensures replicas eventu- gramming complexity. There is much recent work on im- ally agree on the value of data items after receiving the same proving the performance properties of systems with stronger set of updates to strict serializability [12] that ensures trans- consistency, yet the flip-side of this trade-off remains elu- actional isolation and external consistency [25]. Stronger sively hard to quantify. To the best of our knowledge, no consistency guarantees often require heavier-weight imple- prior work does so for a large, production Web service. mentations that increase latency and/or decrease through- We use measurement and analysis of requests to Face- put [5, 13, 26, 37]. As a result, many production systems [14, book’s TAO system to quantify how often anomalies happen 15, 19, 24, 32, 42, 46] choose weaker forms of consistency in practice, i.e., when results returned by eventually consis- in order to provide low latency and high throughput. tent TAO differ from what is allowed by stronger consistency These weaker forms of consistency have two primary models.
    [Show full text]
  • Activity Diagrams & State Machines
    2IW80 Software specification and architecture Activity diagrams & State machines Alexander Serebrenik This week sources Slides by Site by David Meredith, Kirill Fakhroutdinov Aalborg University, DK GE Healthcare, USA Before we start… True or False? 1. A web server can be an actor in a use case diagram. 2. Guarantee is an action that initiates the use case. 3. Use case “Assign seat” includes the use case “Assign window seat”. 4. Generalization is represented by an arrow with a hollow triangle head. 5. Every use case might involve only one actor. / SET / W&I 24-2-2014 PAGE 2 Before we start… T, unless it is a part of the system True or False? you want to model 1. A web server can be an actor in a use case diagram. Guarantee is a postcondition. An action that initiates the use case is called “trigger”. 2. Guarantee is an action that initiates the use case. 3. Use case “Assign seat” includes the use case “Assign window seat”. 4. Generalization is represented by an arrow with a hollow triangle head. 5. Every use case might involve only one actor. / SET / W&I 24-2-2014 PAGE 3 Before we start… True or False? 1. A web server can be an actor in a use case diagram. 2. GuaranteeNo, the correct is an relationaction that here initiates is extension the use (<<extend>>); case. <<include>> suggests that “Assign window seat” is always called whenever “Assign seat” is executed. 3. Use case “Assign seat” includes the use case “Assign window seat”. 4. Generalization is represented by an arrow with a hollow triangle head.
    [Show full text]
  • Com.Telelogic.Rhapsody.Core
    com.telelogic.rhapsody.core Package Class Use Tree Serialized Deprecated Index Help PREV PACKAGE NEXT PACKAGE FRAMES NO FRAMES All Classes Package com.telelogic.rhapsody.core Interface Summary The IRPAcceptEventAction interface represents Accept Event IRPAcceptEventAction Action elements in a statechart or activity diagram. The IRPAcceptTimeEvent interface represents Accept Time Event IRPAcceptTimeEvent elements in activity diagrams and statecharts. The IRPAction interface represents the action defined for a IRPAction transition in a statechart. The IRPActionBlock interface represents action blocks in IRPActionBlock sequence diagrams. The IRPActivityDiagram interface represents activity diagrams in IRPActivityDiagram Rational Rhapsody models. IRPActor The IRPActor interface represents actors in Rhapsody models. The IRPAnnotation interface represents the different types of IRPAnnotation annotations you can add to your model - notes, comments, constraints, and requirements. The IRPApplication interface represents the Rhapsody application, IRPApplication and its methods reflect many of the commands that you can access from the Rhapsody menu bar. The IRPArgument interface represents an argument of an IRPArgument operation or an event. IRPASCIIFile The IRPAssociationClass interface represents association classes IRPAssociationClass in Rational Rhapsody models. The IRPAssociationRole interface represents the association roles IRPAssociationRole that link objects in communication diagrams. The IRPAttribute interface represents attributes of
    [Show full text]
  • OMG Systems Modeling Language (OMG Sysml™) Tutorial
    OMG Systems Modeling Language (OMG SysML™) Tutorial Based on the INCOSE tutorial available on the web http://www.uml-sysml.org/documentation/sysml-tutorial-incose-2.2mo and the book “SysML for Systems Engineers” SysML as an OMG standard • Specification status Adopted by OMG in May ’06 • Current Specification v1.2 released in June 2010 • The INCOSE tutorial is based on the OMG SysML specification v 1.0 (2007-09-01) • The tutorial, the specifications, papers, and info on tools can be found on the OMG SysML Website at http://www.omg.org/spec/SysML/ • The examples are based on the Topcased modeling tool (open source and Eclipse-based, available at www.topcased.org) Motivation, Objectives and Audience • At the end of this tutorial, you should have an understanding of: – Motivation of model-based systems engineering approach – SysML diagrams and language concepts – How to apply SysML as part of a model-based SE process – The course must be supplemented by modeling practice. • 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 What is Systems Engineering • Systems Engineering is a discipline that concentrates on the design and application of the whole (system) as distinct from the parts. It involves looking at the problem in its entirety, taking into account all the facets and all the variables. ( Federal Aviation Agency FAA-USA, Systems Engineering Manual, Definition by Simon Ramo, 2006 ) • Systems Engineering is an iterative process of top-down synthesis, development and operation of a real-world system that satisfies, in a near-optimal manner, the full range of requirements for the system.
    [Show full text]