SYSML 1.4 FOR PAPYRUS - wiki.eclipse.org · (CEA LIST) Patrick Tessier (CEA LIST) Benoit Maggi (CEA LIST) Klaas Gadeyne (Flanders Make) You A DEDICATED TEAM EclipseCon 2015 | Ludwigsburg

SYSML 1.4 FOR PAPYRUS

EclipseCon 2015 | Ludwigsburg

Prepared by: François Le Fèvre | Patrick Tessier | Benoit Maggi

• SysML 1.4 standard

Standard Difficulties to implement SysML 1.4

• Systematic implementation approach

Process Test

• Current state

Feature Overview Zoom on specific diagrams

• Outgoing work

Planning Team We need you

AGENDA


SYSML 1.4 STANDARD

EclipseCon 2015| CEA Team

• formal/2015-06-03

Specification 346 pages

55 concepts

Profile given by OMG

4 new diagrams

SYSML 1.4 OMG STANDARD


• The standard is essentially written in natural

language

Requirements are not well identify

Constraints are mostly written in natural language

• Figures in the spec are difficult to interpret:

Parameters in the parametric are ports, properties?

What is mandatory? Optional?

• Some representations do not exist in the profile:

parts, references…

Call out concepts, not present in the profile.

• Constructions are dependent from diagrams

Property path need the concept of context purely diagram

IMPLEMENTATION OF SYSML INSIDE

PAPYRUS


SYSTEMATIC IMPLEMENTATION

APPROACH


• In order to address problems and succeed to understand

developments

• Use of Model Driven Development

• Specification are made with SysML 1.1 version

• Model of the Specification as Requirement model

• Derive new requirements to match technologies used in Papyrus

• Code and tests reference requirements

PROCESS

OMG

• Profile

• Standard specifications (PDF)

Process

• MDD

• Semantic

• GUI

SysMLPapyrus


USE OF SYSML REQUIREMENT

DIAGRAM

Automatic

Requirements

Extraction from the

standard specification

(PDF)

Refining the req for a

technology

Implementation


Code ref the requirement

by using tag

@papyrus.req ${modelID}#$reqID}


• Use in the build of test about model validation

• Best effort:

• Each written requirement must be satisfied and verified by a test.

• RCPTT scenario

• Have been deployed

• Run tests for each Gerrit contribution, to be sure

• Patches can be compiled

• Patches do not break existing tests


TESTS

USING ECLIPSE GALAXY TOOLS


JavaDoc

Maven Web Site

Nexus

RCP with P2 update site

https://hudson.eclipse.org/papyrus/view/Sysml/job/papyrus-sysml-website/ws/site-staging/index.html

Hudson

CURRENT STATE


• Graphical coverage:

• BDD:86% , IBD: 87%, Requirement: 100%, Parametric: 71%

• Customization of papyrus

• Technology

• Model-based. Less code as possible (e.g. BDD = 330 lines of codes)

SYSML 1.4 CURRENT STATE


Class Diagram Composite Structure Diagram

Block Definition

Diagram

Requirements

Diagram

Internal Block

Definition

Parametric

Diagram

Semantics

ElementTypesConfiguration model(cf. org.eclipse.papyrus.sysml.service.types)

Graphical

Expansion model

(cf. org.eclipse.papyrus.infra.gmfdiag.common)

FROM STANDARD TO HIGH LEVEL FEATURES

AND ITS DECOMPOSITION IN TERM OF FUNCTION


DISPARITY BETWEEN DIAGRAMS

Block

Definition

Diagram

Parametric

Diagram


OUTGOING WORK


SysML 1.4 Standard Release

June

0.7

SysMLPapyrus

Papyrus 1.1.3

0.8

SysMLPapyrus

Nightly can be

downloaded

Next Version End of 2015

SysMLPapyrus

PLANNING


François Le Fèvre

(CEA LIST)

Patrick Tessier

(CEA LIST)

Benoit Maggi

(CEA LIST)

Klaas Gadeyne (Flanders

Make)

You

A DEDICATED TEAM


• You want to participate:

Mailing list

Bugzilla

Contribution by following instruction of contributing.mdd

• Feed backs for the version delivered with papyrus mars 1.1.3

• An example in SysML can be a good contribution and be

included as model example inside SysML 1.4

WE NEED EXPERT, USER AND DEVELOPERS

WE NEED YOU


Documents

SYSML 1.4 FOR PAPYRUS - wiki.eclipse.org · (CEA LIST) Patrick Tessier (CEA LIST) Benoit Maggi (CEA LIST) Klaas Gadeyne (Flanders Make) You A DEDICATED TEAM EclipseCon 2015 | Ludwigsburg