...
| Non Functional Requirements | Owner | Sub-category | Project Impacted for Casablanca | Link(s) to High Level Design (HLD) /Low Level Design (LLD) (if any) | Dependency (from/to) another project(s) | T-Shirt Size (XS, S, M, L, XL)* | Project's Impact: Test Only (TO), Code (C) | 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) | Company Engagement | Notes | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| S3P |
| Likely ALL depending upon TSC determination of new level requirements per category | Usability: New API’s adhere to Versioning strategy Manageability: Adherence to ONAP Logging Spec v1.2 | Portal: on AAF, MUSIC, OOM VID, Policy, SDC, AAI: on Portal | Portal: L | Portal: C | Portal: N | Portal: Limited resources | Portal: Looking for resources who can help with adhering logging standards, API versioning and kubernetes deployment of Portal dockers. | ||||||||
| Security | Note: This does not cover what is in S3P. However based on that it is expected to have a certificate or use CADI to get certificates to enable secure communication Pluggable authentication and Authorization (Use of CADI and ?):
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 | CADI/AAF Integration:
| Portal: on AAF Test coverage (js): (1) js Sonar plug-ins activation (2) min. 3 additional containers per application => Jenkins enhancements (3) Maven build to be updated | Test coverage (js): All: M/L | Portal: C | Portal: N | Portal: Limited resources | Portal: Looking for resources who understand the AAF based certificate management to upgrade using CADI client in Portal. | |||||||||
| Upgrade (from Beijing to Casablanca) | All: XL | ||||||||||||||||
Architecture Alignment |
|
| |||||||||||||||
| 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. | Portal: on OOM | Portal: M | Portal: C | Portal: N | Portal: Limited resources | Portal: Switching CSIT jobs from using HEAT based to OOM based requires resources who can understand the current setup. | ||||||||||
| Internationalization language support | Tao Shen |
| Design language/internationalization component in Portal and provide service apis to partnering apps like Policy, VID, SDC, AAI 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,...) As per Lingli and Tao from chinamobile, this is reviewed and approved by Arch Team. | UsecaseUI: on Portal | Portal: L | Portal: C | Portal: C | Portal: AT&T, ChinaMobile | Portal: Policy, VID, SDC, AAI can choose to use this Internationalization feature based on their capacity. Only UsecaseUI team is committed to develop and use this feature for now in Casablanca. | ||||||||
| 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) | Portal: XL | Portal: C | Portal: P | Portal: Limited resources | Portal: AT&T, IBM, TechM | Portal: UI projects may depend on Portal team for pairwise testing |
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
...