Skip to end of metadata
Go to start of metadata


Zoom Meeting Link:  https://zoom.us/j/137904496 International numbers available: https://zoom.us/zoomconference?m=mi-ad1sMLWlXByAKLio5vDnd9JYqUR_a

2019 Modeling Subcommittee Recordings

Duration 60 minutes

DurationAgenda ItemRequested byNotes / Links
START RECORDING
 5Co-chair

Welcome and Plan

M2 and M3 Checklist to be shared at the TSC this week for approval.

Catherine suggests to enhance as follows

Please provide the link to the specific use case/feature requirement and its associated Sequence Diagrams

Describe the interactions and behavior of each information exchange with the use cases/feature requirements and sequence diagrams

Andy Mayer will email Catherine to ask for clarification of the TSC approval process.

 5Resource IM report

Review modeling activity status. Jessie S Jewitt walked through R3 Clean to compare with IFA011 2.5.1.

Asking for team to take a look at the comparison version and provide comments before a vote on the consensus vote:

https://wiki.onap.org/display/DW/Comparison+of+Current+R3+Clean+Version+with+IFA011+v2.5.1

 5Service IM report

Kevin presented Composite / Atomic diagram for services. Discussion on cardinality, both Descriptor and Run-Time (instance)

See: https://wiki.onap.org/display/DW/ONAP+Service+IM+Minutes+20190130

No call this week

 5

DM report


No report

5Infrastructure Modeling Discussion

Focus on abstraction of Multi-cloud layer. What does ONAP need to be aware of? What are opportunities to enable "model-driven". E.g., Compute, Storage, Network capabilities.

5R4 High level requirements

 https://wiki.onap.org/display/DW/ONAP+R4+Modeling+High+Level+Requirements

Need to influence actual code with High Level Requirements.

Code commitment is essential for data model. Need modeling leads to work with PTLs and members to identify development resources.

Input needed by M2, please provide input by Feb 12th (especially on the Code Commitment).

5Other Discussion

Alexander Vul is recommending continuous development approach for info and data models. We can use the stereotypes to represent the modeling element lifecycle state.

See: Lifecycle Stereotype Proposal

Need to capture active issues between releases (history)

Possible UML basics class focused on Information Modeling, and use of Papyrus. Multiple languages for the class would be useful.

A good UML Reference is: http://www.temida.si/~bojan/IPIT_2014/literatura/UML_Reference_Manual.pdf


  

ACTION ITEMS:

Call to approve PNFD (for the Clean Model) with the attributes geographicalLocationInfo and swVersionList removed for the present R4 release. Subcommittee will initiate 2 week email poll on this question. (call for general consensus during the Feb 12th call).





Zoom Chat Log