UML or DSML? You can now have both with Papyrus 1.0!

Slide title

70 pt

CAPITALS

Slide subtitle

minimum 30 pt

Ericsson NWADSL at EclipseCon Europe 2014 | Public | © Ericsson AB 2014 | 2014-10-29 | Page 1 (27)

UML or DSML?

You can now have both with Papyrus 1.0!

Ulf Olsson Ericsson AB Toni Siljamäki Ericsson AB Francis Bordeleau Ericsson AB (co-author) NWADSL@EclipseConEurope2104

Slide title

44 pt

Text and bullet level 1

minimum 24 pt

Bullets level 2-5

minimum 20 pt

Characters for Embedded font: !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵŶŷŸŹźŻżŽžƒȘșˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–—‘’‚“”„†‡•…‰‹›⁄€™ĀĀĂĂĄĄĆĆĊĊČČĎĎĐĐĒĒĖĖĘĘĚĚĞĞĠĠĢĢĪĪĮĮİĶĶĹĹĻĻĽĽŃŃŅŅŇŇŌŌŐŐŔŔŖŖŘŘŚŚŞŞŢŢŤŤŪŪŮŮŰŰŲŲŴŴŶŶŹŹŻŻȘș−≤≥fifl

ΆΈΉΊΌΎΏΐΑΒΓΕΖΗΘΙΚΛΜΝΞΟΠΡΣΤΥΦΧΨΪΫΆΈΉΊΰαβγδεζηθικλνξορςΣΤΥΦΧΨΩΪΫΌΎΏ

ЁЂЃЄЅІЇЈЉЊЋЌЎЏАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯЁЂЃЄЅІЇЈЉЊЋЌЎЏѢѢѲѲѴѴҐҐәǽẀẁẂẃẄẅỲỳ№

Do not add objects or

text in the footer area Ericsson NWADSL at EclipseCon Europe 2014 | Public | © Ericsson AB 2014 | 2014-10-29 | Page 2 (27)

› What’s the problem?

› How did we go about solving it?

› Experiences

› Conclusions

Outline

Slide title

44 pt


minimum 24 pt

Bullets level 2-5

minimum 20 pt






› Large development organization

– 25000 R&D personnel out of 114000 world wide

› Wide range of products

› Radio, IP, transport, mobility, communications,

OSS/BSS, cloud infrastructure, …

› Continuity and compatibility

– Modeling support

› Language, validation, transformation

– Collaboration support

– Stakeholder support

› Portfolio, design, implementation, marketing

› Efficient tool development

– Leverage community development momentum

What is the problem?

Slide title

44 pt


minimum 24 pt

Bullets level 2-5

minimum 20 pt






The goal:

Get into the head

of the next guy

Find the tools to bridge this gap.

And the gap to the machine!

http://www.google.com/url?sa=i&rct=j&q=&esrc=s&frm=1&source=images&cd=&cad=rja&docid=YCjzSWXjanad9M&tbnid=g_oS7zYemXs_cM:&ved=0CAUQjRw&url=http://www.shortfacts.com/2013/03/09/top-5-facts-about-the-human-brain/&ei=r493UsyyMqrO4QSN6YCIAg&bvm=bv.55819444,d.bGE&psig=AFQjCNE9xjRXDgf65bG_oUFNnL0hGp2_1g&ust=1383653648904053

http://www.google.com/url?sa=i&rct=j&q=&esrc=s&frm=1&source=images&cd=&cad=rja&docid=YCjzSWXjanad9M&tbnid=g_oS7zYemXs_cM:&ved=0CAUQjRw&url=http://www.shortfacts.com/2013/03/09/top-5-facts-about-the-human-brain/&ei=r493UsyyMqrO4QSN6YCIAg&bvm=bv.55819444,d.bGE&psig=AFQjCNE9xjRXDgf65bG_oUFNnL0hGp2_1g&ust=1383653648904053

Slide title

44 pt


minimum 24 pt

Bullets level 2-5

minimum 20 pt






Network architecture Old method: 3GPP

standardization by telco

industry consensus

Problem: this only a part of our scope, and the world moves faster now…

So, what do we do instead of paper and drawing tools?

Behind this:

You find this:

Slide title

44 pt


minimum 24 pt

Bullets level 2-5

minimum 20 pt






› Functional modeling with

interfaces works well to

discuss and agree end-to-

end behavior

– Hierarchy of logical functions

– Expandable logical interfaces

– Information elements

– Use-cases, signal flows

– Complemented with

topological models

Modeling Approach

Slide title

44 pt


minimum 24 pt

Bullets level 2-5

minimum 20 pt






Collaboration Approach

Git repository

managed by

Gerrit Central

Architect Workbench

… …

Commit

Push

Fetch

Import

All workbenches hold the complete model(s)

Cycle: evolve/propose/commit/distribute

Supports studies based on stable architecture

Central coordination, distributed way of working

Slide title

44 pt


minimum 24 pt

Bullets level 2-5

minimum 20 pt






CTO marching orders

“We need to ensure

architecture and product

consistency across the

company”

Slide title

70 pt

CAPITALS

Slide subtitle

minimum 30 pt


Top right

corner for

field-mark,

customer or

partner logotypes.

See Best practice

for example.

Slide title

40 pt

Slide subtitle

24 pt

Text

24 pt

Bullets level 2-5

20 pt


NWADSL – Short Background

NWADSL – Short Background

– Very Domain Specific Language – Modeling of Network Architectures

– Guiding document: Network Architecture Evolution Strategy

– Defining the NWA language – Concepts, Modeling Elements, Colors

– Modeling Rules, WoW, Guidelines, Wiki

– Example Models (PowerPoint slide-kit)

– Technical Icons Library

NWADSL – Start Modeling (tool independent DSL)

– PowerPoint Modeling

– Modeling in Visio

– Whiteboard

Top right

corner for

field-mark,

customer or

partner logotypes.

See Best practice

for example.

Slide title

40 pt

Slide subtitle

24 pt

Text

24 pt

Bullets level 2-5

20 pt


Technical Icons Library

Top right

corner for

field-mark,

customer or

partner logotypes.

See Best practice

for example.

Slide title

40 pt

Slide subtitle

24 pt

Text

24 pt

Bullets level 2-5

20 pt


The first NWADSL tooling (1)

open

open

open

Top-level diagram:

Domain-level diagram:

Function diagram:

Interface diagram:

Top right

corner for

field-mark,

customer or

partner logotypes.

See Best practice

for example.

Slide title

40 pt

Slide subtitle

24 pt

Text

24 pt

Bullets level 2-5

20 pt


The first NWADSL tooling (2) Sequence diagram:

open

Sub-sequence diagram:

Top right

corner for

field-mark,

customer or

partner logotypes.

See Best practice

for example.

Slide title

40 pt

Slide subtitle

24 pt

Text

24 pt

Bullets level 2-5

20 pt


Question: Why Not UML ???

Why not Open Source UML tools for NWADSL instead of in-house tools?

– Evaluation of Ericsson DSL’s and tooling on Papyrus was ongoing.

– Why not create an NWADSL in Papyrus UML?

– (an EMF-based NWADSL was also discussed, but we like to reuse capabilities of UML and open source tooling, not reinventing them)

Initial discussions with the Papyrus vendor CEA

– Example graphics in Papyrus by CEA

– Testing stereotypes, SVG shapes, stylesheets

– …showing that it could be done in Papyrus

First pilot: Test Papyrus Graphics Capabilities

– Problem: Replace UML elements with SVG’s

– The initial support in Papyrus was primitive...

– …but the first pilot project was successful.

– …showing GREAT potential for improvements.

Top right

corner for

field-mark,

customer or

partner logotypes.

See Best practice

for example.

Slide title

40 pt

Slide subtitle

24 pt

Text

24 pt

Bullets level 2-5

20 pt


Customized NWADSL in Papyrus

NWADSL - Main Parts

– NWA Profile

– Customized Palette

– SVG Graphics Library

– CSS stylesheet rules

for graphics rendering

(rules based on stereotypes and property values)

Top right

corner for

field-mark,

customer or

partner logotypes.

See Best practice

for example.

Slide title

40 pt

Slide subtitle

24 pt

Text

24 pt

Bullets level 2-5

20 pt


NWADSL Modeling in Papyrus (1) Top-level diagram:

Domain-level diagram:

Function diagram:

Interface diagram:

open

open

open

Top right

corner for

field-mark,

customer or

partner logotypes.

See Best practice

for example.

Slide title

40 pt

Slide subtitle

24 pt

Text

24 pt

Bullets level 2-5

20 pt


NWADSL Modeling in Papyrus (2) Sequence diagram:

open

Sub-sequence diagram:

Top right

corner for

field-mark,

customer or

partner logotypes.

See Best practice

for example.

Slide title

40 pt

Slide subtitle

24 pt

Text

24 pt

Bullets level 2-5

20 pt


Multiple DSL’s in Same Model

NWA Vision:

– Integrate NWADSL with other DSLs and plain UML.

Some NWA Use Cases:

– De-compose into finer-grained NWA Functions. (done)

– Combine with NWA Info Modeling. (done)

– Combine with plain UML modeling. (done)

– Combine NWA modelling with BPM.

– De-compose NWA Functions into

”design” models, like Executable UML.

Proof-of-concept showcase models needed:

– Combine NWADSL with another Ericsson DSL in the same model.

– Combine NWADSL with a ”design language”, like Executable UML.

Top right

corner for

field-mark,

customer or

partner logotypes.

See Best practice

for example.

Slide title

40 pt

Slide subtitle

24 pt

Text

24 pt

Bullets level 2-5

20 pt


Model Compiler:

ExecutableUML DSL Prototype

Quick DSL Prototyping:

– Develop an Executable UML Profile (basic OCL restrictions)

– Develop Customized UI Palettes

– Then migrate an existing model...

Model Compiler Prototyping:

– M2M + M2T capabilities required

– Template capability is also required

– QVTo and blackboxing using StringTemplates can solve this

NWA Modeling showcase thinking:

– When linking these technologies to NWADSL we prove we can go from Network Modeling downto code.

+

QVTo

Profile + DSL restrictions in OCL: Customized Palettes:

Migrated Executable UML model:

call

generate

Top right

corner for

field-mark,

customer or

partner logotypes.

See Best practice

for example.

Slide title

40 pt

Slide subtitle

24 pt

Text

24 pt

Bullets level 2-5

20 pt


Integrate NWA + ExecUML DSL’s

NWA model

Exec UML model

decompose

Top right

corner for

field-mark,

customer or

partner logotypes.

See Best practice

for example.

Slide title

40 pt

Slide subtitle

24 pt

Text

24 pt

Bullets level 2-5

20 pt


Integrate NWA + Baseband DSL’s

NWA model

Baseband model

decompose

decompose

baseband

Top right

corner for

field-mark,

customer or

partner logotypes.

See Best practice

for example.

Slide title

40 pt

Slide subtitle

24 pt

Text

24 pt

Bullets level 2-5

20 pt


Slide title

44 pt


minimum 24 pt

Bullets level 2-5

minimum 20 pt






› The good

– 103 people on the mailing list

– 16 active architects

– …and this is just the beginning!

› The bad

– Our goal is to work on a model-based level of abstraction,

therefore all tools must work on the same level

› Luna 1.0 had text-based compare only, which caused corrupt

models. Very off-putting…

› The EMFCompare project (Obeo, EclipseSource) has made

major progress in the past months

– Possible to create corrupt models if upstream commits are not

synchronized

– Pushback from the users: too complex, “looks like programming”

Life at the coalfront

Slide title

44 pt


minimum 24 pt

Bullets level 2-5

minimum 20 pt






› Simple UI

– As few irrelevant items as possible

› Scripting

– For local adaptation

› Creation of navigation-enabled HTML

– For information sharing with non-modelers

› Improved focus on graphical interaction

– Example: UI for EMFCompare is on the right track, but not intuitive

enough

– Things done in the diagrams sometimes has unintended effects on

the model

› …

Wish list (excerpts)

Slide title

44 pt


minimum 24 pt

Bullets level 2-5

minimum 20 pt






We need:

› Flexibility

– To achieve the right abstraction

› Integration

– For efficiency in the whole development and integration chain

› Ease of use

– To lower the threshold for architecture-level users

› Efficient collaboration

– To support the entire organization

…and a community approach

– To leverage innovation and creativity inside and outside the

company

Conclusions

Slide title

44 pt


minimum 24 pt

Bullets level 2-5

minimum 20 pt






›Not a question of “OR”, we have both!

›Presents a DSML to the user: – Adapted to the problem space (actually, spaces!)

– Customized: no UML expertise required

›Based on UML: – Leverages years of work of top modeling and tool

implementation experts

– Builds on the semantic richness of UML

› Benefits: – Facilitates integration with other languages

– Accommodates other UML-based technologies

(present and future)

– Provides a full language support infrastructure

(editors, renderers, compilers, debuggers etc.)

› Drawbacks: – More complex to define that “pure”

(built from scratch) DSML – UML expertise required

UML or DSML?

DSML

Documents

UML or DSML? You can now have both with Papyrus 1.0!