You are here

Domain Analysis

Collaborative modeling environment features

Author(s): 
Constantin Masson, Jonathan Corley, Eugene Syriani
Organization(s): 
Université de Montréal, University of West Georgia
Modeling Languages/Notations: 
Lifecycle Phases: 
Artifact Types: 
Artifact Development Contexts: 
Required Tool(s): 
Image viewer
Programming/Modeling Languages: 
Feature Modeling
Artifact Description: 

There has been a growing trend toward collaborative environments especially those utilizing browser-based interfaces which can be seen in modeling tools such as AToMPM and WebGME. In response to the growing interest in collaborative modeling, we explored existing systems and potential solutions to identify the various features relevant to collaborative modeling systems. In this paper, we detail the feature diagram resulting from our exploration of collaborative modeling systems. We also detail the features of an existing collaborative system both to illustrate the use of the diagram and further explore the features. Through this feature diagram we identify key areas for collaborative modeling systems. We hope the feature diagram will be used to guide development, analysis, and discussion around collaborative modeling systems.

Revision Summary: 
No revisions submitted.

UML Models Generated and Derived for Evaluating aToucan

Author(s): 
Tao Yue
Organization(s): 
Simula Research Laboratory
Lifecycle Phases: 
System/Software Domains: 
Artifact Development Contexts: 
Artifact Types: 
Required Tool(s): 
IBM RSA and Word
Programming/Modeling Languages: 
UML
Artifact Description: 

It contains the models derived by the participants of two controlled experiments conducted to evaluate aToucan. It also contains models generated by the aToucan for a number of case studies including ATM, Elevator. References models are also included in this package.

Revision Summary: 
No revisions submitted.

Renarrating Metalanguage Integration

Author(s): 
Vadim Zaytsev
Organization(s): 
Universiteit van Amsterdam
System/Software Domains: 
Modeling Languages/Notations: 
Artifact Development Contexts: 
Required Tool(s): 
Adobe Reader
Programming/Modeling Languages: 
Ad hoc categorical-style diagram
Artifact Description: 

An example of use for the "parsing in a broad sense" megamodel that we are presenting this year at MoDELS: four technology-specifc renarrations.

Revision Summary: 
No revisions submitted.

Modeling Car Crash Management with KAOS

Author(s): 
Antoine Cailliau, Christophe Damas, Bernard Lambeau, and Axel van Lamsweerde
Organization(s): 
Université catholique de Louvain
Modeling Languages/Notations: 
Artifact Types: 
Keywords: 
Artifact Development Contexts: 
Programming/Modeling Languages: 
KAOS
Revision Summary: 
No revisions submitted.

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

Author(s): 
George Popescu
Organization(s): 
École Polytechnique Fédérale de Lausanne
System/Software Domains: 
Artifact Types: 
Modeling Languages/Notations: 
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

Author(s): 
Philippe Collet
Organization(s): 
Université Nice Sophia Antipolis
System/Software Domains: 
Modeling Languages/Notations: 
Artifact Types: 
Keywords: 
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.

Requirements Modeling in SEAM: The Example of a Car Crash Management System

Author(s): 
George Popescu
Organization(s): 
École Polytechnique Fédérale de Lausanne
System/Software Domains: 
Modeling Languages/Notations: 
Artifact Development Contexts: 
Programming/Modeling Languages: 
SeamCAD
Artifact Description: 

Requirements Modeling in SEAM: The Example of a Car Crash Management System - CMA@RE paper

Revision Summary: 
No revisions submitted.

Applying BPMN on bCMS

Author(s): 
Muhammad Atif Qureshi
Organization(s): 
University of Technology Sydney
Modeling Languages/Notations: 
Artifact Types: 
Artifact Development Contexts: 
Revision Summary: 
No revisions submitted.

The VCL Model of the Barbados Crisis Management System

Author(s): 
Nuno Amálio
Organization(s): 
University of Luxembourg
System/Software Domains: 
Lifecycle Phases: 
Modeling Languages/Notations: 
Artifact Types: 
Keywords: 
Required Tool(s): 
The 'Visual Contract Builder' (http://vcl.gforge.uni.lu/)
Programming/Modeling Languages: 
VCL
Artifact Description: 

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.

Revision Summary: 
No revisions submitted.

CMA12 - CMS Domain- i* - Group 6

Author(s): 
Jennifer Horkoff
Organization(s): 
University of Trento
Modeling Languages/Notations: 
Lifecycle Phases: 
Artifact Types: 
Keywords: 
Artifact Development Contexts: 
Required Tool(s): 
OpenOME
Programming/Modeling Languages: 
i*
Artifact Description: 

Final submission to CMA'12, Modeling of CMS Domain in i*

Revision Summary: 
No revisions submitted.

Pages

Subscribe to RSS - Domain Analysis