Diagram Interchange Proposal

Slides:



Advertisements
Similar presentations
Diagram Definition: Revised Submission
Advertisements

Diagram Definition: an Overview Third OMG/Eclipse Symposium 25 March 2012 Maged Elaasar, Senior Software Engineer.
Language Specification using Metamodelling Joachim Fischer Humboldt University Berlin LAB Workshop Geneva
Profiles Construction Eclipse ECESIS Project Construction of Complex UML Profiles UPM ETSI Telecomunicación Ciudad Universitaria s/n Madrid 28040,
© 2008 by Borland Software Corp; made available under the EPL v1.0 | 17 March 2008 Introduction to the Graphical Modeling Framework Artem Tikhomirov, Borland.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 2, Modeling with UML, Part 4 UML 2 Metamodel.
SEG4110 – Advanced Software Design and Reengineering TOPIC D Metamodelling.
1 © Wolfgang Pelz UML3 UML 3 Notations describe how to use reusable software. Package Component Deployment Node.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 8 The Enhanced Entity- Relationship (EER) Model.
R R R CSE870: Advanced Software Engineering: Extending and Using UML (Cheng) Supplementary: Using and Extending UML.
Design Management: When Model Driven Engineering Embraces the Semantic Web NECSIS 2012, Gatineau, QC 27 June 2012 Maged Elaasar.
® Eurostep.ESUKPC v0.1©Copyright Eurostep Limited An Introduction to ISO STEP Part 25 David Price.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 8 The Enhanced Entity- Relationship (EER) Model.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
UML Diagrams Computer Science I.
An Approach and Tool for Synchronous Refactoring of UML Diagrams and Models Using Model-to-Model Transformations Hafsteinn Þór Einarsson Helmut Neukirchen.
SEG4110 – Advanced Software Design and Reengineering
Diagram Definition A Case Study with the UML Class Diagram MoDELS 2011, Wellington, NZ By Maged Elaasar 1,2 (Presenter) and Yvan Labiche.
Specializing and extending the UML
Ontologies Reasoning Components Agents Simulations Structural Modeling with UML2 Jacques Robin.
IBM Software Group ® Overview of SA and RSA Integration John Jessup June 1, 2012 Slides from Kevin Cornell December 2008 Have been reused in this presentation.
New ITS Investigation NHS CfH Research Report Grahame Grieve, Laura Sato, Charlie McCay.
Actors and Use Case Diagrams Month Day, Year. Agenda Training Plan Overview Review Detailing Requirements with Requisite Pro Concepts Setting Up XDE Integration.
Chapter 16 Applying UML and Patterns Craig Larman
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Advanced UML Class Diagrams.
NJIT UML Class Diagrams Chapter 16 Applying UML and Patterns Craig Larman.
® IBM Software Group © 2006 IBM Corporation Diagram Definition: Initial Submission Maged Elaasar, IBM ADTF, OMG June 2009, San Jose,
Object-Oriented Analysis and Design Feb 11, 2009.
Sheet 1 DocEng’03, Grenoble, November 2003 Model Driven Architecture based XML Processing Ivan Kurtev, Klaas van den Berg University of Twente, the Netherlands.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Abstract Classes. Review PA – 3 Design Considerations /Web/CS239/programs/pa3/draft.php ?harrisnlCS239
Graphical Modeling Framework (GMF) Richard C. Gronback Project Lead.
Copyright © IBM Corp., | March | Creating Robust Scalable DSLs with UML Tutorial (172) James Bruck, Christian Damus IBM Rational Software.
1 Class Diagrams. 2 Overview Class diagrams are the most commonly used diagrams in UML. Class diagrams are for visualizing, specifying and documenting.
Ontologies Reasoning Components Agents Simulations Architectural Modeling with UML2 Composite Structures and Components Jacques Robin.
® A Proposed UML Profile For EXPRESS David Price Seattle ISO STEP Meeting October 2004.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
All Presentation Material Copyright Eurostep Group AB ® A Meta-model of EXPRESS in UML for MOF and UML to EXPRESS David Price April 2002.
Class diagrams Terézia Mézešová.
October 1st 2015 Alexis Fouché 1, Florian Noyrit 1, Sébastien Gérard 1, Maged Elaasar 2 SYSTEMATIC GENERATION OF STANDARD COMPLIANT TOOL SUPPORT OF DIAGRAMMATIC.
Chapter 3: Introducing the UML
UML Profile BY RAEF MOUSHEIMISH. Background Model is a description of system or part of a system using well- defined language. Model is a description.
® IBM Software Group A Metamodeling Approach to Pattern Specification Maged Elaasar 1,2, Dr. Lionel Briand 1, Dr. Yvan Labiche 1 1 Carleton University,
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 2, Modeling with UML: UML 2 Metamodel Note to Instructor: The material in this.
Part 25 E2 EXPRESS/UML Walkthrough Seattle STEP October 2004.
SysML v2 Formalism Requirements Formalism WG September 15, 2016.
Language = Syntax + Semantics + Vocabulary
The Enhanced Entity- Relationship (EER) Model
Subgroup Chair: Robert Shapiro (Global360) Baseline Proposal:
UML Diagrams By Daniel Damaris Novarianto S..
SysML 2.0 Requirements for Visualization
SysML 2.0 Formalism Requirements and Potential Language Architectures
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Chapter 8: More About OOP and GUIs
SysML 2.0 Formalism: Requirement Benefits, Use Cases, and Potential Language Architectures Formalism WG December 6, 2016.
COMPONENT & DEPLOYMENT DIAGRAMS
SysML v2 Formalism: Requirements & Benefits
Syntactic Requirements
UML Diagrams Jung Woo.
Business Process Measures
IDEF1X Standard IDEF1X (Integrated Definition 1, Extended) was announced as a national standard in 1993 It defines entities, relationships, and attributes.
The Object Oriented Approach to Design
Model-Driven Ontology Engineering
Object Oriented Analysis and Design
Chapter 2, Modeling with UML, Part 4 UML 2 Metamodel
Domain Class Diagram Chapter 4 Part 2 pp
Class Diagrams.
An Introduction to Software Architecture
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Chapter 16 Class Diagrams.
Presentation transcript:

Diagram Interchange Proposal Maged Elaasar, IBM melaasar@ca.ibm.com

Proposed Diagram Interchange (DI) Diagram Interchange (DI) (replaces current DI) Provides an abstract metamodel that defines diagram interchange syntax Domains extend DI using inheritance to define domain specific DI Diagrams are interchanged as instances of the domain-specific DI MOF M3 spec DI M2 spec DSL DSL DI Model Diagram M1 user Abstract Syntax Diagram Syntax Is Instance of Inherits References

DI Metamodel - View Hierarchy Connector is owned by the lowest common parent of the source and target view (constraint) Connector’s source and target associations are uni-directional Waypoints are ordered and non unique

DI Metamodel – Style Sheet StyleRules are ordered MasterSheets are many and ordered StyleRule does not need explicit ‘type:Class’ association, since can be infered from ‘property.type’

UML Class Shape Example Diagram width x y Node height ratio Node showTitle collapsed visible ratio Node showTitle collapsed visible <Diagram xmi:id="1"> <definitions mxi:type="dd:DiagramDefinition" href="uml.definition#//ClassDiagram"/> <children mxi:id="2"> <definitions mxi:type="dd:NodeDefinition" href="uml.definition#//Class"/> <element xmi:type="uml:Class" href="model.uml#//..."/> <children xmi:id="3"> <definitions mxi:type="dd:NodeDefinition" href="uml.definition#//AttributeCompartment"/> <styles key="collapsed" value="true"/> <styles key="ratio" value=".25"/> </children> <children xmi:id="4"> <definitions mxi:type="dd:NodeDefinition" href="uml.definition#//OperationCompartment"/> <styles key="showTitle" value="true"/> <styles key="ratio" value=".75"/> <sourceConnectors href="8"/> <styles key="x" value="100"/> <styles key="y" value="200"/> <styles key="fillColor" value="0x00FF000000"/> <children mxi:id="5"> <children xmi:id="6"> <children xmi:id="7"> <targetConnectors href="8"/> <styles key="x" value="300"/> <connectors mxi:id="8"> <definitions mxi:type="dd:ConnectorDefinition" href="uml.definition#//Generlization"/> <element xmi:type="uml:Generalization" href="model.uml#//..."/> <source xmi:type="di:Node" href="2"/> <target xmi:type="di:Node" href="5"/> <bendpoints x="50" y="10"/> <bendpoints x="100" y="200"/> <styles key="lineColor" value="0x0000FF0000"/> </connectors> </Diagram>

UML Association and Interface Realization Connector Node Node offset offset Node offset Node Node offset offset Connector

UML DI Metamodel – View Hierarchy Two subtypes of Compartment for UML : List Compartment and Diagram comparemtment Diagram’s umlShape and umlConnector are derived unions subsetting child and connector, respectively How do we make the Diagram.child collection ordered (needed for z-order)?

UML DI Metamodel – Common Views

UML DI Metamodel – Class Diagram

UML DI Metamodel – Class Diagram Shapes

UML DI Metamodel – Class Diagram Connectors

DI More Abstractions Try to have a crack at it but it is not critical (not show stopper) Could define them as concrete to allow creating adhoc diagrams Define common properties as mixin types in separate DI packages

DI Extensibility Profiles Allow subsetting, redefinition of base properties in stereotypes Clarify what types other than stereotypes are allowed in profiles and what it means What DD needs to do to get access to profiles (package merge?)

Proposed Diagram Graphics Diagram Graphics (DG) Provides an abstract metamodel that defines diagram graphics syntax Provides a way to map the abstract syntax (DSL+DI) to the graphical syntax (DG) Domains extend DG to create domain specific DG and its mapping from their DSL+DI DI DG Mapping DG Graphics DSL Model (abstract syntax) Controller (mapping) View (concrete syntax)

Proposed Diagram Definition Architecture Diagram Graphics (DG) Provides an abstract metamodel that defines diagram graphics syntax and how it maps to the abstract syntax (DSL+DI) Domains extend DG to create domain specific DG metamodel MOF M3 spec DI DG M2 spec DSL DSL DI DSL DG Rendered Graphics Model Diagram M1 user Is Instance of Abstract Syntax Diagram Syntax Diagram Graphics Inherits References Uses

Diagram Graphics (DG) – Declarative Graphics Class Diagram Figure width x y Classifier Figure [*] Node Stereotype Label Figure [1] height Name Label Figure [1] ratio Node showTitle collapsed visible Package Label Figure [1] Attribute Compartment Figure [1] Title Label Figure [1] ratio Node List Container Figure [1] showTitle collapsed visible Label Figure [*] Operation Compartment Figure [1] Title Label Figure [1] List Container Figure [1] Label Figure [*]

Diagram Graphics (DG) – Declarative Map Model (abstract syntax) Controller (map) View (concrete syntax)