DOCSLIB.ORG

Inconsistency Management in Model-Driven Engineering

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Inconsistency Management in Model-Driven Engineering FACULTY OF SCIENCE Department of Computer Science System and Software Engineering Lab Inconsistency Management in Model-Driven Engineering An Approach using Description Logics Ragnhild Van Der Straeten A dissertation submitted in partial fulfilment of the requirements of the degree of Doctor in Science September 2005 Advisors: Prof. Dr. Viviane Jonckers, Prof. Dr. Tom Mens FACULTEIT VAN DE WETENSCHAPPEN Vakgroep Informatica Laboratorium voor Systeem en Software Engineering Inconsistentiebeheer in modelgebaseerde ontwikkeling Een benadering gebruikmakend van Description Logics Ragnhild Van Der Straeten Proefschrift ingediend met het oog op het behalen van de graad van Doctor in de Wetenschappen September 2005 Promotoren: Prof. Dr. Viviane Jonckers, Prof. Dr. Tom Mens Abstract Model-driven engineering (MDE) is an approach to software development where the pri- mary focus is on models, as opposed to source code. Models are built representing different views on a software system. Models can be refined, evolved into a new version, and can be used to generate executable code. The ultimate goal is to raise the level of abstraction, and to develop and evolve complex software systems by manipulating models only. The ma- nipulation of models is achieved by means of model transformation. Because model-driven engineering is still in its infancy, there is a need for sophisticated formalisms, techniques and associated tools supporting model development, evolution and transformation. The main concern of the research presented in this dissertation, is the definition, detec- tion and resolution of model inconsistencies. We focus on two aspects of these activities: defining and resolving inconsistencies, and a feasibility study of Description Logics (DLs) as a formalism for supporting these activities. Since the Unified Modeling Language (UML) is the generally accepted object-oriented modelling language, it ought to play an essential role in MDE. A software design is typically specified as a collection of different UML diagrams. Because different aspects of the software system are covered by different UML diagrams, there is an inherent risk that the overall specification of the system is inconsistent. Also model transformations, such as (arbitrary) model evolutions, can transform a model into an inconsistent state. Unfortunately, current- day UML CASE tools provide poor support for managing inconsistencies between (evolving) UML models. Inconsistency management is a complex process consisting of different activities. It is a well-studied process that is also well-known within software engineering. However, in the UML context, little research has been done taking into account a wide range of inconsistencies over different kinds of UML diagrams. Inconsistency management in the UML context, is quite complicated due to several reasons. The most obvious reasons are the missing formal semantics for the UML and the UML being a general purpose language that can be applied to several application domains and in several software development processes. To be able to define the occurrence of UML model inconsistencies precisely and unam- biguously, there is first of all a need to formalise the UML’s abstract syntax and concepts. A first contribution is to formalise an important fragment of the abstract syntax. The stud- ied UML fragment allows the specification of the static structure of an application and the specification of behaviour of individual objects and the possible interactions between objects. As a second contribution, we propose a classification of inconsistencies. The defi- nitions of these inconsistencies are based on our formalisation. Inconsistency management, as a process, also includes the activity of resolving inconsistencies. Different resolution strategies are known in literature. The resolution of inconsistencies gives rise to some par- ticular challenges. We give an overview of these challenges in the context of our classified inconsistencies. From the formalisation of a fragment of the UML abstract syntax, from our classification of inconsistencies, from the definition of different inconsistencies and from the different resolution strategies, we distil a set of key criteria. The requirements for each of these criteria can be used to evaluate a formalism and tool support supporting the detection and resolution of inconsistencies. Through the second focus of this dissertation, we discovered that Description Logics (DLs) and DL systems are suited (or can be made suited) for the detection and resolution of inconsistencies on a fairly high-level of model abstraction. DL is a two-variable fragment of first-order predicate logic, defining a family of logic languages, offering a classification task based on the subconcept-superconcept relationship. DLs are very suited for reasoning about hierarchies and about the satisfiability of knowledge bases. Different DL systems are developed and can be used to validate this formalism for the purpose of inconsistency detection and resolution. DLs are validated against our key criteria in three successive steps. First, we investigate to which extent it is possible to encode the fragment under study of the abstract syntax of the UML. We also answer the question if DLs can be used as a semantic domain for some possible semantics for UML diagrams. Second, we show how inconsistencies can be detected using this formalism. Finally, we investigate if it is possible to resolve inconsistencies using DLs and the capabilities of state-of-the-art DL systems. Model transformations are considered to be the heart and soul of MDE. One partic- ular kind of model transformation and evolution is model refactoring. Model refactorings restructure models as opposed to source code refactorings, which restructure source code and are well-known and well-studied. Model refactorings preserve behaviour. We show how some of the classified inconsistencies correspond to behaviour preserving properties that can be expressed between a UML model and its refactored version. A second idea about model refactorings introduced in this dissertation, is to use inconsistency detection and resolution techniques for supporting a software engineer in executing model refactorings. Our ideas are illustrated and validated on a simplified, yet complex enough, set of models of an Automatic Teller Machine (ATM) simulation application using a prototype tool, called RACOoN. This tool is integrated in a commercial UML CASE tool using the latter’s built-in plugin mechanism. Samenvatting Modelgebaseerde ontwikkeling is een bepaalde benadering van software ontwikkeling waarbij de nadruk ligt op modellen in plaats van op broncode. Modellen worden gebouwd vanuit een bepaalde kijk op het software systeem. Modellen kunnen verfijnd worden, evolueren naar nieuwe versies en kunnen, bijvoorbeeld, gebruikt worden om broncode te genereren. Het ultieme doel van modelgebaseerde ontwikkeling is om het abstractieniveau te verhogen en om complexe software systemen te ontwikkelen en te laten evolueren enkel door modelma- nipulatie. Deze modelmanipulaties worden bekomen door middel van modeltransformaties. Modelgebaseerde ontwikkeling staat echter nog in zijn kinderschoenen waardoor er een nood is aan gesofisticeerde formalismen, technieken en geassocieerde programma-ondersteuning voor het ontwerpen van modellen, de evolutie van modellen en transformatie van modellen. De hoofdinteresse van het onderzoek dat gepresenteerd wordt in deze thesis, is de defini- tie, detectie en resolutie van model inconsistenties. De aandacht wordt gevestigd op twee aspecten van deze activiteiten, nl., de definitie van inconsistenties en resolutie strategie¨en, en een onderzoek naar de haalbaarheid van “Description Logics” (DLs) ter ondersteuning van deze activiteiten. Vermits de “Unified Modeling Language” (UML) de standaard objectgeori¨enteerde mod- elleertaal is, zou het een belangrijke rol moeten spelen in modelgebaseerde ontwikkeling. Een software ontwerp is meestal een collectie van UML diagrammen, waardoor er een in- herent risico is dat de globale specificatie van het systeem inconsistent is. Modeltransfor- maties, zoals bijvoorbeeld een willekeurige evolutie van het model, kunnen inconsistenties veroorzaken. De bestaande UML ondersteunende programma’s bieden echter onvoldoende ondersteuning voor het beheren van inconsistenties tussen (evoluerende) UML modellen. Inconsistentiebeheer is een complex proces bestaande uit verschillende activiteiten. Het is een goed bestudeerd proces dat bekend is binnen software ontwikkeling. In de context van UML is er nog niet zo veel onderzoek gedaan naar verschillende soorten inconsistenties over een aantal overlappende UML diagrammen. En dit omwille van een aantal redenen. De belangrijkste zijn: UML heeft geen formele semantiek, daarbovenop kan ´e´en enkel diagram op verschillende manieren ge¨ınterpreteerd worden en UML is een taal voor algemeen ge- bruik in de zin dat ze kan gebruikt worden voor verschillende applicatiedomeinen en binnen verschillende software ontwikkelingsprocessen. Om UML model inconsistenties op een precieze manier te kunnen defini¨eren,hebben we nood aan een formalisatie van de abstracte syntax van UML en een mogelijke semantiek. Een eerste bijdrage van dit werk is de formalisatie van een belangrijk deel van de abstracte syntax van UML. Dit deel van UML laat toe om de statische structuur van een applicatie te specificeren en eveneens de specificatie van het gedrag van een bepaald object en de mogelijke interacties tussen objecten. Een tweede bijdrage van dit werk bestaat
Load more

Recommended publications
  • EB GUIDE Documentation Version 6.1.0.101778 EB GUIDE Documentation
    EB GUIDE documentation Version 6.1.0.101778 EB GUIDE documentation Elektrobit Automotive GmbH Am Wolfsmantel 46 D-91058 Erlangen GERMANY Phone: +49 9131 7701-0 Fax: +49 9131 7701-6333 http://www.elektrobit.com Legal notice Confidential and proprietary information. ALL RIGHTS RESERVED. No part of this publication may be copied in any form, by photocopy, microfilm, retrieval system, or by any other means now known or hereafter invented without the prior written permission of Elektrobit Automotive GmbH. ProOSEK®, tresos®, and street director® are registered trademarks of Elektrobit Automotive GmbH. All brand names, trademarks and registered trademarks are property of their rightful owners and are used only for description. Copyright 2015, Elektrobit Automotive GmbH. Page 2 of 324 EB GUIDE documentation Table of Contents 1. About this documentation ................................................................................................................ 15 1.1. Target audiences of the user documentation ......................................................................... 15 1.1.1. Modelers .................................................................................................................. 15 1.1.2. System integrators .................................................................................................... 16 1.1.3. Application developers ............................................................................................... 16 1.1.4. Extension developers ...............................................................................................
    [Show full text]
  • UML 2 Toolkit, Penker Has Also Collaborated with Hans- Erik Eriksson on Business Modeling with UML: Business Practices at Work
    UML™ 2 Toolkit Hans-Erik Eriksson Magnus Penker Brian Lyons David Fado UML™ 2 Toolkit UML™ 2 Toolkit Hans-Erik Eriksson Magnus Penker Brian Lyons David Fado Publisher: Joe Wikert Executive Editor: Bob Elliott Development Editor: Kevin Kent Editorial Manager: Kathryn Malm Production Editor: Pamela Hanley Permissions Editors: Carmen Krikorian, Laura Moss Media Development Specialist: Travis Silvers Text Design & Composition: Wiley Composition Services Copyright 2004 by Hans-Erik Eriksson, Magnus Penker, Brian Lyons, and David Fado. All rights reserved. Published by Wiley Publishing, Inc., Indianapolis, Indiana Published simultaneously in Canada No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning, or otherwise, except as permitted under Section 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, Inc., 222 Rose- wood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8700. Requests to the Pub- lisher for permission should be addressed to the Legal Department, Wiley Publishing, Inc., 10475 Crosspoint Blvd., Indianapolis, IN 46256, (317) 572-3447, fax (317) 572-4447, E-mail: [email protected]. Limit of Liability/Disclaimer of Warranty: While the publisher and author have used their best efforts in preparing this book, they make no representations or warranties with respect to the accuracy or completeness of the contents of this book and specifically disclaim any implied warranties of merchantability or fitness for a particular purpose.
    [Show full text]
  • UML Profile for Communicating Systems a New UML Profile for the Specification and Description of Internet Communication and Signaling Protocols
    UML Profile for Communicating Systems A New UML Profile for the Specification and Description of Internet Communication and Signaling Protocols Dissertation zur Erlangung des Doktorgrades der Mathematisch-Naturwissenschaftlichen Fakultäten der Georg-August-Universität zu Göttingen vorgelegt von Constantin Werner aus Salzgitter-Bad Göttingen 2006 D7 Referent: Prof. Dr. Dieter Hogrefe Korreferent: Prof. Dr. Jens Grabowski Tag der mündlichen Prüfung: 30.10.2006 ii Abstract This thesis presents a new Unified Modeling Language 2 (UML) profile for communicating systems. It is developed for the unambiguous, executable specification and description of communication and signaling protocols for the Internet. This profile allows to analyze, simulate and validate a communication protocol specification in the UML before its implementation. This profile is driven by the experience and intelligibility of the Specification and Description Language (SDL) for telecommunication protocol engineering. However, as shown in this thesis, SDL is not optimally suited for specifying communication protocols for the Internet due to their diverse nature. Therefore, this profile features new high-level language concepts rendering the specification and description of Internet protocols more intuitively while abstracting from concrete implementation issues. Due to its support of several concrete notations, this profile is designed to work with a number of UML compliant modeling tools. In contrast to other proposals, this profile binds the informal UML semantics with many semantic variation points by defining formal constraints for the profile definition and providing a mapping specification to SDL by the Object Constraint Language. In addition, the profile incorporates extension points to enable mappings to many formal description languages including SDL. To demonstrate the usability of the profile, a case study of a concrete Internet signaling protocol is presented.
    [Show full text]
  • Complete Code Generation from UML State Machine
    Complete Code Generation from UML State Machine Van Cam Pham, Ansgar Radermacher, Sebastien´ Gerard´ and Shuai Li CEA, LIST, Laboratory of Model Driven Engineering for Embedded Systems, P.C. 174, Gif-sur-Yvette, 91191, France Keywords: UML State Machine, Code Generation, Semantics-conformance, Efficiency, Events, C++. Abstract: An event-driven architecture is a useful way to design and implement complex systems. The UML State Machine and its visualizations are a powerful means to the modeling of the logical behavior of such an archi- tecture. In Model Driven Engineering, executable code can be automatically generated from state machines. However, existing generation approaches and tools from UML State Machines are still limited to simple cases, especially when considering concurrency and pseudo states such as history, junction, and event types. This paper provides a pattern and tool for complete and efficient code generation approach from UML State Ma- chine. It extends IF-ELSE-SWITCH constructions of programming languages with concurrency support. The code generated with our approach has been executed with a set of state-machine examples that are part of a test-suite described in the recent OMG standard Precise Semantics Of State Machine. The traced execution results comply with the standard and are a good hint that the execution is semantically correct. The generated code is also efficient: it supports multi-thread-based concurrency, and the (static and dynamic) efficiency of generated code is improved compared to considered approaches. 1 INTRODUCTION Completeness: Existing tools and approaches mainly focus on the sequential aspect while the concurrency The UML State Machine (USM) (Specification and of state machines is limitedly supported.
    [Show full text]
  • Mutating UML State Machine Behavior with Semantic Mutation Operators
    Mutating UML State Machine Behavior with Semantic Mutation Operators Anna Derezinska a and Łukasz Zaremba Institute of Computer Science, Warsaw University of Technology, Nowowiejska 15/19, Warsaw, Poland Keywords: Model-Driven Software Development, State Machine, Code Generation, Mutation Testing, Framework for Executable UML (FXU), C#. Abstract: In Model-Driven Software Development (MDSD), an application can be built using classes and their state machines as source models. The final application can be tested as any source code. In this paper, we discuss a specific approach to mutation testing in which modifications relate to different variants of behavioural features modelled by UML state machines, while testing deals with standard executions of the final application against its test cases. We have proposed several mutation operators aimed at mutating behaviour of UML state machines. The operators take into account event processing, time management, behaviour of complex states with orthogonal regions, and usage of history pseudostates. Different possible semantic interpretations are associated with each operator. The operators have been implemented in the Framework for eXecutable UML (FXU). The framework, that supports code generation from UML classes and state machines and building target C# applications, has been extended to realize mutation testing with use of multiple libraries. The semantic mutation operators have been verified in some MDSD experiments. 1 INTRODUCTION satisfying selected criteria (Jia and Harman, 2011). In a standard mutation testing process, syntactic Model-Driven Software Development (MDSD) can changes, so-called mutations, are injected into a be aimed at production of high quality software in a source code and supposed to be detected by test cases.
    [Show full text]
  • A Formalism for Specifying Model Merging Conflicts Mohammadreza Sharbaf, Bahman Zamani, Gerson Sunyé
    A Formalism for Specifying Model Merging Conflicts Mohammadreza Sharbaf, Bahman Zamani, Gerson Sunyé To cite this version: Mohammadreza Sharbaf, Bahman Zamani, Gerson Sunyé. A Formalism for Specifying Model Merging Conflicts. System Analysis and Modelling (SAM) conference, Oct 2020, Virtual Event, Canada. 10.1145/3419804.3421447. hal-02930770 HAL Id: hal-02930770 https://hal.archives-ouvertes.fr/hal-02930770 Submitted on 4 Sep 2020 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. A Formalism for Specifying Model Merging Conflicts Mohammadreza Sharbaf ∗ Bahman Zamani Gerson Sunyé MDSE Group, University of Isfahan MDSE Group, University of Isfahan LS2N, University of Nantes Isfahan, Iran Isfahan, Iran Nantes, France [email protected] [email protected] [email protected] ABSTRACT sites. Each of the participants focuses on specific aspects of the Verifying the consistency of model merging is an important step to- system and locally modifies only a particular part of the model. wards the support for team collaboration in software modeling and When participants deliver locally modified models, those need to evolution. Since merging conflicts are inevitable, this has triggered be integrated into a common relevant model for continuing the soft- intensive research on conflict management in different domains.
    [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]
  • Institution-Based Encoding and Verification of Simple UML
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Cronfa at Swansea University Institution-based Encoding and Verification of Simple UML State Machines in CASL/SPASS Tobias Rosenberger1;2, Saddek Bensalem2, Alexander Knapp3, and Markus Roggenbach1 1 Swansea University, U.K. ft.rosenberger.971978; [email protected] 2 Université Grenoble Alpes, France [email protected] 3 Universität Augsburg, Germany [email protected] Abstract. We present a new approach on how to provide institution-based seman- tics for UML state machines. Rather than capturing UML state machines directly # as an institution, we build up a new logical framework MD into which UML # state machines can be embedded. A theoroidal comorphism maps MD into the Casl institution. This allows for symbolic reasoning on UML state machines. By utilising the heterogeneous toolset HeTS that supports Casl, a broad range of verification tools, including the automatic theorem prover Spass, can be combined in the analysis of a single state machine. 1 Introduction As part of a longstanding line of research [9,10,19,8], we set out on a general programme to bring together multi-view system specification with UML diagrams and heterogeneous specification and verification based on institution theory, giving the different system views both a joint semantics and richer tool support. Institutions, a formal notion of a logic, are a principled way of creating such joint semantics. They make moderate assumptions about the data constituting a logic, give uniform notions of well-behaved translations between logics and, given a graph of such translations, automatically give rise to a joint institution.
    [Show full text]
  • Network Protocol Design and Evaluation
    Network Protocol Design and Evaluation 04 - Protocol Specification, Part I Stefan Rührup University of Freiburg Computer Networks and Telematics Summer 2009 Overview ‣ In the last chapter: • The development process (overview) ‣ In this chapter: • Specification • State machines and modeling languages • UML state charts and sequence diagrams • SDL and MSC (Part II) Network Protocol Design and Evaluation Computer Networks and Telematics Stefan Rührup, Summer 2009 2 University of Freiburg What are we modeling? Transitional Systems Reactive Systems input-output transformation event-driven e.g. scientific computation, compilers e.g. communication protocols, operating systems, control systems correctness criteria: correctness criteria: - termination - non-termination under normal - correctness of input-output conditions transformation - correctness of event-response actions formal models describe event-response sequences, including state information [S. Leue, Design of Reactive Systems, Lecture Notes, 2002] Network Protocol Design and Evaluation Computer Networks and Telematics Stefan Rührup, Summer 2009 3 University of Freiburg Specification with State Machines ‣ A protocol interacts with the environment • triggered by events • responds by performing actions • behaviour depends on the history of past events, i.e. the state event 1 state 1 state 2 action action event 2 ‣ state machines do not model the data flow, but the flow of control Network Protocol Design and Evaluation Computer Networks and Telematics Stefan Rührup, Summer 2009 4 University of
    [Show full text]
  • Precise Semantics of UML State Machines (PSSM)
    An OMG® Executable UML® Publication Precise Semantics of UML State Machines (PSSM) Version 1.0 __________________________________________________ OMG Document Number: formal/2019-05-01 Date: May 2019 Normative reference: https://www.omg.org/spec/PSSM/1.0 Machine readable file(s): https://www.omg.org/PSSM/20181101 Normative: https://www.omg.org/spec/PSSM/20181101/PSSM_Syntax.xmi http s ://www.omg.org/spec/PSSM/20181101/PSSM_Semantics.xmi https://www.omg.org/spec/PSSM/20181101/PSSM_TestSuite.xmi _________________________________________________ Copyright © 2016 Airbus Group Copyright © 2016, 2018 Commissariat á l'Energie Atomique et Alternatives (CEA) Copyright © 2016, 2018 Data Access Technologies, Inc. (Model Driven Solutions) Copyright © 2016 LieberLieber Software Copyright © 2017, 2019 Object Management Group, Inc. Copyright © 2016 No Magic, Inc. Copyright © 2016 Simula Research Laboratory 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. LICENSES The companies listed above have granted to the Object Management Group, Inc. (OMG) a nonexclusive, royalty-free, paid up, worldwide license to copy and distribute this document and to modify this document and distribute copies of the modified version. Each of the copyright holders listed above has agreed that no person shall be deemed to have infringed the copyright in the included material of any such copyright holder by reason of having used the specification set forth herein or having conformed any computer software to the specification.
    [Show full text]
  • Partial Reconfiguration in the Field of Logic Controllers Design 353
    INTL JOURNAL OF ELECTRONICS AND TELECOMMUNICATIONS, 2013, VOL. 59, NO. 4, PP. 351–356 Manuscript received November 3, 2013; revised December, 2013. DOI: 10.2478/eletel-2013-0042 Partial Reconfiguration in the Field of Logic Controllers Design Michał Doligalski and Arkadiusz Bukowiec Abstract—The paper presents method for logic controllers Context switching techniques presented in the paper, provide multi context implementation by means of partial reconfigura- adaptation of control algorithm of the production process. tion. The UML state machine diagram specifies the behaviour Context is the alternative specification (version) of particu- of the logic controller. Multi context functionality is specified at the specification level as variants of the composite state. lar function provided by logic control algorithm. Alternative Each composite state, both orthogonal or compositional, de- context is required when production process has two or more scribes specific functional requirement of the control process. alternative formulas, e.g. ingredients may be in the form of The functional decomposition provided by composite states raw material or semi-finished product. It’s not necessary to is required by the dynamic partial reconfiguration flow. The remodel whole control algorithm but only some parts should state machines specified by UML state machine diagrams are transformed into hierarchical configurable Petri nets (HCfgPN). be adjusted to actual conditions. HCfgPN are a Petri nets variant with the direct support of the exceptions handling mechanism. The paper presents places- oriented method for HCfgPN description in Verilog language. II. PARTIAL RECONFIGURATION In the paper proposed methodology was illustrated by means of Classical design flow of LCs implemented in the FPGA simple industrial control process.
    [Show full text]
  • Transforming Erlang Finite State Machines
    Transforming Erlang finite state machines D´anielLuk´acs,Melinda T´oth,Istv´anBoz´o [email protected], [email protected], [email protected] ELTE E¨otv¨osLor´andUniversity Faculty of Informatics Budapest, Hungary Abstract Model driven development approaches help to alleviate the abstraction gap between high-level design and actual implementation, to aid design, development and maintenance of industrial scale software systems. To provide automatic, easily usable tools for stakeholders, model driven development essentially relies on efficient and expressive translations between the program source code and the model. We present a declarative, rule-based approach to deterministically transform Erlang program sources that satisfy a certain syntactical constraint, into valid UML models of state machines. The transforma- tion relies only on static analysis techniques, and the produced model conforms to the state machine metamodel defined in OMG UML 2.0. 1 Introduction In industrial settings there is an always present necessity to use large software applications with over millions of lines of source code. During design, development and maintenance of software, managing the complexity emerging from these large volumes becomes a critical issue in order to realise a successful product lifecycle. The most important resource needed to manage complexity is relevant, up-to-date information, commonly manifested as the design, development and user documentations. As the software evolves during its development and usage, documentations also have to be actualised to mirror the collective knowledge that was incorporated in the system during its changes. To implement this resource intensive process with the highest efficiency, organisations concerned with software development employ various automatic software analysis tools and machine processable documents to support the developers in creating documentations and keeping them up to date.
    [Show full text]