Model

Demo Artifact

Author(s): 
Andrew Jacobson
Organization(s): 
CSU
Artifact Types: 

Downloads

Keywords: 
Artifact Development Contexts: 
Required Tool(s): 
Eclipse, Papyrus
Programming/Modeling Languages: 
UML
Artifact Description: 

A dummy artifact for the Eclipse plugin demo

Revision Summary: 
No revisions submitted.

Case Studies for Validation of a UML/OCL Approach for Service-Oriented Applications

Author(s): 
Loli Burgueno, Martin Gogolla, Antonio Vallecillo
Organization(s): 
University of Malaga, University of Bremen, University of Malaga
System/Software Domains: 
Modeling Languages/Notations: 
Required Tool(s): 
USE (UML-based Specification Environment) https://sourceforge.net/projects/useocl/; YEd (yet another graph Editor) https://www.yworks.com/products/yed
Programming/Modeling Languages: 
UML OCL SOIL
Artifact Description: 

The case studies have been developed in order to explain and validate an approach for service-oriented applications. Research papers explaining the approach are available from the authors.

Revision Summary: 
No revisions submitted.

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.

Artifact to paper 'Partial Evaluation of OCL Expressions', to appear in Proceedings of MODELS'17

Author(s): 
Bastian Ulke^1, Friedrich Steimann^1 and Ralf Lämmel^2
Organization(s): 
1 FernUniversitat in Hagen; 2 Universitat Koblenz-Landau
Modeling Languages/Notations: 
Artifact Types: 
Artifact Development Contexts: 
Required Tool(s): 
see README files.
Programming/Modeling Languages: 
Ecore, Java, OCL
Artifact Description: 

Partial Evaluation of OCL Expressions
Bastian Ulke, Friedrich Steimann and Ralf Lämmel

Abstract (taken from the paper) -- In the academic literature, many uses of the Object Constraint Language (OCL) have been proposed. By contrast, the utilization of OCL in contemporary modelling tools lags behind, suggesting that leverage of OCL remains limited in practice. We consider this undeserved, and present a scheme for partially evaluating OCL expressions that allows one to capitalize on given OCL specifications for a wide array of purposes using a single implementation: a partial evaluator of OCL.

In this context, our artifact delivers the following contributions:

  1. it presents a Java-based partial evaluator for OCL invariants. The partial evaluator evaluates OCL subexpressions where their value is fix and translates them to a constraint on variables where they are not (the genrated constraints can be solved by a constraint solver to find value assignments satisfying the invariants, thus repairing or completing a model instance; refer to section II for more details).
  2. The artifact comprises a text-based user interface to illustrate the constraint generation based on a user-specified set of dynamic and fix properties.
  3. The same interface can be used to reproduce the results of the implementation evaluation (please refer to section IX of our paper for further details).
  4. Our artifact also publishes the models and OCL invariants that were used for the evaluation.

The artifact consists consists of three parts:

  1. The metamodel for Java/JPA programs and 14 instances, constructed from Open Source projects, as well as the 77 OCL expressions reflecting JPA's rules of well-formedness.
    (Paper65_Models.zip)
  2. A Java SE-based setup of our Java-based OCL partial evaluator. This application can be used to reproduce evaluation results presented in our paper and to get an impression of the complexity reduction achieved by partially evaluating OCL expressions.
    (Paper65_PartEval.zip)
  3. A virtual machine, comprising a preconfigured Eclipse workspace to inspect the implementation of our partial evaluator for OCL. (Depending on your system configuration, you may want to ensure that the VM is set up to run an "Ubuntu (64 bit)" operating system.)
    (URL: https://figshare.com/s/0d0ec7567d12ac45c253)

All three parts contain own README files with further details on their usage.

Terms of use
In case you use parts of this artifact for your own research, please cite our publication in your work.

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.

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.

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.

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.

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.

Pages