PMG-pro: a model-driven development method of service-based applications

In the Internet of Things, billions of networked and software-driven devices will be connected to the Internet. They can communicate and cooperate with each other to form a composite system. In this paper, we propose PMG-pro (present, model, generate and provide), a language independent, bottom-up and model-driven method for the development of such composite system. We envision that all devices in the Internet of Things provide their functionalities as services. From a service description, a service presenter generates source code (i.e., for the service invocations) and uses an abstract graphical representation to represent a service. The code is connected to the abstract graphical service representation. A service abstractor constructs the abstract graphical representations even more abstract in hierarchical service taxonomy. Software developers use the abstract graphical service presentations to specify new service-based applications, while the source code is used for the automation of code generation

Mapping i* within UML for Business Modeling

[Context and Motivation] Business modeling is nowadays a common approach in huge enterprise software developments. It notably allows to align business processes and supporting IT solutions at best, to produce a documentation of the company’s "savoir-faire" and to look for possible optimizations. The business modeling discipline of the Rational Unified Process (RUP) has enriched the semantic of the Unified Modeling Language’s (UML) use case diagrams for the special purpose of representing the organization’s processes with accurate elements. [Question/Problem] RUP/UML business use case scemantics are nevetheless only intended to further stereotype use case models and not to be used for reasoning. In parallel and in line with artificial intelligence concepts, researchers have developed the i* framework enabling the evaluation and decomposition of multiple design opportunities. RUP/UML business use case semantics could be used more efficiently to integrate the latter benefits. [Principal ideas/results] Through a systematic mapping of elements from i* on the one side and of the RUP/UML business use case model on the other, we have set up a RUP/UML graphical notation for i* elements. Applicability has been shown on an illustrative example. [Contribution] The main contribution of the framework is allowing to model in an i* fashion using CASE-tools meant for RUP/UML and proposing an interface for forward engineering the produced model in a classical UML requirements model. Future work is required to fully validate the proposal, notably to measure the method’s efficacy.status: publishe

An Integrated Enterprise Modeling Framework Using the RUP/UML Business Use-Case Model and BPMN

Part 1: Regular PapersInternational audienceVarious frameworks are available for modeling an organizational setting. Their constituting models nevertheless mostly choose a particular decision level to represent perceived reality meaning that some introduce coarse-grained (i.e. abstract) elements and some others fine-grained (i.e. detailed) ones. Sometimes, in a same model, elements of various levels of granularity can be mixed like for example in the i* strategic rationale model. The main drawback is that this leads to hard to read and complex models, not ideal for easy and quick understanding of the software problem. Also, within the industry, poor unification in the use of models does exist. The various Unified Modeling Language (UML) models and the Business Process Model and Notation (BPMN) are nevertheless rather popular. In this paper, we study the use of the Business Use Case Model – an extension of the classical UML use-case model defined in the Rational Unified Process (RUP) – and the BPMN Business Process Model (BPM) as a unified framework for knowledge representation at strategic, tactical and operational levels. By default, the RUP advises to use UML activity diagrams for operational-level knowledge representation. Their main drawback is that they have been engineered to model software behavior with respect to the user and not business process modeling at large. The BPMN BPM thus offers more perspectives for pure business process modeling; that is why it mostly used in the industry for this purpose. The use of these models in a unified way is ensured by traceability at the various levels of modeling