You are here

Workshop/Focus Group

Integrating modeling and programming languages - The case of Java and fUML (case study models)

Author(s): 
Patrick Neubauer
Organization(s): 
Vienna University of Technology
Modeling Languages/Notations: 
System/Software Domains: 
Artifact Development Contexts: 
Artifact Types: 
Required Tool(s): 
- Eclipse Kepler (Modeling Tools distribution) - fUML Library Support projects (see: https://github.com/patrickneubauer/fuml-library-support) In case Java library reverse engineering is desired: a reverse engineering tool of choice (e.g., Jar2UML Eclipse plugin).
Programming/Modeling Languages: 
UML 2 and Java 6.
Artifact Description: 

- UML class models representing the reverse engineered Java libraries
- UML activity models representing the modeled activities referencing the reverse engineered Java libraries

Revision Summary: 
No revisions submitted.

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

Author(s): 
Shuai Wang, Shaukat Ali
Organization(s): 
Certus Software V&V Center, Simula Research Laboratory
Modeling Languages/Notations: 
Artifact Development Contexts: 
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

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.

Coloured Petri Net Model of the bCMS system using CPN Tools

Author(s): 
Isabel Sofia Sousa Brito, João Paulo Barros
Organization(s): 
Polytechnic Institute of Beja
Lifecycle Phases: 
Modeling Languages/Notations: 
Artifact Types: 
Artifact Development Contexts: 
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

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.

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

Author(s): 
Marco Aurelio Wehrmeister
Organization(s): 
Federal University of Technology - Parana (UTFPR)
Modeling Languages/Notations: 
Lifecycle Phases: 
Artifact Development Contexts: 
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)

Author(s): 
Florian Schneider
Organization(s): 
Technische Universität München
Modeling Languages/Notations: 
Lifecycle Phases: 
Artifact Development Contexts: 
Artifact Types: 
Required Tool(s): 
Web Browser
Programming/Modeling Languages: 
URML
Revision Summary: 
No revisions submitted.

Multi-models to aid Decision Making in Enterprises

Author(s): 
Suman Roychoudhury, Asha Rajbhoj, Vinay Kulkarni, Deepali Kholkar
Organization(s): 
Tata Consultancy Services
Artifact Types: 
System/Software Domains: 
Lifecycle Phases: 
Modeling Languages/Notations: 
Artifact Development Contexts: 
Required Tool(s): 
OpenOME (http://sourceforge.net/projects/openome/ ) , iThink Software ( http://www.iseesystems.com/softwares/Business/ithinkSoftware.aspx) , Anylogic ( http://www.anylogic.com/downloads )
Artifact Description: 

Intentional Model , System Dynamic Model , Agent based model

Revision Summary: 
No revisions submitted.

Pages

Subscribe to RSS - Workshop/Focus Group