DOCSLIB.ORG

Executable Models of Event Driven Systems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Databases and Information Systems IX 101 G. Arnicans et al. (Eds.) © 2016 The authors and IOS Press. This article is published online with Open Access by IOS Press and distributed under the terms of the Creative Commons Attribution Non-Commercial License 4.0 (CC BY-NC 4.0). doi:10.3233/978-1-61499-714-6-101 Executable Models of Event Driven Systems Janis BICEVSKISa,1, Zane BICEVSKAb and Girts KARNITISa a University of Latvia, Faculty of Computing, Riga, Latvia b DIVI Grupa Ltd, Riga, Latvia Abstract. The approach proposed in this paper is based on usage of Domain Specific Languages (DSL) and allows create executable information systems' models. It lets us apply principles of the Model Driven Development (MDD) to information systems development and use: bridges the gap between business and IT, take an exact specification of information system, up-to-date documentation etc. The practical experience proves the viability of the proposed approach. Keywords. Business Process Modeling, Model Driven Development, Domain Specific Language. 1. Introduction Model driven development (MDD) is a concept that offers a wide range of advantages for development, maintenance and use of information systems [1], [2]: (1) MDD provides a higher level of abstraction to describe the business process, and it leads to reduced efforts for error-prone description, meaningful validation and exhaustive testing, (2) MDD bridges the gap between business and IT, (3) MDD captures domain knowledge, (4) MDD results in software being less sensitive to changes in business requirements, (5) MDD provides up-to-date documentation. To reach the benefits of MDD, there should be used modelling languages and tools allowing accurately describe the system’s operation. It means the objects of high abstraction level should be transformable into source code of an information system. The most popular modelling languages like UML and BPMN are able to carry out the task only partially [3]. The languages use high abstraction concepts without linking them to specific domain objects and views. To achieve a full compliance, the objects of high abstraction level must be linked to the gradual detailing level up to the level of implementation. Many authors propose usage of Domain Specific Languages (DSL) as the solution. For instance, [4] argue that although UML is a useful modelling language, it is not an appropriate language for MDD, because UML is designed for documenting and not for programming. As a response to this the MDD community shifted focus to smaller, more specific languages [3], [5]). These DSLs focus on a specific problem area or even a business domain. That ultimately also defines the scope and applicability of these languages. They are by definition not meant to solve a generic issue and hence don’t attract a large 1 Corresponding author, Professor, University of Latvia, blwrd. Raina 19, LV-1586, Riga, Latvia, Email: [email protected] 102 J. Bicevskis et al. / Executable Models of Event Driven Systems developer community. The usage of DSLs in the MDD context leads to the requirement the models should be executable. And the challenges are still there - how to define business models and how to make them executable? The essential change is that models can now be directly used to drive software development. This paper describes a platform DIMOD for defining of DSLs ensuring executable models. The main focus of the research is devoted to so-called Event Driven Systems (EDS) where the data processing is caused by system’s external or internal events. The model of an EDS consists of widely-used modelling artefacts like data object, activity, data object’s state, event, time constraints etc. The proposed tools let you: to define a new DSL - artefacts and graphical representation of diagrams; to create an editor for editing graphical diagrams in the new DSL; to define semantics of the used concepts and the execution of models. The EDS represent a class of models where each instance is an executable model in a particular DSL. The models are executable either by interpreting the model, or by generating the source code from the model using a code generator. Wide range of data processing systems used in our daily life are examples of EDS – state information systems (population register, vehicle register etc.) as well as commercial solutions (e-shops, CRMs etc.). For example, the population register processes the data of citizens as data objects, and the personal life events (birth, education etc.) serve as events which change the states of data objects. The present work is a continuation of the previous research [6] extending it by implementation issues. The structure of the paper: the second section describes the purpose of the study – to create a DSL based approach for modelling of executable event–driven information systems. The third to fifth section describe the syntax, the semantics and the pragmatics of the proposed approach. The sixth section describes the related research. The conclusion contains summary about EDS and MDD approaches. 2. Models of Event-Driven Systems 2.1. Context In everyday life we use lot of EDS. The main goal of this research is to design a DSL- based modelling platform for describing of EDS to achieve a better appliance of MDD principles in development of information systems. 2.2. Business Process Modelling Environment DIMOD Usually business processes of EDS are described using some graphical DSL. As the EDS represents a wide class of information systems, the used DSLs can also be different. Hence it is advisable to use not only one specific graphical editor supporting one concrete DSL but to create your own editor for each used DSL. Currently there are several such platforms in use; one of them, called GrTP [7], is produced in Latvia. The business process graphical modelling environment DIMOD, used in this research, was derived from GrTP. Accordingly the DIMOD features are widely affected by those of GrTP. The business process modeling environment DIMOD is intended: J. Bicevskis et al. / Executable Models of Event Driven Systems 103 to define the DSL using meta-model that is stored into model’s repository. DSL parameters may be defined and modified using the separate configuration component Configurator [8]. Once the DSL is defined the corresponding modelling editor is created for the DSL automatically; to create and edit business process diagrams in the DSL. This is usually done by some highly qualified modelling experts in collaboration with domain experts (“clever users”); to check the business process models’ internal consistency. Both IT and domain experts are involved in it; to publish the created model/diagrams in WEB. It allows a wide range of users to use the business model diagrams without installation DIMOD. DIMOD also includes a feature to call APIs in predefined points for implementation of DSL specific semantics. It provides accessibility of specific functions or external sources as well as read/write access to model’s repository. 2.3. Characteristic Aspects of EDS Modelling Languages There are three views used to describe programming and/or modelling languages: Syntax of the modelling/ programming language. The syntax of modelling language is determined by the meta-model. A program or a model is considered to be syntactically correct if it meets all the conditions included in the meta-model. The syntactical correctness of the model/ program does not guarantee that the information according the model is processed exactly in that way which has been desired by the author. Therefore it is not sufficient to have only syntactically correct model to create an information system; it is necessary to define the semantics of the language. Semantics of the modelling/ programming language. The semantics of modelling language describes the meaning of concepts used in the language. The semantics can be defined in different ways – by axiomatic mathematical theory or by describing of an abstract machine explaining the language command execution and the meaning of language structures. In this paper the concept of abstract machine is used as it is well-known in the IT industry. Pragmatics of the modelling/ programming language. The pragmatics gives recommendations how the language should be applied and describes the methods. The pragmatics is based on practical considerations like language usage costs, development deadlines, availability of support, complexity of the language etc. The following sections will include analysis of all three aspects of EDS. 2.4. Ontological Model of EDS A modeling language should be defined in two levels: (1) firstly definitions of the ontological notions should be created, and then (2) the graphical representation is aligned to defined notions. The separation between the used concepts and their graphical depiction is the essential difference between the proposed approach and the traditional way used in many modelling languages where basic language elements are defined by graphical symbols representing basic concepts. The ontology of the EDS business process model proposed by the authors is shown in the Figure 1. The meta-model consists of a voluntary number of elements. Every 104 J. Bicevskis et al. / Executable Models of Event Driven Systems element has at least three predefined attributes – type, name, and identifier – and a voluntary number of additional attributes. Besides the five predefined types of elements the model may contain a voluntary number of additional types of elements. The predefined types are as follows: the object represents external donors/receivers of the information as well as sources/targets of data; some examples of such elements are messages, documents, records in data bases, legislative acts, etc. action represents activities with data objects, start/end of processes, execution of process’s steps, conditional execution, parallel activities, control of time restrictions, etc. state describes corteges of attributes’ values available for the data object to be processed. The corteges of values are equivalence classes with objects that are to be processed similarly during the specified process.
Recommended publications
  • 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.
  • Introduction to Systems Modeling Languages

    Introduction to Systems Modeling Languages

    Fundamentals of Systems Engineering Prof. Olivier L. de Weck, Mark Chodas, Narek Shougarian Session 3 System Modeling Languages 1 Reminder: A1 is due today ! 2 3 Overview Why Systems Modeling Languages? Ontology, Semantics and Syntax OPM – Object Process Methodology SySML – Systems Modeling Language Modelica What does it mean for Systems Engineering of today and tomorrow (MBSE)? 4 Exercise: Describe the “Mr. Sticky” System Work with a partner (5 min) Use your webex notepad/white board I will call on you randomly We will compare across student teams © source unknown. All rights reserved. This content is excluded from our Creative Commons license. For more information, see http://ocw.mit.edu/help/faq-fair-use/. 5 Why Systems Modeling Languages? Means for describing artifacts are traditionally as follows: Natural Language (English, French etc….) Graphical (Sketches and Drawings) These then typically get aggregated in “documents” Examples: Requirements Document, Drawing Package Technical Data Package (TDP) should contain all info needed to build and operate system Advantages of allowing an arbitrary description: Familiarity to creator of description Not-confining, promotes creativity Disadvantages of allowing an arbitrary description: Room for ambiguous interpretations and errors Difficult to update if there are changes Handoffs between SE lifecycle phases are discontinuous Uneven level of abstraction Large volume of information that exceeds human cognitive bandwidth Etc…. 6 System Modeling Languages Past efforts
  • UML Model to Fault Tree Model Transformation for Dependability

    UML Model to Fault Tree Model Transformation for Dependability

    ! ! UML Model to Fault Tree Model Transformation for Dependability Analysis ! ! ! ! ! by Zhao Zhao ! ! ! ! ! A thesis submitted to the Faculty of Graduate and Postdoctoral Affairs in partial fulfillment of the requirements for the degree of ! ! ! ! Master of Applied Science in Electrical and Computer Engineering ! ! ! ! ! Department of System and Computer Engineering Carleton University Ottawa, ON, Canada ! ! ! ! ! August 2014 ©Copyright2014, Zhao Zhao ! ! !I ACKNOWLEDGEMENT I would like to express my thank to all those who helped me during the writing of this thesis. My deepest gratitude goes first and foremost to my thesis supervisor, Prof. Dorina Petriu. It was only through her valuable supervision and patient guidance that I was able to complete all the work of this thesis. I would also like to thank my family, my father and my mother, and all my friends for their continuous support and encouragement. ! ! ! ! ! ! ! ! !II ABSTRACT Model-Driven Development (MDD) is a software development paradigm that has shifted the focus of software development from code to models. MDD’s emphasis on mod- els facilitates also the derivation of analysis models for different software non-functional properties (NFPs) from the software design models. Such analysis models are based on dif- ferent formalisms, and can be used to verify the NFPs of the software under development starting in the early lifecycle stages. This thesis proposes a model transformation to automatically generate Fault Tree models from UML models annotated with dependability annotations. Fault tree analysis is a top down deductive failure analysis model using both qualitative and quantitative analysis of undesired events of a system. It is used in safety and reliability engineering.
  • Executable Statemachines

    Executable Statemachines

    Enterprise Architect User Guide Series Executable StateMachines How to simulate State models? In Sparx Systems Enterprise Architect, Executable StateMachines provide complete language-specific implementations to rapidly generate, execute and simulate complex State models on multiple software products and platforms. Author: Sparx Systems Date: 21/12/2018 Version: 1.0 CREATED WITH Table of Contents Executable StateMachines 4 Executable StateMachine Artifact 9 Modeling Executable StateMachines 13 Code Generation for Executable StateMachines 25 Debugging Execution of Executable StateMachines 37 Execution and Simulation of Executable StateMachines 41 Example: Simulation Commands 43 Example: Simulation in HTML with JavaScript 58 CD Player 60 Regular Expression Parser 68 Entering a State 71 Example: Fork and Join 86 Example: Deferred Event Pattern 93 Example: Entry and Exit Points (Connection Point References) 103 Example: History Pseudostate 110 Example Executable StateMachine 125 User Guide - Executable StateMachines 21 December, 2018 Executable StateMachines Executable StateMachines provide a powerful means of rapidly generating, executing and simulating complex state models. In contrast to dynamic simulation of State Charts using Enterprise Architect's Simulation engine, Executable StateMachines provide a complete language-specific implementation that can form the behavioral 'engine' for multiple software products on multiple platforms. Visualization of the execution uses and integrates seamlessly with the Simulation capability. Evolution of the model now presents fewer coding challenges. The code generation, compilation and execution is taken care of by Enterprise Architect. For those having particular requirements, each language is provided with a set of code templates. Templates can be customized by you to tailor the generated code in any ways you see fit. These topics introduce you to the basics of modeling Executable StateMachines and tell you how to generate and simulate them.
  • Modeling Event-Based Communication in Component-Based Software Architectures for Performance Predictions

    Modeling Event-Based Communication in Component-Based Software Architectures for Performance Predictions

    Journal on Software and Systems Modeling manuscript No. (will be inserted by the editor) Modeling Event-based Communication in Component-based Software Architectures for Performance Predictions Christoph Rathfelder1, Benjamin Klatt1, Kai Sachs2, Samuel Kounev3? 1 FZI Research Center for Information Technology Karlsruhe, Germany frathfelder; [email protected] 2 SAP AG Walldorf, Germany [email protected] 3 Karlsruhe Institute of Technology (KIT) Karlsruhe, Germany [email protected] Received: date / Revised version: date Abstract Event-based communication is used in dif- 1 Introduction ferent domains including telecommunications, transporta- tion, and business information systems to build scal- The event-based communication paradigm is used in- able distributed systems. Such systems typically have creasingly often to build loosely-coupled distributed sys- stringent requirements for performance and scalability as tems in many different industry domains. The applica- they provide business and mission critical services. While tion areas of event-based systems range from distributed the use of event-based communication enables loosely- sensor-based systems up to large-scale business infor- coupled interactions between components and leads to mation systems [24]. Compared to synchronous com- improved system scalability, it makes it much harder for munication using, for example, remote procedure calls developers to estimate the system's behavior and perfor- (RPC), event-based communication among components mance under load due to the decoupling of components promises several benefits such as high scalability and ex- and control flow. In this paper, we present our approach tendability [25]. Being asynchronous in nature, it allows enabling the modeling and performance prediction of a send-and-forget approach, i.e., a component that sends event-based systems at the architecture level.
  • Tackling Design Patterns Chapter 10: UML State Diagrams Copyright C 2016 by Linda Marshall and Vreda Pieterse

    Tackling Design Patterns Chapter 10: UML State Diagrams Copyright C 2016 by Linda Marshall and Vreda Pieterse

    Department of Computer Science Tackling Design Patterns Chapter 10: UML State Diagrams Copyright c 2016 by Linda Marshall and Vreda Pieterse. All rights reserved. Contents 10.1 Introduction ................................. 2 10.2 Notational Elements ............................ 2 10.2.1 State Nodes . 2 10.2.2 Transition edges . 3 10.2.3 Control Nodes . 4 10.2.4 Actions . 5 10.2.5 Signals . 5 10.2.6 Composite States . 6 10.3 Examples ................................... 6 10.4 Exercises ................................... 7 References ....................................... 8 1 10.1 Introduction UML State diagrams are used to describe the behaviour of nontrivial objects. State diagrams are good for describing the behaviour of one object over time and are used to identify object attributes and to refine the behaviour description of an object. A state is a condition in which an object can be at some point during its lifetime, for some finite period of time [4]. State diagrams describe all the possible states a particular object can get into and how the objects state changes as a result of external events that reach the object [1]. The notation for state diagrams was first introduced by Harel [2], and then adopted by UML. 10.2 Notational Elements A UML State diagram is a graph in the mathematical sense of the word. It is a diagram consisting of nodes and edges. The nodes can assume a variety of forms each with specific meaning, while the edges are labeled arrows connecting these nodes. In Section 10.2.1 we discuss the basic nodes. The basic nodes are called state nodes. In Section 10.2.2 we discuss the syntax for the edges.
  • Case No COMP/M.4747 Œ IBM / TELELOGIC REGULATION (EC)

    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.
  • The UML Profile for Communicating Systems DRAFT October 18, 2004

    The UML Profile for Communicating Systems DRAFT October 18, 2004

    The UML Profile for Communicating Systems DRAFT October 18, 2004 Copyright © 1997-2003 ETSI. IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSIÂSRÂ000Â314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http://webapp.etsi.org/IPR/home.asp). All published ETSI deliverables shall include information which directs the reader to the above source of information. This Technical Specification (TS) has been produced by ETSI Technical Committee. How to Read this Specification 2 Acknowledgements 2 Overview 5 Methodological Aspects 5 Class Diagram 6 State Machine Diagram 7 Composite Structure Diagram 8 Relationship Between Diagrams 9 Overview 5 Active Class 5 Description 5 Attributes 5 Constraints 5 Semantics 5 Notation 5 Passive Class 5 Description 5 Attributes 5 Constraints 6 Semantics 6 Notation 6 Interface 6 Description 6 Constraints 6 Semantics 6 Notation 6 Signal 6 Description 6 Attributes 6 Semantics 6 Notation 7 Directed Association 7 Description 7 Attributes 7 Constraints 7 Semantics 7 Notation 7 Composition 7 Description 7 Attributes 7 xxx 7 Constraints 7 Semantics 8 UML Profile for Communicating Systems 1 Notation 8 Generalisation 8 Description 8 Attributes 8 Constraints 8 Semantics
  • Modelling and Transformation of Non-Functional Annotations

    Modelling and Transformation of Non-Functional Annotations

    Modelling and Transformation of Non-Functional Annotations Modelling and Transformation of Non-Functional Annotations Jorge Ibarra Delgado School of Computer Science University of St. Andrews June 24, 2015 1/32 Modelling and Transformation of Non-Functional Annotations Context Plan 1 Context Introduction Objectives 2 PlantNF 3 PlantNF-to-UPPAAL Transformation Tool 2/32 Modelling and Transformation of Non-Functional Annotations Context Introduction Modelling An abstract description of an artefact Key elements of a new or existing system Different stakeholders can verify and evaluate requirements helps enabling the reuse of components 3/32 Modelling and Transformation of Non-Functional Annotations Context Introduction Modelling Informal Methods Easy to learn and apply Too much expressiveness UML, boxes connected by lines 4/32 Modelling and Transformation of Non-Functional Annotations Context Introduction Modelling Informal Methods 4/32 Modelling and Transformation of Non-Functional Annotations Context Introduction Modelling Formal Methods Requires more intellectual effort Construction by applying semantical rules Event-B, PROMELA, UPPAAL, MoDeST 5/32 Modelling and Transformation of Non-Functional Annotations Context Introduction Modelling Formal Methods 5/32 Modelling and Transformation of Non-Functional Annotations Context Introduction Model Transformation Used to generate models of different kind Use of a target model which can be formally verified Examples of target models are Petri nets and timed automata 6/32 Our approach: Explore the use
  • Modeling with UML Chapter 2, Part 3 Activity Diagrams Activity Diagrams

    Modeling with UML Chapter 2, Part 3 Activity Diagrams Activity Diagrams

    Activity Diagrams • Describe the behavior of a system in terms of activities • Represent the sequencing and coordination of actions or steps, Modeling with UML similar to a control flow graph. Chapter 2, part 3 CS 4354 • Activity: Rounded rectangles represent actions called activities. Summer II 2015 • Edges between activities represent control flow. Jill Seaman ✦branching, looping, concurrency • Activity diagrams can be hierarchical: ✦A given activity in a rounded rectangle could be further detailed in its own separate activity diagram. 1 2 Activity Diagrams: Branching • Decisions (branches, alternates) ✦Branch Node: diamond with one incoming arrow two or more outgoing arrows. ✦Outgoing edges are labeled with guards (conditions in square brackets) that select that arrow when the condition is true. ✦[else] can be used as a guard. ✦Merge nodes (diamond with many incoming, one outgoing arrow) to mark the end of the branching. ✦The diamonds are sometimes omitted, but should be included for clarity. 3 4 Decision in the Handle Incident process. Activity Diagrams: Concurrency • Fork nodes and Join nodes (concurrency) ✦The fork is a line with one incoming edge and several outgoing edges. ✦Fork: denotes splitting control into multiple threads, representing the fact that each outgoing edge can be done in parallel. ✦The join is a line with many incoming edges and one outgoing edge. ✦Join: denotes synchronizing threads back into one (waiting until all of the incoming activities are completed before moving forward). ✦Fork and Join denote activities that may be done in any order (they are not required to be done concurrently). 5 6 Concurrency in incident management process.
  • Com.Telelogic.Rhapsody.Core

    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
  • Efficient Generation of Graphical Model Views Via Lazy Model-To-Text Transformation

    Efficient Generation of Graphical Model Views Via Lazy Model-To-Text Transformation

    This is a repository copy of Efficient Generation of Graphical Model Views via Lazy Model- to-Text Transformation. White Rose Research Online URL for this paper: https://eprints.whiterose.ac.uk/164209/ Version: Accepted Version Proceedings Paper: Kolovos, Dimitris orcid.org/0000-0002-1724-6563, De La Vega, Alfonso and Cooper, Justin (Accepted: 2020) Efficient Generation of Graphical Model Views via Lazy Model-to-Text Transformation. In: ACM/IEEE 23rd International Conference on Model Driven Engineering Languages and Systems (MODELS ’20). (In Press) Reuse Items deposited in White Rose Research Online are protected by copyright, with all rights reserved unless indicated otherwise. They may be downloaded and/or printed for private study, or other acts as permitted by national copyright laws. The publisher or other rights holders may allow further reproduction and re-use of the full text version. This is indicated by the licence information on the White Rose Research Online record for the item. Takedown If you consider content in White Rose Research Online to be in breach of UK law, please notify us by emailing [email protected] including the URL of the record and the reason for the withdrawal request. [email protected] https://eprints.whiterose.ac.uk/ Efficient Generation of Graphical Model Views via Lazy Model-to-Text Transformation Dimitris Kolovos Alfonso de la Vega Justin Cooper Department of Computer Science Department of Computer Science Department of Computer Science University of York University of York University of York York, UK York, UK York, UK [email protected] [email protected] [email protected] ABSTRACT transforming them into textual formats such as Graphviz, Plan- Producing graphical views from software and system models is tUML, SVG and HTML, which are subsequently rendered in an often desirable for communication and comprehension purposes, embedded browser.