class diagram

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.

Aspect-Oriented Modeling for Performance Evaluation with UML+MARTE, LQN, and CSM

Artifact Details
Author(s): 
Mohammad Alhaj, Dorina Petriu
Organization(s): 
Carleton University
Submitter's Name: 
Mohammad Alhaj
Artifact Description: 

The paper proposes a multi-paradigm modeling approach which aims to derive performance models from software models of enterprise SOA systems, in order to evaluate their run-time performance from the early development phases. This helps to choose between different architecture, design, and configuration alternatives in order to meet the performance requirements. The source models of the proposed transformation are the platform independent model of the service oriented system, the deployment diagram and the platform aspect models. The Performance completion feature model describes the variability in the service platform that may affect the system’s performance. It provides the choice to select between multiple platform alternatives based on the business requirements. Aspect-oriented modeling techniques are used to produce a platform-dependent model by weaving aspect models of platform operations into the platform-independent model. The platform-dependent model thus obtained represents the source models for the transformation into a performance model. The UML profile MARTE is used to annotate models with performance information.

Revision Summary: 
No revisions submitted.

bCMS case study models for OO-SPL approach

Artifact Details
Author(s): 
Paul Istoan
Organization(s): 
University of Luxembourg
Submitter's Name: 
Paul Istoan
Required Tool(s): 
MagicDraw v.16
Programming/Modeling Languages: 
UML
Artifact Description: 

UML models for the OO-SPL modeling of the bCMS case study

Revision Summary: 
No revisions submitted.

UML Class Diagram Patterns

Artifact Details
Author(s): 
Azzam Maraee, Mira Balaban, Arnon Strum, Adiel Ashrov
Organization(s): 
Ben Gurion University
Submitter's Name: 
Azzam Maraee
Programming/Modeling Languages: 
UML 2
Artifact Description: 

A catalog of modeling anti-patterns for problems of correctness and quality in class diagram design. It is developed by the BGU Modeling Group. The catalog accumulates knowledge regarding design problems by presenting them as patterns and classifying them into different categories based on the kind of problems they cover. The patterns of correctness problems characterize typical situations in which correctness problems arise, analyze the causes, and suggest possible solutions.

Revision Summary: 
No revisions submitted.
Syndicate content