...
| 2019 Modeling Subcommittee Recordings |
|---|
Duration 60 minutes
| Duration | Agenda Item | Requested by | Notes / Links |
|---|---|---|---|
| START RECORDING | |||
| 5 | Co-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. | |
| 5 | Resource IM report | Review modeling activity status. Former user (Deleted) 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://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Comparison+of+Current+R3+Clean+Version+with+IFA011+v2.5.1 | |
| 5 | Service IM report | Kevin presented Composite / Atomic diagram for services. Discussion on cardinality, both Descriptor and Run-Time (instance) See: https://lf-onap.atlassian.net/wiki/display/DW/ONAP+Service+IM+Minutes+20190130 No call this week | |
| 5 | DM report | No report | |
| 5 | Infrastructure 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. | |
| 5 | R4 High level requirements | https://wikilf-onap.onapatlassian.orgnet/wiki/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). | |
| 5 | Other Discussion | Alex 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 | |
...