ReMoDD The Repository for Model-Driven Development

Models describing the use of Activity Theory in modeling the high level requirements of the bCMS system. Includes description of transformation (using heuristics) to URN models. Used in the CMA workshop at MODELS 2012. Also includes initial metamodel of a proposed DSL.

The submitted models apply the the Concern-Oriented Reuse (CORE) approach to the bCMS case study. CORE is a concern-oriented, model-driven software development approach for reactive systems that covers the early requirements, late requirements, high-level and low-level design phases of software development. It is based on two aspect-oriented modelling notations: the Aspect-Oriented User Requirements Notation (AoURN) and Reusable Aspect Models (RAM).

This document presents the VCL model of the barbados Crisis Management System. It is a submission for the Comparing Modelling Approaches workshop an event of the Models 2012 conference.

The paper proposes a multi-paradigm modeling approach which aims to derive performance models from software models of enterprise SOA systems, in order to evaluate their run-time performance from the early development phases. This helps to choose between different architecture, design, and configuration alternatives in order to meet the performance requirements. The source models of the proposed transformation are the platform independent model of the service oriented system, the deployment diagram and the platform aspect models. The Performance completion feature model describes the variability in the service platform that may affect the system’s performance. It provides the choice to select between multiple platform alternatives based on the business requirements. Aspect-oriented modeling techniques are used to produce a platform-dependent model by weaving aspect models of platform operations into the platform-independent model. The platform-dependent model thus obtained represents the source models for the transformation into a performance model. The UML profile MARTE is used to annotate models with performance information.

Comparison criteria document for bCMS models of CMA workshop

Defines the requirements of a Software Product Line called bCMS-SPL including a reference variant.

This submission contains 14 high and low-level design models of parts of a single bCMS system using the Reusable Aspect Models approach (RAM). The included aspects are:

• Command
• Copyable
• Crisis
• FireStation
• Locatable
• Map
• Named
• NetworkedCommand
• PoliceStation
• RoutePlanning
• Singleton
• SocketCommunication
• Vehicle
• VirtualSharedData

UML models for the OO-SPL modeling of the bCMS case study

This Artifact is the PDF description of a model for the Comparing Modeling Approaches workshop. It presents the cloud component model and a Model for Variability of Refinement Processes used to model the bCMS-SPL use case. Our targets are high-level and architectural design, and evolution. Runtime support will be tackled, but is not in the main focus of this contribution. We introduce:
- A single system: on the basis of a custom component model, the cloud component model. The latter is dedicated to the modeling of distributed applications.
- The whole SPL: on the basis of an MDE refinement process model that has the property of being variable. Its specification is inspired by previous works on refinement and feature models dedicated to provide adaptation capabilities to component-based architectures.

The Object-Oriented Modeling (OOM) approach is used for developing the model of the focused case study i.e. Crises Management System. Our approach targets the requirements specification and design phase of the software development process. We choose to focus on the single system i.e. bCMS.
The method uses UML 2 collaborations for service structure and activity diagrams for both global behaviour (choreography) and local component behaviour (orchestration). The behaviour of each system component is designed as a composition of the roles it plays in different services.