Requirement Types
Type | Description | Prerequisite | Review / Approval | Notes |
|---|---|---|---|---|
Feature | A change that impacts multiple components. |
| Requirements Subcommittee (M2) |
|
Specification | A change that impacts a single component. |
| Impacted PTLs (M2) |
|
Use Case | The application of one or more ONAP components to provide a specific end user solution. |
| Requirements Subcommittee (M2) |
|
Best Practice | A software development practice or instruction, that is broadly applicable, but applied to new code only (Example: use Python 3 interpreter) | Socialization with PTLs and general consensus | PTLs (nlt M1) |
|
Global Requirement | A software development practice or instruction, that is broadly applicable, applied to ALL code (Example: use Python 3 interpreter) | Previously approved as a Best Practice | PTLs (nlt M1) |
|