Results 1 -
7 of
7
Towards a Practical Approach to Check UML/fUML Models Consistency Using CSP
"... Abstract. This work provides an underpinning for a systems modelling approach based on UML and fUML together. It uses UML state diagrams as a starting point for modelling system object behaviours abstractly, then refining each state diagram by adding the implementation decisions in a form of a fUML ..."
Abstract
-
Cited by 3 (1 self)
- Add to MetaCart
(Show Context)
Abstract. This work provides an underpinning for a systems modelling approach based on UML and fUML together. It uses UML state diagrams as a starting point for modelling system object behaviours abstractly, then refining each state diagram by adding the implementation decisions in a form of a fUML activity diagram. Maintaining behavioural consis-tency between each UML state diagram and its corresponding fUML activity diagram is an important but difficult task. In this paper we introduce a framework that automates checking such consistency in a practical way. The framework is based on formalizing these diagrams into the process al-gebra CSP to do trace refinement checking using FDR2. One of the main contributions in this work is that we transform FDR2 output (counter-example in case of inconsistency) back to the UML/fUML model in a way that allows the modeller to debug the consistency problem. To be able to provide this kind of interactive feedback, the generated CSP model is augmented with traceability information. A case tool plugin based on the Epsilon model management framework has been developed to support our approach. 1
Trust-Based Monitoring of Component-Structured Software
, 2004
"... In contrast to traditional software, component-structured systems are developed by combining independently designed and sold software components. This technology promises an easier reuse of software building blocks and, in consequence, a significant reduction of the efforts and costs to produce soft ..."
Abstract
- Add to MetaCart
In contrast to traditional software, component-structured systems are developed by combining independently designed and sold software components. This technology promises an easier reuse of software building blocks and, in consequence, a significant reduction of the efforts and costs to produce software applications. On the other side, component-structured software is subject to a new class of security threats. In particular, a maliciously acting component may easily spoil the application incorporating it. In this paper we introduce an approach addressing this particular threat. A so-called security wrapper monitors the events passing the interface of a component and checks them for compliance with formally specified security policies guaranteeing a benevolent behavior of the checked component. We introduce the layout and functionality of the wrappers and outline the formal security specifications which can be easily derived from a set of specification patterns. Unfortunately, the security wrappers cause runtime overhead which, however, can be significantly reduced by relaxing the degree of monitoring trustworthy components. In order to support the decision, whether a component can be trusted, we developed a special trust information service. This service collects evaluation reports of a particular component running in various applications which are provided by the different security wrappers. Based on the evaluation reports, the trust information service computes a so-called trust value which is delivered to the security wrappers, and a wrapper adjusts the degree of supervision of a component based on its trust value. The use of the security wrappers as well as of the trust management approach is clarified by means of an e-commerce example realizing the automated procurement of goods for a fastfood restaurant.
A Framework for Verifying UML Behavioral Models
"... Abstract. MDD and MDA approaches require capturing the behavior of UML models in sufficient detail and precision so that the models can be automatically implemented/executed in the production environment. With this purpose, Action Semantics were added to the UML specification as the fundamental unit ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract. MDD and MDA approaches require capturing the behavior of UML models in sufficient detail and precision so that the models can be automatically implemented/executed in the production environment. With this purpose, Action Semantics were added to the UML specification as the fundamental unit of behavior specifications. Actions are the basis for defining the fine-grained behavior of operations, activity diagrams, interaction diagrams and state machines. Unfortunately, most of the current proposals devoted to the verification of behavioral models tend to skip the analysis of the actions they may include. The main goal of this PhD is to cover this gap by proposing a new verification framework aimed at verifying action-based behavioral specifications. In particular, we plan to describe several correctness properties of these specifications, develop a set of verification techniques based on the static analysis of the actions included in the actionbased behavioral specifications for verifying these properties and integrate our techniques with other existing verification approaches. 1
Transforming Collaborative Service Specifications into Efficiently Executable State Machines
"... Abstract: We describe an algorithm to transform UML 2.0 activities into state machines. The implementation of this algorithm is an integral part of our tool-supported engineering approach for the design of interactive services, in which we compose services from reusable building blocks. In contrast ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract: We describe an algorithm to transform UML 2.0 activities into state machines. The implementation of this algorithm is an integral part of our tool-supported engineering approach for the design of interactive services, in which we compose services from reusable building blocks. In contrast to traditional ap-proaches, these building blocks are not only components, but also collaborations in-volving several participants. For the description of their behavior, we use UML 2.0 activities, which are convenient for composition. To generate code running on exist-ing service execution platforms, however, we need a behavioral description for each individual component, for which we use a special form of UML 2.0 state machines. The algorithm presented here transforms the activities directly into state machines, so that the step from collaborative service specifications to efficiently executable code is completely automated. Each activity partition is transformed into a separate state machine that communicates with other state machines by means of signals, so that the system can easily be distributed. The algorithm creates a state machine by reachability analysis on the states modeled by a single activity partition. It is implemented in Java and works directly on an Eclipse UML2 repository.
International Journal on Software Tools for Technology Transfer manuscript No. (will be inserted by the editor) An Integrated Framework for Checking the Behaviour of fUML Models Using CSP
"... Abstract Transforming UML models into a formal rep-resentation to check certain properties has been ad-dressed many times in the literature. We have observed several aspects that inhibit the practical use of such approach in real life projects. In this paper we address some of those aspects, using f ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract Transforming UML models into a formal rep-resentation to check certain properties has been ad-dressed many times in the literature. We have observed several aspects that inhibit the practical use of such approach in real life projects. In this paper we address some of those aspects, using fUML (Foundational sub-set for executable UML) as a semi-formal modelling language and CSP as a formal language. One of those aspects is to perform the formalization automatically without any interaction with the modeller, who should be isolated from the formal methods domain. Moreover, we provide the modeller with modeller-friendly feed-back after performing the model checking on the for-malization. This work also considers the formalization of systems that depend on asynchronous communica-tion between components in order to allow checking of the dynamic behaviour of systems. Several optimization approaches have been used to be able to model check such systems using FDR2, and at the same time comply with the fUML inter-object communication mechanism. The optimized approach is described in full details in this paper. We have designed a comprehensive framework that is implemented as a plugin to MagicDraw (the case tool we use) that we call Compass. The framework depends on Epsilon as a model transformation tool that utilizes the Model Driven Engineering (MDE) approach. In or-der to validate our framework, we have checked a To-
Service Specification by Composition of Collaborations — An Example
"... We outline a specification style for reactive services that focuses on UML 2.0 collaborations and activities as reusable specification building blocks. In contrast to tra-ditional component-based approaches, a collaboration di-rectly describes the interactions between the components as well as the i ..."
Abstract
- Add to MetaCart
(Show Context)
We outline a specification style for reactive services that focuses on UML 2.0 collaborations and activities as reusable specification building blocks. In contrast to tra-ditional component-based approaches, a collaboration di-rectly describes the interactions between the components as well as the internal behavior necessary for a component to take part in it. To compose services from such reusable col-laborations, we use events identified as input and output pins on the activities that are connected together. While our approach is formally settled in temporal logic, in this paper we focus on an example specification from the viewpoint of a service engineer. 1.
Màster en Computació
"... Verifying consistency between structural and behavioral schemas in UML ..."
(Show Context)
