...
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.
- 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.
Honolulu Use Cases
Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,assignee,arch review,tsc priority,scope status,t-shirt size,m1 scorecard,m1 approval,m2/3 scorecard,m2/3 approval,m4 scorecard,m4 approval |
---|
maximumIssues | 1000 |
---|
jqlQuery | filter=12442 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
Honolulu
...
Features
Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,assignee,arch review,tsc priority,scope status,t-shirt size,m1 scorecard,m1 approval,m2/3 scorecard,m2/3 approval,m4 scorecard,m4 approval |
---|
maximumIssues | 1000 |
---|
jqlQuery | filter=12441 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
...
Honolulu Specs
Honolulu Best Practices
Honolulu Global Requirements
Honolulu Requirements
Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,assignee,arch review,tsc priority,scope status,t-shirt size,m1 scorecard,m1 approval,m2/3 scorecard,m2/3 approval,m4 scorecard,m4 approval |
---|
maximumIssues | 1000 |
---|
jqlQuery | filter=12439 12441 |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
...