...
1. Use case subcommittee discuses new use casescases
2. For every use case2. , Use case subcommittee describes ONAP Platform capabilities desired for new Release implementation of the new use casefor the implementation, produces use case flow diagrams, breaks use case into platform requirements (functional and non-functional), provides its view on the foreseen modules introductions/modifications and suggests potential PNFs / VNFs
2a. Use case and Architecture subcommittees jointly identify key features and requirements exposed required by the new use review platform requirements required by the new use case and/or by the release.
3. Use case subcommittee gets feedback from the potentially effected projects including integration team on feasibility and development and development time estimation
3a. Architecture subcommittee evaluates impact of the target use case(s) platform requirements on the architecture and makes updates as required
...
4a. Architecture, Use Case, and Modeling subcommittees subcommittees discuss and select use cases and key features synchronize on plans key platform requirements for the release
5. TSC approves the selected use cases and key featuresthe selected key platform requirements for the release
6. In case a new modules or a new functionality to existing modules or a new APIs introduction is foreseen, architecture subcommittee defines the new/modified ONAP flows and the interfaces principles, based on the approved use cases platform requirements (1)
7. Projects define their extended functionality and their external APIs, following those principles.
8. Detailed per-component flows are defined by the projects and projects write their user stories / implement them; Integration team continuously works with Use case subcommittee to accompany the use case requirements development, review epics/user stories, answer questions, etc. Use case subcommittee behaves as system engineers for the use case platform requirements through test start date
9. Integration team defines the gating use case platform requirements based on step 8 and finalizes the PNFs / VNFs selection, with the help of use case subcommittee, architecture subcommittee, PTLs of a different ONAP projects
10. TSC approves the gating use caseplatform requirements
11. Integration project leads (coordinates) effort to get the gating use case platform requirements tested, repaired, and verified, and the results are documented
12. Use case subcommittee along with the Integration team decides which new and complete use cases can be showcased following new platform capabilities introduction
(1) The defined functional extensions should be as generic as possible to allow re-use of it by additional use cases.