Translating standard process models to BPEL

Standardisation of languages in the field of business process management has long been an elusive goal. Recently though, consensus has built around one process implementation language, namely BPEL, and two fundamentally similar process modelling notations, namely UML Activity Diagram (UML AD) and BPMN. This paper presents a technique for generating BPEL code from process models expressed in a core subset of BPMN and UML AD. This model-to-code translation is a necessary ingredient to the emergence of model-driven business process development environments based on these standards. The proposed translation has been implemented as an open source tool

A thread-tag based semantics for sequence diagrams

The sequence diagram is one of the most popular behaviour modelling languages which offers an intuitive and visual way of describing expected behaviour of object-oriented software. Much research work has investigated ways of providing a formal semantics for sequence diagrams. However, these proposed semantics may not properly interpret sequence diagrams when lifelines do not correspond to threads of controls. In this paper, we address this problem and propose a thread-tag based sequence diagram as a solution. A formal, partially ordered multiset based semantics for the thread-tag based sequence diagrams is proposed

SDL based validation of a node monitoring protocol

Mobile ad hoc network is a wireless, self-configured, infrastructureless network of mobile nodes. The nodes are highly mobile, which makes the application running on them face network related problems like node failure, link failure, network level disconnection, scarcity of resources, buffer degradation, and intermittent disconnection etc. Node failure and Network fault are need to be monitored continuously by supervising the network status. Node monitoring protocol is crucial, so it is required to test the protocol exhaustively to verify and validate the functionality and accuracy of the designed protocol. This paper presents a validation model for Node Monitoring Protocol using Specification and Description Llanguage (SDL) using both Static Agent (SA) and Mobile Agent (MA). We have verified properties of the Node Monitoring Protocol (NMP) based on the global states with no exits, deadlock states or proper termination states using reachability graph. Message Sequence Chart (MSC) gives an intuitive understanding of the described system behavior with varying node density and complex behavior etc.Comment: 16 pages, 24 figures, International Conference of Networks, Communications, Wireless and Mobile 201

Advanced Positioning and Location based services in 4G Mobile-IP Radio Access Networks

2004 IEEE 15TH IEEE International Symposium on personal, indoor and mobile radio communications (PIMRC 2004), Barcelona, Spain, 5-8 september 2004.This paper proposes an evolved architecture from 3G networks to provide basic and advanced positioning methods for location based services in mobile IPv6-based radio access networks. We start analyzing current status of location-based services (i.e. LBS or LCS) and architectures in 3G networks as well as state-of-the-art research on LBS and mobile Internet. Next we set the requirements the solution should fulfill. We continue proposing the evolved architecture for support of basic and advanced positioning methods, using MIPv6 and HMIPv6 as mobility scenario for the mobile IPv6 based RAN, describing element's functions and changes from current approaches as well as description of the dynamic behavior. We complete the proposal with a bandwidth analysis of the signaling, identifying issues when planning implementation of LCS services in the network

Improving the reuse possibilities of the behavioral aspects of object-oriented domain models.

Reuse of domain models is often limited to the reuse of the structural aspects of the domain (e.g. by means of generic data models). In object-oriented models, reuse of dynamic aspects is achieved by reusing the methods of domain classes. Because in the object-oriented approach any behavior is attached to a class, it is impossible to reuse behavior without at the same time reusing the class. In addition, because of the message passing paradigm, object interaction must be specified as a method attached to one class which is invoked by another class. In this way object interaction is hidden in the behavioral aspects of classes. This makes object interaction schemas difficult to reuse and customize. The focus of this paper is on improving the reuse of object-oriented domain models. This is achieved by centering the behavioral aspects around the concept of business events.Model; Models;

The use of the concept of event in enterprise ontologies and requirements engineering literature.

The concept of event is used in a lot of meanings. It can be the possible outcome of doing something (probability theory), it can be a business transaction (accounting), or just a plain happening. In software engineering, the concept of event is also used a lot. It is used to accomplish loose coupling between software components or to realise interaction between different services. There is however not a consensus on the meaning of `an event'. In enterprise ontologies, an event is defined as a happening at one point in time, or as an activity which takes time to complete. In requirement engineering, the same different uses can be found, together with an event as a request for something that needs to be done. These differences can also be found in implementation. All these distinct purposes of the word event make it difficult to integrate and use different requirement engineering techniques. Comparison or transformations between models drawn in different grammars is impossible because of the ambiguity of the concept of event. We define three meanings for an event that are used by enterprise ontologies and requirement engineering techniques: an achievement (happening at one point in time), an activity (happening over time) and a request (a demand for something that needs to be done). We also identify a missing link between real economic events, the events defined in the requirements model and the events used in implementation.Requirements modelling; Enterprise ontology; Process modelling; Dynamic; Event;

Exploring narrativity in data visualization in journalism

Many news stories are based on data visualization, and storytelling with data has become a buzzword in journalism. But what exactly does storytelling with data mean? When does a data visualization tell a story? And what are narrative constituents in data visualization? This chapter first defines the key terms in this context: story, narrative, narrativity, showing and telling. Then, it sheds light on the various forms of narrativity in data visualization and, based on a corpus analysis of 73 data visualizations, describes the basic visual elements that constitute narrativity: the instance of a narrator, sequentiality, temporal dimension, and tellability. The paper concludes that understanding how data are transformed into visual stories is key to understanding how facts are shaped and communicated in society