...

Candidate requirement proposals will be frozen on October 1st, 2020.

These requirements will be prioritized by the TSC to realistically fit within the Honolulu Release by xx

The Release Scope should be finalized during the M1 Release Planning milestone on xx January 11th, 2020.

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

...

• 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 Must be followed by the new code associated to new container(s). The owner best practice owners to present their best practices then practice to the PTLs and then to the TSC to review/to approve as best practice.
• Global requirement: Best Practice that
should
• must be applied to whole code base during a particular release (formely called TSC MUST HAVE). The
owner
• best practice owners to present their approved
best practices then 
•  best practices to the PTLs and then to the TSC to review/to approve as GR at M1.
• POC - POC definition - Developer Wiki - Confluence (onap.org)

Honolulu Use Cases

...

...

Honolulu Best Practices

...

Candidates

...

...

...