...
- Use case: High level feature that ONAP is supposed to support. Require Arch review, Req review, Impacted PTL review, all has to be GO from all the PTLs.
- Feature: Functional change that touches multiple components (formely Functional REQuirement). Require Arch review, Req review, Impacted PTL review, all has to be GO from all the PTLs.
- Spec: Functional change that is touching only a single project (formely Functional REQuirement). Require PTL to decide GO/NO GO, single component impact.
- Best Practice: Design pattern recognized by the community. Should be followed by the new code. The owner to present their best practices then TSC to review and /to approve.
- Global requirement: Best Practice that should be applied to whole code base during a particular release (formely called TSC MUST HAVE). Require The owner to present their approved best practices then TSC to review and /to approve as GR.
- POC - POC definition - Developer Wiki - Confluence (onap.org)
...