...
- 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 decides to decide GO/NO GO, single component impact.
- Best Practice: Design pattern recognized by the community. Should be followed by the new code. (To be reviewed/approved by the TSC then PTLs is OK or NOT to include)Require PTL to decide GO/NO GO.
- Global requirement: Best Practice that should be applied to whole code base during a particular release. (To be reviewed and approved by TSC - TSC MUST HAVE REQ)
...