class diagram

MODELS2017-BPMN2UML Artifacts

Author(s): 
Qusai Ramadan^1, Mattia Salnitriy^2, Daniel Strüber^1, Jan Jürjens^1 and Paolo Giorginiy^2
Organization(s): 
1 University of Koblenz-Landau, 2 University of Trento
Modeling Languages/Notations: 
System/Software Domains: 
Artifact Development Contexts: 
Required Tool(s): 
We recommend using Eclipse Neon, Modeling Tools distribution (https://www.eclipse.org/downloads/packages/eclipse-modeling-tools/neonr), with installed Henshin(https://www.eclipse.org/henshin/) and CARiSMA (https://rgse.uni-koblenz.de/carisma/) plug-ins. These plug-ins can be installed either using online update sites, or the mirrored update sites provided as part of the artifact. More details about how to install these softwares are provided in the README file.
Programming/Modeling Languages: 
For people who are interested in viewing the SecBPMN2 Models or UMLsec models, we recommended the use of the following tools. However, this is not an obligation, our project still can be executed without having these tools. For viewing the SecBPMN2 models, please install STS-Tool. For viewing the UMLsec models, please install Papyrus on your Eclipse. More details about how to install these software are provided in the README file.
Artifact Description: 

The Eclipse project package *myexample.zip* has the following contents:
src/my.example* directory:

  • Externalservices1.bpmn, Externalservices2.bpmn, Flightplan.bpmn, Landing.bpmn: Input models from the ATM case study
  • example1.bpmn: Small input model for testing purposes
  • .henshin files: Henshin modules implementing the transformation
  • BpmnToUml.java: Java class for executing the transformation via orchestration of Henshin modules
  • BpmnToUmlMetricsPrinter.java: Java class for computing metric values for input and output models

Testing directory: Additional test input models

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.

Toward a Megamodeling Approaches Overview

Author(s): 
Ralf Lämmel^1, Vadim Zaytsev^2
Organization(s): 
1 Universität Koblenz-Landau, 2 Universiteit van Amsterdam
System/Software Domains: 
Modeling Languages/Notations: 
Artifact Development Contexts: 
Required Tool(s): 
Adobe Reader
Programming/Modeling Languages: 
UML, MEGAF, MegaL and other structured, unstructured and semi-structured languages for megamodelling
Artifact Description: 

This is an attempt to collect technology models (commonly referred to as megamodels or macromodels) used in recent academic peer-reviewed publications for explaining and/or analysing software languages and software technologies.

Revision Summary: 
No revisions submitted.

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.

uml-profile-store

Author(s): 
Alexander Bergmayr
Organization(s): 
Vienna University of Technology
Modeling Languages/Notations: 
Artifact Development Contexts: 
Artifact Types: 
Required Tool(s): 
Modeling Tool with UML2 support including UML Profiles
Programming/Modeling Languages: 
UML2
Artifact Description: 

UML profiles generated from annotation-based Java libraries / frameworks

Revision Summary: 
No revisions submitted.

OpenStack Model

Author(s): 
Lukman Rahim
Organization(s): 
Unviersiti Teknologi PETRONAS
Lifecycle Phases: 
System/Software Domains: 
Artifact Types: 
Modeling Languages/Notations: 
Artifact Development Contexts: 
Required Tool(s): 
StarUML 5.0.2.1570
Programming/Modeling Languages: 
UML
Artifact Description: 

Class diagram of OpenStack

Revision Summary: 
No revisions submitted.

Class diagram of OpenNebula

Author(s): 
Lukman Rahim
Organization(s): 
Unviersiti Teknologi PETRONAS
Lifecycle Phases: 
System/Software Domains: 
Artifact Types: 
Modeling Languages/Notations: 
Artifact Development Contexts: 
Required Tool(s): 
ArgoUML
Programming/Modeling Languages: 
UML
Artifact Description: 

A class diagram showing the design of OpenNebula

Revision Summary: 
No revisions submitted.

How Could Ancient Romans Know About UML Statecharts?

Author(s): 
Martin Gogolla
Organization(s): 
University of Bremen
Artifact Types: 
Modeling Languages/Notations: 
Artifact Development Contexts: 
Required Tool(s): 
USE 3.1.0, JFLAP, yEd
Programming/Modeling Languages: 
UML, OCL
Artifact Description: 

How Could Ancient Romans Know About UML Statecharts?

Revision Summary: 
No revisions submitted.

Modeling the Architecture and Design of the Crisis Management System Product Line Using SimPL

Author(s): 
Kunming Nie^1, Tao Yue^2, Shaukat Ali^2
Organization(s): 
1 Beihang University, 2 Simula Research Laboratory
System/Software Domains: 
Lifecycle Phases: 
Modeling Languages/Notations: 
Artifact Types: 
Artifact Development Contexts: 
Required Tool(s): 
IBM Rational Software Architect
Programming/Modeling Languages: 
UML
Artifact Description: 

The artifact is an emx file containing a model capturing the system architecture and design, and variabilities of an extended crisis management system product line. The model is specified using the SimPL methodology, which is based on UML class diagram with extended functionality of specifying and organizing variation points.

Revision Summary: 
No revisions submitted.

Concern-Driven Development with AoURN and RAM

Author(s): 
Omar Alam^1, Matthias Schöttle^1, Gunter Mussbacher^2, Jörg Kienzle^1
Organization(s): 
1) McGill University 2) Carleton University
System/Software Domains: 
Artifact Types: 
Keywords: 
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.

Pages