Comparing UML 2.0 Interactions and MSC-2000

Slides:



Advertisements
Similar presentations
System and Software Engineering Research 1 Motorola 2003 Integrated Application of MSC Clive Jervis Rapporteur Q15 Motorola UK Research Labs.
Advertisements

Profiles Construction Eclipse ECESIS Project Construction of Complex UML Profiles UPM ETSI Telecomunicación Ciudad Universitaria s/n Madrid 28040,
1 CIS224 Software Projects: Software Engineering and Research Methods Lecture 11 Brief introduction to the UML Specification (Based on UML Superstructure.
Restricted © Siemens AG All rights reserved Siemens Corporate Technology | Month 20XX Proposed topics for TDL phase 3.
IT Requirements Capture Process. Motivation for this seminar Discovering system requirements is hard. Formally testing use case conformance is hard. We.
A Brief Introduction. Acknowledgements  The material in this tutorial is based in part on: Concurrency: State Models & Java Programming, by Jeff Magee.
Solutions to Review Questions. 4.1 Define object, class and instance. The UML Glossary gives these definitions: Object: an instance of a class. Class:
R R R CSE870: Advanced Software Engineering: Extending and Using UML (Cheng) Supplementary: Using and Extending UML.
Using UML Models for the Performance Analysis of Network Systems Nico de Wet and Pieter Kritzinger Department of Computer Science University of Cape Town.
PPL Syntax & Formal Semantics Lecture Notes: Chapter 2.
State and Sequence Diagrams Modelling dynamic information So far we have seen: Use Case Diagrams – requirements capture, interface.
The Software Development Life Cycle: An Overview
CS3773 Software Engineering
Workshop on Integrated Application of Formal Languages, Geneva J.Fischer Mappings, Use of MOF for Language Families Joachim Fischer Workshop on.
Business Modeling : basic concepts Extracted from Rational UML Profile for business modeling.mht.
UML / UML 2.0 Diagrams (Part III) 1. Sequence diagram is the most common kind of interaction diagram. It focuses on the message interchange between a.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 11, Testing: Model-based Testing.
Chapter 2, Modeling with UML: UML 2 Hightlights
Documenting Software Architectures 1.Uses and Audiences for Architecture Documentation Architecture documentation serves as a means of education Architecture.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
Automata Based Method for Domain Specific Languages Definition Ulyana Tikhonova PhD student at St. Petersburg State Politechnical University, supervised.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
1 Class Diagrams. 2 Overview Class diagrams are the most commonly used diagrams in UML. Class diagrams are for visualizing, specifying and documenting.
A division of Data Access Technologies, Inc. Combining Alf and UML in Modeling Tools Ed Seidewitz, Model Driven Solutions Jérémie Tatibouet, CEA 28 September.
1 Software Design Lecture What’s Design It’s a representation of something that is to be built. i.e. design  implementation.
Modeling the ODP Computational Viewpoint with UML 2.0: The Templeman Library Example José Raúl Romero, Antonio Vallecillo Universidad de Málaga, Spain.
FDT Foil no 1 MSC Structuring MSCs Using Message Sequence Charts for real systems.
Chapter 16 UML Class Diagrams.
1. 2 Purpose of This Presentation ◆ To explain how spacecraft can be virtualized by using a standard modeling method; ◆ To introduce the basic concept.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
Slide no. 1  =====!"§!“!Nova§ ITU-T work on technical languages and general software issues Amardeo Sarma Chairman, ITU-T Study Group 10.
Class Diagrams Revisited. Parameterized Classes Parameterized Classes - are used to represent relationships between templates.
PPL Syntax & Formal Semantics Lecture Notes: Chapter 2.
ITEC1301 Object-Oriented Systems Construction Lecture Notes #4 1.
© 2009 Artisan Software Tools. All rights reserved. Testing Solutions with UML/SysML Andrew Stuart, Matthew Hause.
© Copyright 2010 Rockwell Collins, Inc. All rights reserved. Practical SysML Applications: A Method to Describe the Problem Space Ray Jorgensen David Lempia.
INTRODUCTION: This report contains the results of the International Council of System Engineer (INCOSE) UML/SySML Team efforts to produce UML/SySML Architecture.
Defects of UML Yang Yichuan. For the Presentation Something you know Instead of lots of new stuff. Cases Instead of Concepts. Methodology instead of the.
COP Introduction to Database Structures
UNIT-IV Designing Classes – Access Layer ‐ Object Storage ‐ Object Interoperability.
An Overview of Requirements Engineering Tools and Methodologies*
Evolution of UML.
SysML 2.0 Formalism Requirements and Potential Language Architectures
UML 2.0 Compliance Points Proposal
Course Outcomes of Object Oriented Modeling Design (17630,C604)
SysML 2.0 Formalism: Requirement Benefits, Use Cases, and Potential Language Architectures Formalism WG December 6, 2016.
Inheritance Allows extension and reuse of existing code
Chapter 16 UML Class Diagrams.
SysML v2 Formalism: Requirements & Benefits
Week 10: Object Modeling (1)Use Case Model
Sequence Diagram.
Today’s Objectives Define the Problem Domain
SDLS Protocol Green Book initiation
Dynamic Modeling: Defining Classes
Chapter 2, Modeling with UML, Part 4 UML 2 Metamodel
Service-centric Software Engineering 1
SYS466 Domain Classes – Part 1.
UML profiles.
Class Diagrams.
Message Sequence Charts
Semantic Markup for Semantic Web Tools:
OOPSLA Workshop on Domain-Specific Modeling Tools Workgroup
Artisan Software Tools A Pragmatic Approach Using Ada and UML
Visual Modeling Using Rational Rose
Overview of the ETSI Test Description Language
Overview of the ETSI Test Description Language
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Issue# UMLTP21-3 Related issues
Introduction to TDL and TOP
Software Architecture & Design
Presentation transcript:

Comparing UML 2.0 Interactions and MSC-2000 Can MSC be retired? 26-Jul-19 Øystein Haugen

Timeline MSC simple HMSC time&data sdl data 1992 1996 2000 2004 UML simple synch integrated in UML 26-Jul-19 Øystein Haugen

Different terms – but the same concepts condition continuation msc ref interaction occurrence inline expression combined fragment message message 26-Jul-19 Øystein Haugen

Several kinds of diagrams 26-Jul-19 Øystein Haugen

Context of MSCs / Interactions msc doc. classifier defining/ utilities composite structure 26-Jul-19 Øystein Haugen

Decomposition, Messages and Suspension region MSC 2000: hierarchy of MSC Documents UML 2.0: hierarchy of UML classes. Strictly follows the composite structure Messages MSC 2000: in general asynchronous, but synchronized method calls can be expressed UML 2.0: synchronous as well as asynchronous. Messages often represent synchronized method calls. Suspension region MSC 2000: it is there UML 2.0: it is not there 26-Jul-19 Øystein Haugen

Data MSC-2000 UML 2.0 In practice has a very sophisticated scheme to define the data interface within the description itself both syntax and semantics that will make it possible to use the data language of your choice interface definition exists for SDL (Z.121) does anyone use it? UML 2.0 has no concrete data language of its own has an abstract syntax of Actions (metamodel) In practice both use fragments of programming languages 26-Jul-19 Øystein Haugen

Time duration observation duration observation time observation time constraint duration constraint duration constraint time observation 26-Jul-19 Øystein Haugen

Timers and the U2TP UML 2.0 Profile timer operations timer operations 26-Jul-19 Øystein Haugen

Generics MSC-2000 UML 2.0 Comparison parameterizing of messages, instances, data values UML 2.0 general template mechanism normal value parameters Comparison MSC is slightly better 26-Jul-19 Øystein Haugen

Formal Semantics MSC-2000 UML 2.0 In practice has no Annex B (i.e. formal semantics) but MSC-96 had Annex B (Michel Reniers) UML 2.0 has no official formal semantics but there are numerous attempts to formalize parts of UML 2.0 pUML-group STAIRS formalization of Interactions based on trace semantics and FOKUS-inspired approach In practice the tools define the real semantics 26-Jul-19 Øystein Haugen

Profiling UML Profiles in UML is a way to customize UML for a specific purpose Official profiles UML Profile for schedulability, performance and time specification still only for UML 1.4 UML Profile for Testing U2TP – the first available profile for UML 2.0 adds timers and time zones adds data partitioning adds test-specific terms Your own profile for some project, or some specific purpose but beware that you add semantics as well as syntax 26-Jul-19 Øystein Haugen

The Future of MSC/SDL vs UML Scenario1: MSC/SDL and UML both prevail they will need different niches, and UML will not let any lucrative niche be left unattended Scenario2: UML fails MSC/SDL can thrive in the real-time market something new e.g. from Microsoft outcompetes both Scenario3: UML succeeds more MSC/SDL will gradually surrender ground to UML MSC/SDL tool vendors will become UML vendors There may be markets for MSC/SDL profiles of UML what is executable UML? 26-Jul-19 Øystein Haugen

Which scenario will happen? It will not be dependent (purely) on technical reasons 26-Jul-19 Øystein Haugen