...

Note:  we will no longer be using a Confluence table to track requirements. More information here.

New Cadence Terminology

• Best Practice: Design pattern recognized by the community. Should be followed by the new code.
• Global requirement: Best Practice that should be applied to whole code base during a particular release.
Spec: Functional change that is touching only a single project (formely Functional REQuirement). Require PTL decides GO/NO GO, single component impact
• 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.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.
• 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. Require PTL to decide GO/NO GO. 

Honolulu Use Cases

...