...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Amsterdam |
| Project Lifecycle State | PlanningIncubation |
| Participating Company | AT&T, China Mobile, China Telecom, Vmware, Huawei, ZTE, Cisco, Intel, Gigaspaces, Amdocs, Nokia ,VMware,Boco,Raisecom, Techmahindra |
...
In Amsterdam, we will provide the tools for the vCPE and , VoLTE use , vFW use cases
Minimum Viable Product
Describe the MVP for this release.Tosca parsers
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.
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=modeling and issuetype in (story) serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.Support all kinds of modeling parser tools and converters
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description | |
|---|---|---|
| To fill out | To fill outtosca parser | tosca parser |
Sub-Components
List all sub-components part of this release.
Activities related to sub-component must be in sync with the overall release.
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
ONAP Dependencies
List the other ONAP projects your depends on.None
Architecture
High level architecture diagram
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
Anyone reading this section should have a good understanding of all the interacting modulesthis project only provide the tools for other project to use.
API Incoming Dependencies
List the API this release is expecting from other releases.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
...
is a tool project, nothing incoming
API Outgoing Dependencies
API this release is delivering TOSCA parser API to other releasesprojects.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |
|---|---|---|---|---|---|
| To fill out | High level description of the TOSCA parser API | TOSCA parser API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
...