Master Thesis: UML2 Sequence Diagram Editor for the ViPER Platform

1
Master Thesis UML2 Sequence Diagram Editor for
the ViPER Platform

• Presented by
• M. Tauseef Ikram

2
Outline

• Introduction
• Tools and Technologies
• Technical
• EMF
• GEF
• ViPER
• Conceptual
• UML2 Specification for Interaction Diagrams
• Communication Diagram
• Sequence Diagram
• Current Status and Future Work
• Software Demonstration For Communication Diagram
  Editor

3
Introduction

• Based on enhancement of ViPER platform
• Adding visual modeling capabilities for UML2
  interaction (communication and sequence) diagrams
  
• Main tasks are
• In depth understanding of tools and technologies
  involved.
• GEF, EMF, ViPER.
• Specification of UML2 Interaction Diagrams
• Design and development of editors as a plugin to
  ViPER for the following diagrams
• Communication Diagram
• Sequence Diagram
• A detailed Thesis report comprising of the study
  conducted and results achieved.

4
Tools And Technologies EMF

• EMF stands for Eclipse Modeling Framework.
• A java framework providing code generation
  facility for structured models.
• Uses XMI(XML Metadata Interchange) as model
  definition from
• Models need to be translated to XMI.
• Consists of two frameworks
• The core EMF framework
• EMF.Edit framework
• EMF.Codegen

5
Tools and Technologies EMF

• EMF Core Framework
• Provides basic support for creating Java Classes
  corresponding to a model.
• Meta Model to describe Models
• Change Notification
• Persisitance Support
• API to manipulate EMF Objects
• EMF.Edit Framework
• Built on and extends core framework.
• Generate adapter classes to create editors for
  EMF Models.
• Content and Label provider classes
• Desktop viewers(JFace)
• Property Sheets
• Command Framework
• Undo
• Eidt
• Redo

6
Tools and Technologies GEF

• GEF stands for Graphical Editing Framework.
• Provides the facility to display and edit a model
  graphically.
• Provides GEF viewers for this purpose.
• Based on Model-View-Controller (MVC)
  architecture.

Figure 1 MVC Architecture
7
Tools and Technologies ViPER
8
Tools and Technologies ViPER

• ViPER builds upon Eclipse, EMF, UML2, and GEF

9
Tools and Technologies ViPER

• ViPER UML2 VME (Visual Modeling Environment)
  supports visual modeling of followinf diagrams
• Structure diagrams (ViPER UML2 VME Structure)
• ViPER UML2 VME Class
• ViPER UML2 VME Object
• ViPER UML2 VME Package
• ViPER UML2 VME CompositeStructure
• ViPER UML2 VME Component
• Behavior diagrams (ViPER UML2 VME Behavior)
• ViPER UML2 VME UseCase
• ViPER UML2 VME StateMachine
• ViPER UML2 VME Communication
• ViPER UML2 VME Sequence

10
UML2 Specification

• For a better grip of an interactive situation.
• Produced at a detailed design phase.
• Suitable to design precise inter-process
  communication.
• Interactions can be designed using the following
  diagrams
• Sequence Diagram
• Communication Diagram

11
UML2 Specification
12
UML2 Specification

• There are some basic components of an interaction
  diagram
• Interaction
• Lifeline
• Message
• OccurrenceSpecification
• Events
• Behavior Executions

13
UML2 Interaction
14
UML2 Lifeline Class Description

• Description
• A specialization of NamedElement
• Represents an individual participant in the
  interaction
• Associations
• selector ValueSpecification0..1
• interaction Interaction1
• represents ConnectableElement0..1
• decomposedAs PartDecomposition0..1
• coveredBy InteractionFragment 0..1
• Notation
• ltlifelineidentgt (ltconnectable-element-namegt
  ltselectorgt ltclass_namegt
  decomposition) self ltselectorgt
  ltexpressiongt
• ltdecompositiongt ref
  ltinteractionidentgt strict
• Changes From Previous UML
• Same as UML 1.x

15
UML2 Lifeline
16
UML2 Message Class Description

• Description
• A particular communication between Lifelines of
  an interaction
• Specifies kind of communication, sender and
  reciever.
• Attributes
• messageKind MessageKind
• messageSort MessageSort
• Associations
• interactionInteraction1
• sendEvent MessageEnd0..1
• receiveEvent MessageEnd0..1
• connector Connector0..1
• argumentValueSpecification
• /signatureNamedElement0..1
• Notation
• ltmessageidentgt (ltattributegt
  ltsignal-or-operation-namegt ( ltargumentgt
  ,ltargumentgt ) ltreturn-valuegt)
  ltargumentgt (ltparameter-namegt ''
  ltargument-valuegt) (ltattributegt ''
  ltout-parameter-namegt '' ltargument-valuegt ) '
  -'
• Changes From Previos UML
• May have gates on either end

17
UML2 Message
18
UML2 Event
19
UML2 OccurenceSpecification Class Description

• Description
• Basic semantic unit of an interaction
• Ordered along a lifeline
• Associations
• event Event 1
• covered Lifeline1
• toBeforeGeneralOrdering
• toAfter GeneralOrdering
• Has 2 specializations
• MessageOccurenceSpecification
• ExecutionOccurenceSpecification

20
UML2 OccurenceSpecification
21
UML2 MessageOccurenceSpecification Class
Description

• Description
• Specifies occurence of events like,
• Sending and recieving of signals
• Invoking or recieving of operation calls
• Is a kind of message end.
• Associations
• event Event 1
• Changes from Previous UML
• Now in UML 2.0

22
UML2 ExecutionOccurenceSpecification Class
Description

• Description
• represents moments in time at which actions or
  behaviors start or finish.
• Associations
• event ExecutionEvent 1
• execution ExecutionSpecification 1
• Changes from Previous UML
• Now in UML 2.0

23
UML2 BehaviorExecutionSpecification Class
Description

• Description
• Specialization of ExecutionSpecification
• represents execution of behavior
• Associations
• behavior Behavior 0..1
• Rationale
• introduced to support interactions specifying
  messages that result from behaviors

24
Current Status and Future Work

• Current Status
• Communication Diagram Editor implemented
• Future Work
• Implementation of Sequence Diagram Editor
• Report Writing

25
Thank You

• Questions are welcome !