- R1 use cases (R-vCPE and vVoLTE) status was presented by Kang and Yang
- Architecture/Usecase subcommittee joint meeting tomorrow:
- Alla presented questions raised by Architecture subcommittee. Relevant R2 use cases task forces were requested to answer question raised previously https://wiki.onap.org/display/DW/Questions+and+answers
- We created our list of questions to Architecture subcommittee. This was sent out by a separate email. We will also provide overview of our agreed way forward for documenting R2 use case/requirements (below)
- The major discussed topic was our way of handling/documenting R2 use cases and we agreed on the following:
- ONAP objective in general is to support any use case, thus set of functionalities we develop should be generic, applicable to any use case
- There will be 3 categories of requirements/platform capabilities presented for R2 approval, this will be comprised of:
i. What features are missing from R1 functional requirements/actual implementation (functional requirements are those resulted from specific use case flows/ONAP related flows, while non-functional requirements are e.g. credentials usage, performance, resiliency, testing requirements etc.). R1 R-vCPE and vVoLTE use case teams along with Integration team members are requested to extend the list under https://wiki.onap.org/display/DW/Missing+Platform+capabilities
ii. Non-functional requirements desired for R2 implementation. We will jointly discuss with Architecture subcommittee tomorrow what is the best way of introducing/handling those
iii. R2 new functional requirements extracted from R2 use cases proposals. R2 task forces are required to do this work for their corresponding use cases
- In parallel to (b), R2 use cases task forces will continue their work on detailed R2 use case proposals description. (b) may be extended as a result of this work
- We will then prioritize functionalities defined by (b) above and make a decision, jointly with Architecture and Modeling subcommittees, what is our R2 proposal