scholarly journals Διαδικασία ανάπτυξης βιομηχανικών εφαρμογών ελέγχου και εργαλείο υποστήριξής της

2006 ◽  
Author(s):  
Χρήστος Τρανώρης
Keyword(s):  
Unified Modeling Language ◽  
International Electrotechnical Commission ◽  
Object Constraint Language ◽  
Unified Modeling ◽  
Model Driven ◽  
Function Block ◽  
Uml Profiles ◽  
Constraint Language ◽  
Function Blocks ◽  
Meta Modeling

Η αναβάθμιση της διαδικασίας ανάπτυξης εφαρμογών λογισμικού που αφορούν τον έλεγχο βιομηχανικών συστημάτων, είναι ένα θέμα που απασχολεί για δεκαετίες του μηχανικούς ελέγχου αλλά και τους μηχανικούς λογισμικού. Κατά την ανάπτυξη των βιομηχανικών εφαρμογών, οι μηχανικοί καλούνται να ικανοποιήσουν πληθώρα απαιτήσεων μεταξύ των οποίων: συμβατότητα με το υπάρχον εγκατεστημένο υλικό, συμβατότητα με τις ήδη εγκατεστημένες παλαιότερες εφαρμογές και επαναχρησιμοποίηση τμημάτων λογισμικού. Για τους παραπάνω λόγους, αναζητούνται συνεχώς λύσεις οι οποίες: θα προσφέρουν μια περισσότερο φιλική προς το μηχανικό ελέγχου διαδικασία ανάπτυξης η οποία θα υποστηρίζει επεκτασιμότητα των εφαρμογών, θα διευκολύνει την επαναχρησιμοποίηση τμημάτων του λογισμικού, θα ενισχύει την συντήρηση του λογισμικού και θα είναι ανεξάρτητη από το υλικό εκτέλεσης των βιομηχανικών συστημάτων. Η International Electrotechnical Commission (IEC) για να αντιμετωπίσει τις απαιτήσεις των σύγχρονων συστημάτων δημιούργησε το πρότυπο IEC61499 το οποίο έρχεται να επεκτείνει το Function Block του IEC61131. Το IEC61499, καθορίζει μια μεθοδολογία σχεδιασμού, όπου το Function Block είναι το βασικό δομικό συστατικό για την ανάπτυξη διαλειτουργικών κατανεμημένων εφαρμογών αυτοματισμού και ελέγχου. Οι εφαρμογές ελέγχου μπορούν να υλοποιηθούν από Function Block δίκτυα διασυνδέοντας τις εισόδους και εξόδους τους. Το IEC61499 προτείνει επίσης τον σχεδιασμό εργαλείων λογισμικού για την υποστήριξη (εν μέρει αυτοματοποίηση) της διαδικασίας ανάπτυξης. Στην παρούσα διατριβή, παρουσιάζεται μια νέα προσέγγιση για τον σχεδιασμό κατανεμημένων βιομηχανικών εφαρμογών και πιο συγκεκριμένα Συστημάτων Μέτρησης και Ελέγχου Βιομηχανικών Διεργασιών1 (IPMCSs) όπως τα ορίζει το πρότυπο IEC. Η προσέγγιση εστιάζει στον ορισμό μιας μεθοδολογίας για την φάση της ανάλυσης και κύρια την τεκμηρίωση των απαιτήσεων και τον μετέπειτα μετασχηματισμό του μοντέλου ανάλυσης σε μοντέλο σχεδιασμού. Η προτεινόμενη προσέγγιση βασίζεται σε κατάλληλα οριζόμενες έννοιες και τεχνικές και αξιοποιεί τελευταίες τάσεις από το χώρο της Μηχανιστικής Λογισμικού (Software Engineering), όπως είναι η έννοια της μετα-μοντελοποίησης (Meta-modeling) όπως αυτή ορίζεται στα πλαίσια της βασισμένης σε μοντέλα ανάπτυξης (Model Driven Development) και της Unified Modeling Language (UML) και των επεκτάσεων της (UML Profiles) και εφαρμογή αυτών στο σχεδιασμό βιομηχανικών εφαρμογών. Για την ομαλή μετάβαση από τις καταγεγραμμένες απαιτήσεις σε μοντέλα σχεδιασμού τεκμηριώθηκε και παρουσιάζεται ένα σύνολο κανόνων μετασχηματισμού το οποίο περιγράφηκε αυστηρά με χρήση της Object Constraint Language. Για να αξιοποιηθεί η προτεινόμενη προσέγγιση από μηχανικούς ελέγχου, σχεδιάστηκε και υλοποιήθηκε ένα εργαλείο λογισμικού συμβατό με το πρότυπο IEC61499. Το εργαλείο που έχει το όνομα CORFU ESS έρχεται να υποστηρίξει: α) την φάση της ανάλυσης, β) τον μετασχηματισμό του μοντέλου ανάλυσης σε μοντέλο σχεδιασμού, γ) τον σχεδιασμό εφαρμογών με Function Blocks όπως ορίζει το IEC61499, δ) την κατανομή των Function Block στις συσκευές των βιομηχανικών δικτύων και ε) τον έλεγχο των τελικών Function Block δικτύων. Η προσέγγιση εφαρμόσθηκε σε μελέτες περίπτωσης για να επιδείξει την εφαρμοσιμότητα της προτεινόμενης διαδικασίας, την αποτελεσματικότητα του εργαλείου που αναπτύχθηκε και την δυνατότητα της διαδικασίας και του εργαλείου να καλύψουν απαιτήσεις μικρής ή μεγάλης κλίμακας εφαρμογών.

Expressing and Validating OCL Constraints using Graphs

2013 ◽  
pp. 93-107
Author(s):  
Najet Zoubeir ◽  
Adel Khalfallah ◽  
Samir Ben Ahmed
Keyword(s):  
Graph Transformation ◽  
Unified Modeling Language ◽  
Object Constraint Language ◽  
Unified Modeling ◽  
Constraint Language ◽  
Uml Diagrams ◽  
Class Diagrams ◽  
Definition Of ◽  
Transformation Systems ◽  
Graph Transformation Systems

The definition of the semantics of visual languages, in particular Unified Modeling Language (UML) diagrams, using graph formalism has known a wide success, since graphs fit the multi-dimensional nature of this kind of language. However, constraints written in Object Constraint Language (OCL) and defined on these models are still not well integrated within this graph-based semantics. In this chapter, the authors propose an integrated semantics of OCL constraints within class diagrams, using graph transformation systems. Their contribution is divided into two parts. In the first part, they introduce graph constraint patterns, as the translation into graphs of a subset of OCL expressions. These patterns are validated with experimental examples using the GROOVE toolset. In the second part, the authors define the relation between OCL and UML models within their graph transformation system.

Specification of Business Components Using Temporal OCL

2011 ◽  
pp. 48-65 ◽  
Author(s):  
Stefan Conrad ◽  
Klaus Turowski
Keyword(s):  
Layered Structure ◽  
Unified Modeling Language ◽  
Third Party ◽  
Object Constraint Language ◽  
Unified Modeling ◽  
Application Systems ◽  
Constraint Language ◽  
Business Application ◽  
Contractual Agreements ◽  
Software Contracts

Compositional, plug-and-play-like reuse of black box components requires sophisticated techniques to specify components, especially when combined with third party components that are traded on component markets to individual customer’s business application systems. As in established engineering disciplines, like mechanical engineering or electrical engineering, formal documentation of business components that become part of contractual agreements are needed. With this initial problem, we explain the general, layered structure of software contracts for business components and show shortcomings of common specification approaches. Furthermore, we introduce a formal notation for the specification of business components that extends the Object Constraint Language (OCL) and allows for a broader use of the Unified Modeling Language (UML) with respect to the layered structure of software contracts for business components.

The Whole-Part Relationship in the Unified Modeling Language

2001 ◽  
pp. 186-210 ◽  
Author(s):  
Franck Barbier ◽  
Brian Henderson-Sellers ◽  
Andreas L. Opdahl ◽  
Martin Gogolla
Keyword(s):  
Unified Modeling Language ◽  
Modeling Language ◽  
Object Constraint Language ◽  
Unified Modeling ◽  
Constraint Language ◽  
Definition Of ◽  
Uml Metamodel ◽  
The Way

This study of the semantics of the Whole-Part relationship in OO modeling is based upon, extends and, specifically, formalizes earlier analyses of the semantics of UML’s Aggregation and Composition (white and black diamonds, also called shared aggregation and composite aggregation). Although UML is nowadays regarded as a standard and is widely used as an OO modeling language, the way the Whole-Part relationship is formalized is unsatisfactory. Here, we provide a rigorous specification of various forms of the Whole-Part relationship using OCL (Object Constraint Language). The first part of the specification is based on the differentiation between primary characteristics (applicable to all Whole-Part relationships) assigned to a new Whole-Part metatype in the UML and secondary features, which are possessed by subtypes of this metatype and permit the representation of several “flavors” of the Whole-Part relationship. This UML-compliant style of specification, based on the use of OCL as well as metamodeling, allows us to directly incorporate our results into the UML metamodel, in particular revising UML’s definition of Composition.

Temporal OCL

2001 ◽  
pp. 152-167 ◽  
Author(s):  
Stefan Conrad ◽  
Klaus Turowski
Keyword(s):  
Layered Structure ◽  
Unified Modeling Language ◽  
Third Party ◽  
Background Information ◽  
Object Constraint Language ◽  
Unified Modeling ◽  
Application Systems ◽  
Constraint Language ◽  
Contractual Agreements ◽  
Software Contracts

Compositional plug-and-play-like reuse of black box components requires sophisticated techniques to specify components, especially if we combine third-party components, which are traded on component markets, to customer-individual business application systems. As in established engineering disciplines like mechanical engineering or electrical engineering, we need a formal documentation of business components that becomes part of contractual agreements. Taking this problem as a starting point, we explain the general layered structure of software contracts for business components and show shortcomings of common specification approaches. Furthermore, we introduce a formal notation for the specification of business components that extends the Object Constraint Language (OCL) and that allows a broader use of the Unified Modeling Language (UML) with respect to the layered structure of software contracts for business components. The remainder of the chapter is as follows. After providing background information in the next section, we discuss the necessity of a multi-level notation standard. Thereafter, we explain how the OCL can be used to specify business components. Taking this as a basis, we proceed to the main thrust of our chapter the temporal extension of OCL. Finally, we present our conclusions and give an outlook.

Modeling

2012 ◽  
pp. 286-310
Author(s):  
P. Papajorgji ◽  
F. Pinet ◽  
A. Miralles ◽  
E. Jallas ◽  
P.M. Pardalos
Keyword(s):  
Information Systems ◽  
Design Patterns ◽  
Unified Modeling Language ◽  
Object Constraint Language ◽  
Problem Domain ◽  
Enterprise Information ◽  
Unified Modeling ◽  
Model Driven ◽  
Spatial Systems ◽  
Agriculture And Environment

Enterprise information systems in agriculture and environment are becoming more complex and difficult to design and implement. This paper aims to show our vision on using model-based approaches to design complex and flexible agricultural and environmental information systems. At the center of this modeling approach is the Unified Modeling Language that facilitates expressing visually concepts of a problem domain and their relationships. UML has a core of notations that are generic and that can be used to model problems in any domain but can be extended to create profiles in order to take into consideration modeling concerns in a particular problem domain. UML profiles are created to use UML in designing spatial systems, ontologies, model driven architecture-based systems and Web-based systems and a recent profile makes it possible to use UML for business modeling purposes. UML is used to present design patterns; their use is crucial in designing complex and flexible information systems. Recently, UML is enriched with Object Constraint Language that is used to express constraints on modeling artifacts. The paper presents the state of the art in modeling agricultural and environmental systems and provides discussions for future directions.

Analyzing Inconsistencies in UML/OCL Models

2015 ◽  
Vol 25 (03) ◽  
pp. 1640021 ◽  
Author(s):  
Nils Przigoda ◽  
Robert Wille ◽  
Rolf Drechsler
Keyword(s):  
Unified Modeling Language ◽  
Modeling Language ◽  
Modeling Languages ◽  
Automatic Method ◽  
Formal Models ◽  
Object Constraint Language ◽  
Validation And Verification ◽  
Unified Modeling ◽  
Constraint Language ◽  
Abstract Description

Modeling languages such as the unified modeling language (UML) or the systems modeling language (SysML) in combination with constraint languages such as the object constraint language (OCL) allows for an abstract description of a system prior to its implementation. But the resulting system models can be highly non-trivial and, hence, errors in the descriptions can easily arise. In particular, too strong restrictions leading to an inconsistent model are common. Motivated by this, researchers and engineers developed methods for the validation and verification of given formal models. However, while these methods are efficient to detect the existence of an inconsistency, the designer is usually left alone to identify the reasons for it. In this contribution, we propose an automatic method which efficiently determines reasons explaining the contradiction in an inconsistent UML/OCL model. For this purpose, all constraints causing the contradiction are comprehensibly analyzed. By this, the designer is aided during the debugging of his/her model.

EVIDENTIAL DIAGNOSIS OF INCONSISTENCIES IN OBJECT-ORIENTED DESIGNS

2004 ◽  
Vol 14 (02) ◽  
pp. 141-178 ◽  
Author(s):  
GEORGE SPANOUDAKIS ◽  
KURIAKOS KASIS ◽  
FLORA DRAGAZI
Keyword(s):  
Software Design ◽  
Formal Language ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
Belief Functions ◽  
Object Constraint Language ◽  
Unified Modeling ◽  
Software Designers ◽  
Constraint Language ◽  
Diagnostic Framework

This paper presents a diagnostic framework for assessing the significance of inconsistencies (i.e., violations of consistency rules) in software design models expressed in the Unified Modeling Language (UML). The assessment is based on significance criteria that software designers can specify and associate with specific consistency rules. These criteria define characteristics that the model elements involved in the violation of a rule should have for the inconsistency to be significant, and they are specified in a formal language derived from the Object Constraint Language (OCL). The satisfiability of the criteria by individual model elements is measured by belief functions defined by the framework. The measures generated by these functions are used to rank the inconsistencies caused by different model elements. The presented framework has been evaluated through a set of experiments. The results of these experiments show that criteria definable in the framework can be used to produce relatively elaborate significance-rankings of inconsistencies.

scholarly journals An Object-Oriented Hypermedia Reference Model Formally Specified in UML

2003 ◽  
pp. 59-78 ◽  
Author(s):  
Nora Koch
Keyword(s):  
Graphical Representation ◽  
Reference Model ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
Mobile Systems ◽  
Modeling Language ◽  
Object Constraint Language ◽  
Unified Modeling ◽  
Constraint Language ◽  
Class Diagrams

Although the Unified Modeling Language (UML) is by now accepted as a standard and is widely used as an object-oriented modeling language, some languages such as Z or VDM are preferred to formally specify reference models. Here, we present a reference model for hypermedia systems in UML. It is an object-oriented and Dexter-based approach that uses UML to provide an intuitive graphical representation of the model. The class diagrams are supplemented with formal constraints in the Object Constraint Language (OCL), adding invariants on elements as well as preconditions and postconditions on operations. The result is an easily extendable reference model for describing specific hypermedia systems, for example, like adaptive or mobile systems. Our contribution shows how formal and semiformal object-oriented techniques can be integrated in the metamodeling process.

From MARTE to Reconfigurable NoCs

2010 ◽  
pp. 135-157
Author(s):  
Imran Rafiq Quadri ◽  
Majdi Elhaji ◽  
Samy Meftali ◽  
Jean-Luc Dekeyser
Keyword(s):  
System Modeling ◽  
Unified Modeling Language ◽  
Modeling And Analysis ◽  
Unified Modeling ◽  
Model Driven ◽  
Abstraction Level ◽  
Management Group ◽  
High Level Modeling ◽  
High Level ◽  
Abstraction Levels

Due to the continuous exponential rise in SoC’s design complexity, there is a critical need to find new seamless methodologies and tools to handle the SoC co-design aspects. We address this issue and propose a novel SoC co-design methodology based on Model Driven Engineering and the MARTE (Modeling and Analysis of Real-Time and Embedded Systems) standard proposed by Object Management Group, to raise the design abstraction levels. Extensions of this standard have enabled us to move from high level specifications to execution platforms such as reconfigurable FPGAs. In this chapter, we present a high level modeling approach that targets modern Network on Chips systems. The overall objective: to perform system modeling at a high abstraction level expressed in Unified Modeling Language (UML); and afterwards, transform these high level models into detailed enriched lower level models in order to automatically generate the necessary code for final FPGA synthesis.

Modeling

2010 ◽  
Vol 1 (1) ◽  
pp. 1-25 ◽  
Author(s):  
Petraq Papajorgji ◽  
François Pinet ◽  
A. Miralles ◽  
E. Jallas ◽  
P.M. Pardalos
Keyword(s):  
Information Systems ◽  
Design Patterns ◽  
Unified Modeling Language ◽  
Object Constraint Language ◽  
Problem Domain ◽  
Enterprise Information ◽  
Model Driven ◽  
Environmental Information Systems ◽  
Spatial Systems ◽  
Present Design

Enterprise information systems in agriculture and environment are becoming more complex and difficult to design and implement. This paper aims to show our vision on using model-based approaches to design complex and flexible agricultural and environmental information systems. At the center of this modeling approach is the Unified Modeling Language that facilitates expressing visually concepts of a problem domain and their relationships. UML has a core of notations that are generic and that can be used to model problems in any domain but can be extended to create profiles in order to take into consideration modeling concerns in a particular problem domain. UML profiles are created to use UML in designing spatial systems, ontologies, model driven architecture-based systems and Web-based systems and a recent profile makes it possible to use UML for business modeling purposes. UML is used to present design patterns; their use is crucial in designing complex and flexible information systems. Recently, UML is enriched with Object Constraint Language that is used to express constraints on modeling artifacts. The paper presents the state of the art in modeling agricultural and environmental systems and provides discussions for future directions.

Sign in / Sign up

Export Citation Format

Share Document