...
The Requirements extracted from SP lists of priorities for Casablanca are covered either by the Use Case, the functional requirements, the non functional requirement or within a project scope of work.
Use Case
| Use Case | Owner | Projects or functional requirements Impacted for Casablanca |
|---|
| Link(s) to High Level Design (HLD) /Low Level Design (LLD) (if any) | Committed (C)/Partially Committed (P) or not (N) per Impacted projects | If Partially or not Committed, |
|---|
| then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc) | Notes | |||||
|---|---|---|---|---|---|---|
| vFW | AT&T | HPA | N/A | N/A | ||
| vDNS | AT&T | HPA | N/A | N/A | ||
| VoLTE | China Mobile | HPA | N/A | N/A | ||
| vCPE | Kang Xi | HPA | N/A | N/A | ||
| CCVPN | DCAE, SO,...? NOTE: No project should be code impacted by this use case. | Contingent that Use Case owner are able to add resources on impacted projects and Integration agreement | ||||
| OSAM | SO, Portal, External API, APPC, DCAE HPA **NOTE: Based on Arch review, no projects should be code impacted | Contingent that Use Case owner are able to add resources on impacted projects and Integration agreement |
Functional Requirements
| Functional Requirements | Owner | Projects Impacted for Casablanca | Links to HLD/LLD Link(s) to High Level Design (HLD) /Low Level Design (LLD) (if any) | Priority (from SP perspective) | Committed (C)/Partially Committed (P) or not (N) per Impacted projects | If Partially or not Committed, how many FTE are required then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc) | Notes |
|---|---|---|---|---|---|---|---|
| HPA | VNFSDK (minor), SDC (minor), Policy, OOF (minor), SO (minor) | Orange: 2 ATT: 2 China Telecom: 2 China Mobile: 1 Verizon: 2 Vodafone: 2 | |||||
| Change Management | SDC, SO, VID, SDNC, APPC, VNFSDK, OOF | Orange: 1 ATT: 1 China Telecom: 2 China Mobile: 2 Verizon: 1 Vodafone: 2 | |||||
| Scaling | Link to Slides | Orange: 1 ATT: 1 China Telecom: 1 China Mobile: 1 Verizon: 3 Vodafone: 1 | |||||
| 5G/PNF | SDC, SO, DCAE, SDN-C, App-C, A&AI, CDT, Modeling | Orange: 2 ATT: 1 China Telecom: 3 China Mobile: 1 Verizon: 1 Vodafone: 2 | |||||
| 5G/performance Analysis and Optimization | DCAE, OOF, SDN-R | Orange: 2 ATT: 2 China Telecom: 1 China Mobile: 3 Verizon: 3 Vodafone: 3 | |||||
| 5G/Network slicing | Withdrawn from Casablanca release by the requirement owner | Orange: 3 ATT: 3 China Telecom: 1 China Mobile: 2 Verizon: 2 Vodafone: 3 | |||||
Centralized Representation and Consistent ID of Cloud Regions | SO,VID,SDNC,OOF,VFC, UUI,MultiCloud, DCAE, DMaaP, Integration | Centralized Representation and Consistent Identification of Cloud Regions In ONAP | Orange: 1 ATT: 2 China Telecom: 2 China Mobile: 3 Verizon: 1 Vodafone: 1 | ||||
| EA/Cloud Infrastructure for Distributed Edge Clouds (5G etc.) | Policy, Multi-Cloud, A&AI, ESR, OOF, SO, DCAE, OOM (minor) | Orange: 3 ATT: 3 China Telecom: 3 China Mobile: 3 Verizon: 2 Vodafone: 1 |
...
Non Functional Requirements
| Non Functional Requirements | Owner | Sub-category | Project Impacted for Casablanca |
|---|
| Link(s) to High Level Design (HLD) /Low Level Design (LLD) (if any) | Committed (C)/Partially Committed (P) or not (N) per Impacted projects | If Partially or not Committed, |
|---|
| then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc) | Notes | ||||||
|---|---|---|---|---|---|---|---|
| S3P |
| Likely ALL depending upon TSC determination of new level requirements per category | |||||
| Security | Note: This does not cover what is in S3P. However based on that it is expected to use CADI to get certificates to enable secure communication Pluggable authentication and Authorization (Use of CADI and ?): All projects Secure communication to xNFs (Security for 5G Use cases). DCAE, APPC, VFC? VNF requirements. (Secure Communication to Network Functions) Vnf package security following SOL 004: SDC, VNF reqs, VNF SDC | ||||||
| Upgrade (from Beijing to Casablanca) | |||||||
Architecture Alignment |
| Materials. | |||||
| HEAT support ? | HEAT-based ONAP deployment support should be dropped once OOM-based ONAP deployment's issues are fully identified and resolved. Recommendation from TSC: keep supporting HEAT in Casablanca for testing and integration purposes. However, HEAT won't be a gating item at Release Sign-Off. | ||||||
| Tao Shen |
|
Note: This will need to go through the whole process (Architecture review,...) to understand what the sdk will be providing and dependencies on other ONAP project (Portal, SDC,...) | |||||
| Testing | Helen Chen |
| Most UI projects with javascript. Recommendation from TSC: This is related to Code Coverage: recommendation is to keep 50% Code Coverage for Casablanca including JavaScript. (In Beijing Release code coverage was only covering Java and Python code) | ||||
|
Note: no owner. | ||||||
|
Note: this is either a project or a sub-project but not a non-functional requirements. |