Workshop/Focus Group

Modeling Specification for bCMS Product Line using Feature Model, Component Family Model and UML

Artifact Details
Author(s): 
Shuai Wang, Shaukat Ali
Organization(s): 
Certus Software V&V Center, Simula Research Laboratory
Submitter's Name: 
Shuai Wang
Required Tool(s): 
Pure::Variants, Rational Software Architect (RSA)
Programming/Modeling Languages: 
Feature model, Component Family Model and UML
Artifact Description: 

This document presents the whole models for bCMS product line, i.e., UML behavioral model repository, Feature Model for bCMS product line and Component Family Model for bCMS product line. Afterwards, an example is shown for configuring a variant.

Revision Summary: 
No revisions submitted.

Modeling Car Crash Management with KAOS

Artifact Details
Author(s): 
Antoine Cailliau, Christophe Damas, Bernard Lambeau, and Axel van Lamsweerde
Organization(s): 
Université catholique de Louvain
Submitter's Name: 
Antoine Cailliau
Programming/Modeling Languages: 
KAOS
Revision Summary: 
No revisions submitted.

Coloured Petri Net Model of the bCMS system using CPN Tools

Artifact Details
Author(s): 
Isabel Sofia Sousa Brito, João Paulo Barros
Organization(s): 
Polytechnic Institute of Beja
Submitter's Name: 
Isabel Sofia Sousa Brito
Required Tool(s): 
CPN Tools
Programming/Modeling Languages: 
Coloured petri nets and Standard ML.
Artifact Description: 

The presented model was constructed as a high-level specification of the bCMS system using CPN Tools. Then, we have shown how non-functional requirements can be added. In particular, the use of timed CPN models can offer a further level of specification towards the creation of more detailed executable prototypes.

Revision Summary: 
No revisions submitted.

Behavior as-is and to-be and Goal-Belief models

Artifact Details
Author(s): 
George Popescu
Organization(s): 
École Polytechnique Fédérale de Lausanne
Submitter's Name: 
George Popescu
Programming/Modeling Languages: 
SeamCAD v. 3.5.10 and 4.0.17
Artifact Description: 

Complete SEAM models: Behavior as-is, Behavior to-be, Witness Goal-Belief, Complete Goal-Belief.

Revision Summary: 
No revisions submitted.

bCMS Case Study: FAMILIAR

Artifact Details
Author(s): 
Philippe Collet
Organization(s): 
Université Nice Sophia Antipolis
Submitter's Name: 
Philippe Collet
Required Tool(s): 
Familiar v1.0.7 or upper: https://github.com/FAMILIAR-project/familiar-documentation/tree/master/installation
Programming/Modeling Languages: 
Feature Modeling with Familiar
Artifact Description: 

This artifact is two-fold: 1. The pdf report is the companion document to the paper presenting FAMILIAR as a feature-oriented approach to requirement and design modeling. It contains descriptions of input files, FAMILIAR scripts and results while illustrating the approach. The bCMS-SPL variability is captured and organized with scripts. It is also related to some technical variabilities of a supposed J2EE platform. 2. All FAMILIAR scripts and input files of this case study, which can be replayed by the FAMILIAR tool.

Revision Summary: 
No revisions submitted.

Using AMoDE-RT and DERAF to specify a Crisis Management System -- Complete Model Description

Artifact Details
Author(s): 
Marco Aurelio Wehrmeister
Organization(s): 
Federal University of Technology - Parana (UTFPR)
Submitter's Name: 
Marco Aurelio Wehrmeister
Required Tool(s): 
Magic Draw modeling tool
Programming/Modeling Languages: 
UML, MARTE, DERAF
Artifact Description: 

Complete description of the Car Crisis Management System case study performed using AMoDE-RT approach and DERAF aspects framework.

URML Model of bCMS (HTML Export)

Artifact Details
Author(s): 
Florian Schneider
Organization(s): 
Technische Universität München
Submitter's Name: 
Florian Schneider
Required Tool(s): 
Web Browser
Programming/Modeling Languages: 
URML
Revision Summary: 
No revisions submitted.

Applying BPMN on bCMS

Artifact Details
Author(s): 
Muhammad Atif Qureshi
Organization(s): 
University of Technology Sydney
Submitter's Name: 
Muhammad Atif Qureshi
Revision Summary: 
No revisions submitted.

Updated Activity Theory bCMS Model Description for CMA-2012

Artifact Details
Author(s): 
Geri Georg
Organization(s): 
Colorado State University
Submitter's Name: 
Geri Georg
Artifact Description: 

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.

Revision Summary: 
No revisions submitted.

Concern-Driven Development with AoURN and RAM

Artifact Details
Author(s): 
Omar Alam^1, Matthias Schöttle^1, Gunter Mussbacher^2, Jörg Kienzle^1
Organization(s): 
1) McGill University 2) Carleton University
Submitter's Name: 
Gunter Mussbacher
Programming/Modeling Languages: 
Aspect-oriented User Requirements Notation (AoURN), Reusable Aspect Models (RAM)
Artifact Description: 

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).

Revision Summary: 
No revisions submitted.
Syndicate content