...

Scope

What is this release trying to address?

...

1. Platform maturity - enhance stability, performance, security etc. to strive for carrier-grade maturity.

...

1. integration of new designers under the SDC umbrella including WorkFlow/Clamp/DCAED/Policy.
2. New requirements:

   ...

   1. 1. **TBD**

   Use Cases

   SDC will contribute to support:

   ...

   SDC aims to position itself as the main design IDE in ONAP. SDC works towards creatingf creating a fully model-driven design experience.

   ...

   Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

   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.

   Indicate where your project fit within the ONAP Archiecture diagram.

   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.Image Added

   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

   Area

   Performance

   Actual Level

   Targeted Level for current Release

   How, Evidences

   Comments

   Performance

   0	0 (stretch goal - 1)		0 -- none 1 – baseline performance criteria identified and measured 2 & 3 – performance improvement plans created & implemented
   Stability	0	1 (stretch goal - 2)		0 – none 1 – 72 hours component level soak w/random transactions 2 – 72 hours platform level soak w/random transactions 3 – 6 months track record of reduced defect rate
   Resiliency	1	1 (stretch goal - 2)		0 – none 1 – manual failure and recovery (< 30 minutes) 2 – automated detection and recovery (single site) 3 – automated detection and recovery (geo redundancy)
   Security	0	1 (stretch goal - 2)		0 – none 1 – CII Passing badge + 50% Test Coverage 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls 3 – CII Gold
   Scalability	0	0 (stretch goal - 1)		0 – no ability to scale 1 – single site horizontal scaling 2 – geographic scaling 3 – scaling across multiple ONAP instances
   Manageability	0	1 (stretch goal - 2)		1 – single logging system across components; instantiation in < 1 hour 2 – ability to upgrade a single component; tracing across components; externalized configuration management
   Usability	0	1 (stretch goal - 2)		1 – user guide; deployment documentation; API documentation 2 – UI consistency; usability testing; tutorial documentation

   
   

   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.

   Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

   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 Legacy
   server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sdc and issuetype in (bug) and fixversion="Beijing Release" and status not in (closed) serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176

   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

   ...

   The project team comply with the ONAP Charter.

   Release Key Facts

   Fill out and provide a link toward the centralized Release Artifacts.