...
The content of this template is expected to be fill out for M1 Release Planning Milestone.
| Info | ||
|---|---|---|
| ||
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki. |
| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Enter the name of the release you are targeting to deliverDublin |
| Project Lifecycle State | Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company List the company participating in this release. At least 3-4 organizations, including an operator are recommended. | AT&T Ericsson, Nokia, China Mobile, Amdocs |
Scope
What is this release trying to address?
Describe the problem being solved by this release
Use Cases
The Dublin release of VNFRQTS project will address the following items:
- bug fixes, maintenance and feature alignment of VNF Guidelines, VNF Requirements and VNF Test Descriptions consistent with the rest of the ONAP Dublin release.
- The VNF Provider Use cases for Autoscaling to be documented with associated VNF Requirements
- The VNF Test Descriptions appendix to be updated to reflect test implementations planned for Dublin by other projects ( VVP, VNFSDK, etc.)
- Toolchain improvements for the management of VNF Requirements
- Categorization of VNF Requirements to support ONAP VNF Badging & certification initiatives
Use Cases
The set of E-E use cases for ONAP Dublin release is discussed by the ONAP TSC Use case committee hereDescribe the use case this release is targeted for (better if reference to customer use case).
Minimum Viable Product
The ONAp VNFRQTS Project will deliver the following documentation as its minimum viable product:
VNF Guidelines.
VNF Requirements.
VNF Test Descriptions.
VNF Provider Use CasesDescribe the MVP for this release.
Functionalities
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
...