1. Papyrus (https://www.eclipse.org/papyrus/)
Focussing on use in ONF (
Nigel Davis (Ciena -

2. Agenda Organizations using Papyrus
General overview of ONF work related to Papyrus usage
Models
Guidelines
Tools
Papyrus overview in the context of ONF work
Tool
Class Models
Other Models
Specific use in ONF
Informal Inter-SDO Open Modelling Initiative (IISOMI)
Tooling
Papyrus issues
Some background

3. Some organisations using Papyrus
Papyrus UML is used for Information Models (IMs) and Data Model (DMs) by:
ONF (for all IMs (and “DMs”) related to software defined standards)
ITU-T (for IMs)
ETSI-NFV (for IMs derived from a tabular representation in normative documents)
MEF (for NRM & NRP projects (inc. Presto))
TMF (migration to Papyrus planed for IMs)
Various commercial telecoms orgainsations
Players in other industries such as aerospace and automotive …
Critical considerations
Opensource, free, highly capable, Eclipse Platform tooling

4. General overview of ONF usage of Papyrus
Models
ONF-CIM especially ONF CoreModel
(there is also a private git repository that we are moving to the open shortly)
The latest version of the CoreModel is at   (in TR 512 V1.3/TR-512_v1.3_Publish)
Version will be released in the ONF “library” in January
ONF TAPI (used also by MEF for the Presto Interface)
ONF WD API
IISOMI Profiles etc
Guidelines (IISOMI)
UML Guidelines
Papyrus Guidelines
Including use of Gendoc
UML Interface Guidelines
UML  Yang
Supported by IISOMI tooling and used by TAPI as part of tool chain
UML  OpenAPI
Supported by IISOMI tooling and used in some TAPI demonstrations
UML  Protobuf (under construction)
UML  TOSCA (exploration)
Pruning & Refactoring Guidelines (early draft)
Tooling
P&R (prototype)

5. MEF defines the Lifecycle Service Orchestration Reference Architecture
NBI of SDN Controller
of WAN Controller
of NFV Orchestrator
of NMS, Subnetwork Managers
Public

6. ONF Forwarding, Termination and Topology IM
Network
Showing layers
From TR-512.2
Network Device OR Opaque Network

7. Papyrus Overview and (ONF) usage demo
Brief overview of:
IISOMI and ONF work structure
Installation of Papyrus (ISSOMI guidelines explain how to get the tool and to add support for Gendoc etc)
Tool version (some parts of the demo will use Eclipse Oxygen and other parts Eclipse Mars – ONF are migrating at the moment)
Tool files (.uml, .notation, .di)
Using the tool (with a focus on class models and diagrams)
Getting a model into the tool
Use of the tool [Main focus of the demo]
Perspectives
Panes
Navigation
Class models
Other Papyrus features and related tools
Validation
Style sheets
Gendoc for documentation
Git
Touch on other models
State
Sequence
etc
Use of class models in an IM and DM context
Core and Tapi
Profiles
P&R method
Increasing the rigor over time…

8. Guidelines evolution UML Modeling Guidelines IISOMI 514
multi SDO
UML Modeling Guidelines IISOMI 514
UML Modeling Guidelines ONF TR-514
ITU-T SG15 Modelling Guidelines
NGCOR Modelling Requirements
Other candidates:
ONAP
OIF …
JWG MA Model Repertoire

9. (inc. converged network ABE)
ONF Tooling evolution
ITU-T Technology IMs
TMF SID
ONF IM
(inc. converged network ABE)
ONF Spec Approach
NVP extension
TMF MTNM / MTOSI
Manual P&R
Tool Assisted P&R
Tool Assisted P&R
Mapping
Mapping
Manual Generation
Experience, lessons, insight
Manual process
CORBA IDL &
XSD
TMF TIP
TAPI
Tooled process
Model migration
Tooled Generation
Tooled Generation
UML Tool
Implementation
OssJ
Transformation Tooling
Java &
XSD
Yang, REST, TOSCA…
IBM RSA (Eclipse, Proprietary)
Tooled Generation
TigerStripe (Cisco, Open Source)
Papyrus (Eclipse, Open Source)
Time
IISOMI (Java Script, Open Source)
Java &
XSD
2005
2011
2017

10. Influence Across Standards and Open Source
TAPI FRS
Use cases & Requirements
TAPI UML Information Model
TAPI YANG
Data Schema
SWAGGER/REST APIs
ONF Core Information Model
ONF Technology Specification Models
UML-YANG
Generation Tool
YANG-SWAGGER Generation Tool
SNOWMASS TAPI SDK
EAGLE Modeling Tools
Open Model Profile
Code
OTN
(ITU-T G.874.1)
ETH
(ITU-T G.8052)
MPLS-TP
(ITU-T G.8152)
Python Reference Implementation
Python Stub Generation Tool
Optical Transport
MEF
Open CS Implementations
Packet WAN
Multi-carrier
T-SDN Interop
Implementation Agreements & Certification
OIF
Interop Implementations
NRM
MEF Models
NRP
ONF OIMT
ONF OTCC
ITU-T SG15
Technology Generic Core Model
(ITU-T G.7711)
ONF OTCC

11. Papyrus Issues (note, Eclipse platform versions indicated)
Migration from version to version
Diagrams get messed up (better on Oxygen)
Mars  newer versions has an issue with associations being flipped on diagrams (uml is OK but further rebuild of the diagrams required)
Profile migration needs to be done with care (can lose settings)
In Version issues
Neon and all but most recent Oxygen do not display association Member end attributes, where owner set to classifier, in the class
Oxygen does not allow rectilinear associations to move easily when they become straight
Moving association ends from one class to another sometimes flips the association orientation
In general
Style sheets do not allow enough flexibility
Eclipse diagram layout appears sensitive to some windows display settings
Support tools
Gendoc documentation is lacking (we have a small community that exchanges learnings)

12. Thank you!! 

13. Background.. Some fragments of the ONF CoreModel

14. Forwarding, Termination and Topology
From TR-512.4

15. Resilience
From TR-512.5

16. Physical
From TR-512.6

17. Emergent behavior
From TR-512.6

18. The Spec Approach
From TR-512.7

19. The control model
From TR-512.8

20. Processing Construct Model
From TR

21. Moving away from the traditional NE
The traditional NE is replaced by a combination of the:
Control model
ProcessingConstruct and ConstraintDomain
Physical model
Various specific functional models
The association between function and physical is defined using the ConstraintDomain and ProcessingConstruct

22. General Operations Patterns
From TR

23. Component-System Pattern
From TR-512.A.2

24. Component-System Pattern
From TR-512.A.2

25. Pruning & refactoring Tooling is currently prototype…
" },
"maintainers": [ {
"name": "oozcitak",
" ": } ],
"_npmOperationalInternal": {
"host": "packages-12-west.internal.npmjs.com",
"tmp": "tmp/xmlbuilder tgz_ _
Pruning & refactoring
Tooling is currently prototype
Generalized Core model is pruned to remove elements not necessary for the TAPI view, for example ProcessingConstruct.
Pruned Core model is refactored to project familiar named items, for example:
ForwardingConstruct in the Core becomes both Connection and ConnectivityService in TAPI.
LogicalTerminationPoint in the Core becomes NodeEdgePoint, ConnectionEndpoint and ServiceEndPoint in TAPI.
Tooling supports the Pruning and Refactoring process
Constructs a clone of the model with multiple interconnected copies of the classes from the source model where requested
Highlights differences between models
Longer term
Tooling will support further refactoring including the merging of classes from several models

26. UML Model (TAPI SDK)

27. TAPI UML, YANG and Swagger Mapping

28. IISOMI Informal Inter-SDO Open Modelling Initiative (IISOMI)
Deals with:
General UML/Papyrus usage
Profiles
Tooling
Attended by people from ONF, TMF, ITU-T and MEF currently
It is open to all
Aim is to foster consistent usages across the industry
Some current challenges
Association classes or not
Association navigation strategy …

29. TR-512.7 Figure 4-22 Sketch of Ethernet OAM spec case in context of LP Case and LP Spec model