...

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.

New Cadence Terminology

• 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
• 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 to decide GO/NO GO, single component impact.
• 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.
• Best Practice: Design pattern recognized by the community. Must be followed by the new code associated to new container(s). The best practice owners to present their best practice to the PTLs and then to the TSC to review/to approve as best practice.
• Global requirement: Best Practice that must be applied to whole code base during a particular release (formely called TSC MUST HAVE). The best practice owners to present their approved 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 Features

<Query under construction>

Honolulu Specs

Jira
server ONAP JIRA columns key,summary,assignee,arch review,tsc priority,scope status,t-shirt size,m1 approval,m2 approval,m3 approval,status maximumIssues 1000 jqlQuery filter=12472 serverId 425b2b0a-557c-3c0c-b515-579789cceedb

Honolulu Specs

Honolulu Best Practices

...

Candidates

Honolulu Global Requirements

<Query under construction>

Honolulu PoC

Honolulu PoC

...