...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Beijing |
| Project Lifecycle State | PlanningIncubation |
| Participating Company | Amdocs, AT&T, ZTE, Huawei, China Mobile, Boco, Orange, Intel |
Scope
What is this release trying to address?
...
- Platform maturity - enhance stability, performance, security etc. to strive for carrier-grade maturity.
- integration of new designers under the SDC umbrella including WorkFlow/Clamp/DCAED/Policy.
- New requirements:
- **TBD**
Use Cases
SDC will contribute to support:
...
SDC will continue to support:
Use Case: Residential Broadband vCPE (Approved)
Minimum Viable Product
Describe the MVP for this release.
...
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspectiveSDC aims to position itself as the main design IDE in ONAP. SDC works towards creating a fully model-driven design experience.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description | Deliverable Location |
|---|---|---|
| SDC Docker Images |
| Executable | Docker image available |
| on nexus3 | ||
| SDC TOSCA SDK | JAR file | Available on nexus as MAVEN dependency |
| Java Source Code | The Java code for the main SDC components. | sdc Git |
| repositories | ||
| Deployment Scripts | Chef recipes used to configure the Docker containers. | sdc Git |
| repositories |
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 and are consolidate consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
ONAP Dependencies
...
subcomponents:
- Jtosca
- SDC Tosca
- SDC Distribution Client
- SDC base docker
- SDC titan cassandra
- SDC workflow designer
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 modules.
...
Platform Maturity
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance | 0 | 0 (stretch goal - 1) |
| |
| Stability | 0 | 1 (stretch goal - 2) |
| |
| Resiliency | 1 | 1 (stretch goal - 2) |
| |
| Security | 0 | 1 (stretch goal - 2) |
| |
| Scalability | 0 | 0 (stretch goal - 1) |
| |
| Manageability | 0 | 1 (stretch goal - 2) |
| |
| Usability | 0 | 1 (stretch goal - 2) |
|
API Incoming Dependencies -TBD
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.
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
API Outgoing Dependencies -TBD
API this release is delivering to other releases.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
Third Party Products Dependencies -TBD
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
...
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
Testing and Integration Plans -TBD
Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.
...
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Risks -TBD
List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| To fill out | To fill out | To fill out |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...