Bernd Zeuner (Deutsche Telekom) December 2, 2018 IISOMI Guidelines December 2018 Update Bernd Zeuner (Deutsche Telekom) December 2, 2018

Guideline Updates

IISOMI 514/TR-514 v1.3 info UML Modeling Guidelines Published Version 1.3, July/2018 TR-514_UML_Modeling_Guidelines_v1.3-1-1.pdf Version 1.4 development started Draft Version 1.3.01, October 29, 2018 Draft_TR-514_UML_Modeling_Guidelines_v1.3.01.docx Preliminary solution 1 for bit set modeling deleted «StrictComposite» made obsolete «LifecycleAggregate» made obsolete Meaning of Composite/Shared/None aggregation property and association end multiplicity clarified

IISOMI 515/TR-515 v1.3 info Papyrus Guidelines Published Version 1.3, July/2018 TR-515_Papyrus_Guidelines_v1.3-1-1.pdf Version 1.4 development started Draft Version 1.3.01, August 27, 2018 Draft_TR-515_Papyrus_Guidelines_v1.3.01.docx

IISOMI 531/TR-531 v1.1 info Papyrus Guidelines Published Version 1.1, July/2018 TR-531_UML-YANG_Mapping_Gdls_v1.1-1-1.pdf Version 1.2 development started Draft Version 1.1.01, November 8, 2018 Draft_TR-531_UML-YANG_Mapping_Gdls_v1.1.01.docx Preliminary solution 1 for bit set modeling deleted Statement added in section 1 that RFC 8342 NMDA is fulfilled Mapping of leafrefs refined in section 5.6.1 «StrictComposite» and «LifecycleAggregate» mappings removed Uses statement in an augmentation wrapped by a container statement

TR-543 v1.0 info UML to OpenAPI Mapping Guidelines Published Version 1.0, February/2018 TR-543-v1.0-info.pdf

TR-544 v1.0 info UML to ProtoBuf Mapping Guidelines Published Version 1.0, February/2018 TR-544-v1.0-info.pdf

Profile Updates

UML Profiles OpenModelProfile, v0.2.15/16 «Choice» stereotype made obsolete OpenModelOperation::isOperationIdempotent property made obsolete OpenModelOperation::isAtomic property made obsolete «StrictComposite» stereotype made obsolete «LifecycleAggregate» stereotype made obsolete OpenInterfaceModelProfile, v0.0.10 «OpenInterfaceModelClass» stereotype made obsolete OpenInterfaceModelAttribute::attributeValueChangeNotification property made obsolete NotificationDefinition enumeration no longer used and deleted BITS removed from Encoding enumeration BitDefinition data type deleted Optional «Bit» stereotype (extending the Property meta class) added Optional «Bits» stereotype (extending the DataType meta class) added Github repository: https://github.com/OpenNetworkingFoundation/EAGLE-Open-Model-Profile-and-Tools/tree/ToolChain/UmlProfiles

GitHub Repository Updates Restructuring

IISOMI GitHub Repositories Current EAGLE-Open-Model-Profile-and-Tools repository contains too many subprojects  unable to identify releases of individual parts Current EAGLE-Open-Model-Profile-and-Tools repository will be renamed  “EagleUmlCommon” and keep Common data types libraries UML profiles Style sheet New repositories EagleYangOpenApi administered by Bartosz EagleYangUml administered by Martin EagleUmlYang administered by Xing and Karthik  already in use EagleUmlOpenAPI need to define an administrator

UML Modeling Guidelines Open Issues

UML Modeling Guidelines Known Open Issues Many (10+) “old” unresolved review comments 7.1 File Naming Conventions (tbd) 7.7.2 Using Colors in diagrams (need further recommendations) 7.7.3 Style Sheets for diagrams (are there more in use?) Some UML properties are applicable for being defined by OCL expressions See iisomi2018.BZ.006.02_Requirements_for_Definitions.docx How is unknown Model/Interface Compatibility

UML Modeling Guidelines Known Open Issues Specification pattern

Papyrus Guidelines Known Open Issues Current applied tool versions: Eclipse version 4.7.2 “Oxygen” Papyrus version 3.2.0 RC4 Gendoc version 0.6.0 Eclipse releases are now published by date (first release 2018-09; Photon was the last one following the alphabet) Papyrus 4.1.0 is based on Eclipse 2018-09 Do we want “continuously” use the latest published version

UML to YANG Mapping Guidelines Known Open Issues Too many to list them all see yellow marked items in the mapping guidelines Currently under discussion Use of “current ()” function in the xPath expression of leafrefs UML pre- and post-condition mapping using “must” statement(s) Model/Interface Compatibility

UML to YANG Mapping Tool Known Open Issues See review comments in Issue #7 No automatic generation of the augment’s target node path Do we need to write the tools (also the YANG to UML tool) in a different programming language

Future Guideline Editorships And UML to YANG Mapping Call Chairman

Guideline Editorships / Mapping Call Chairman Deutsche Telekom will stop active contribution to IISOMI/OIMT/OTCC at the end of the year The following guideline documents need an editor: UML Modeling Guidelines Papyrus Guidelines UML to YANG Mapping Guidelines The UML to YANG Mapping Sub-team needs a chairman Opportunity to re-arrange the IISOMI/OIMT conference calls?