...
1. Use case subcommittee discuses new use cases. For every use case
2. Use case subcommittee describes ONAP Platform capabilities desired for new Release implementation of the new use case, produces use case flow diagrams, 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 case and/or by the release.
3. Use case subcommittee gets feedback from the potentially effected projects including integration team on feasibility and development time estimation
3a. Architecture subcommittee evaluates impact of the target use case(s) on the architecture and makes updates as required
4. Iterate back to 2
4a. Architecture, Use Case, and Modeling subcommittees select use cases and key features synchronize on plans for the release
5. TSC approves the selected use cases and key features
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 (1)
...
11. Integration project leads (coordinates) effort to get the gating use case tested, repaired, and verified, and the results are documented.
(1) The defined functional extensions should be as generic as possible to allow re-use of it by additional use cases.