...
- Agenda bashing
- reminder for filling R9 high level requirements: https://wiki.onap.org/display/DW/ONAP+R9+Modeling+High+Level+Requirements
- Ben would like the modeling team to join the use case realization call on May 3, to discuss the modeling high level reqs
- reminder for filling R9 high level requirements: https://wiki.onap.org/display/DW/ONAP+R9+Modeling+High+Level+Requirements
- Model Proposals
- ETSI support for CNF model
- R9 DM proposal: https://wiki.onap.org/pages/viewpage.action?pageId=93011772
- aligned with SOL001 v4.2.1, package format is still under discussion
- will ask for approval after SOL001 v4.2.1 is stable
- a proposal of updating the information model documentation is planned in R9
- R9 DM proposal: https://wiki.onap.org/pages/viewpage.action?pageId=93011772
- 5G service / CPS model
- PNF instance model
- reverse engineering
- Topology model
- Proposal: https://wiki.onap.org/display/DW/Abstract+Topology+Model
- discussion material: Proposed Topology IM Sketch
- inspired by TAPI model to add "link", "connection" classes
- looking at ORAN use cases and see if the models can fulfill the requirements
- TAPI presentation may be found here: otcc2019.KS.002_TAPI_Concepts_Topology_Connectivity.pptx
- it's proposed to continue the discussion in this call
- Cagatay Buyukkoc
- ORAN requirements on topology model, the background is to have different views (including logical views, deployment views, etc.) on how NF are/will be deployed
- could be company specific
- ORAN is discussing on developing a tool to transform IM into DM automatically
- ORAN requirements on topology model, the background is to have different views (including logical views, deployment views, etc.) on how NF are/will be deployed
- ETSI support for CNF model
- Modeling Documentation
- R6 readthedocs review:
- gendoc template improvement: ONAP Information Model - Gendoc Examples
- discussion whether the description only applies for a navigatable end of an association
- continue discussion later
- add relationship documentation to the UML guideline:
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key ONAPMODEL-28 - UML principle wiki page:
- Principle and Guideline for Information Model Proposal Using Papyrus (Draft)
- review the updates to the Gendoc requirements part
- Michela suggest whether it's possible to add information of associations into the class definitions
- Xu will investigate it offline
- Michela suggest whether it's possible to add information of associations into the class definitions
- Using Papyrus for Modeling updates
- suggest to further discuss the version recommended after Jacqueline come back
- UML principle wiki page:
- R6 readthedocs review: