...
- Green: Use Case will be fully implemented and tested
- Yellow: Use Case will be partially implemented. It is possible to identify capabilities for this use case that can be tested (phasing approach).
- Red: Use Case can not be partially delivered, min. requirements can not be met in order to define a testing strategy.
Priority | M1 Scorecard | TSC M1 Approval | Use Case | Owner | Projects or functional requirements impacted for Dublin | Link(s) to HLD/LLD if any | Dependency (from/to) another project(s) | T-Shirt Size | Project's Impact: Test Only (TO), Code (C) | Committed (C)/ Partially Committed (P) or not (N) per impacted project | If Partially or not Committed, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc) | Company Engagement | Notes | M4 Status |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1-regression 3-enhancements | HPA Testing confirmed by INTEL | vFW | Policy/(APPC) HPA | vFirewall Use Case Upgrade | XS | All: Test Only except Policy APPC(TO) | Policy: Committed | Policy: Committed | AT&T | |||||
1 | HPA HPA Testing confirmed by INTEL | vDNS | Integration Team | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | |||||||
1 | Not part of Dublin scope - no regression test | VoLTE | Integration Team | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | |||||||
1 | Not part of Dublin scope - no regression test | vCPE with TOSCA | Integration Team | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | ||||||||
1 | HPA Testing confirmed by INTEL | vCPE (Heat) | Integration Team | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | |||||||
2 | Davide/Lin to review and provide final feedback | CCVPN Use Case (Dublin) High priority:1, SD-WAN Multi-site to Multi-site service creation; 2, Service change: add or delete a site;3, close loop intelligent surveillance | SDC, SO, SDN-C,OOF,ExternalAPI, UUI, ESR,Modeling,MultiVIM/Cloud, VFC, Modeling, DCAE, Policy, Holmes, Consistent ID of a cloud region | CCVPN Use Case (Dublin) | AAI: M | AAI: TO DCAE: TO ExtAPI: TO Multi-VIM: Test support Holmes: C | SDC: Partially committed based on Chinamobile/ZTE/Vodafone contribution SO: Committed based on the contributions from CMCC, ZTE and VDF for the main flows SDN-C/CCSDK : Committed based on contributions from Huawei and ZTE VF-C: Committed Modeling: Committed Usecase-UI: Committed Holmes: Committed based on Huawei and ZTE contribution Multi-VIM/Cloud: Committed based on VMware contribution Policy: Committed base on Huawei contribution ExtAPI: Committed as long as a serviceOrder is created, either for service creation or modification with full service characteristics and values. ExtAPI can not read service characteristic and service state from AAI which does not expose those informations. | SDC: not enough resources | Dev/Test provided by Chinamobile, Vodafone, Huawei, ZTE, WindRiver, VMWare, Intel, Lenovo, ChinaTelecom, Fujitsu | |||||
2 | 5G Use Case (Dublin) | 5G: PNF Pre-onboarding Onboarding | SDC, VNFSDK, VNFRqmt (Docs) | 5G - PNF Pre-Onboarding & Onboarding | BBS | SDC: C VNFSDK: C | SDC: Committed based on Nokia/Ericsson contribution VNFSDK: Committed | AT&T, Huawei, Ericsson, Nokia | PNF POB/OB U/C is now in development, requirements and architecture stage with high corporate commitment. | |||||
2 | 5G Use Case (Dublin) | 5G: Bulk PM | DCAE, DMaaP, VNFRqmt | 5G - Bulk PM (Casablanca carry-over items) | 5G: PM Dictionary | DCAE: C DMaaP: C | DCAE: Committed based on Ericsson contribution DMaaP: Committed | AT&T, Ericsson, Nokia | Bulk PM is in development with high corporate commitment. | |||||
2 | 5G Use Case (Dublin) | 5G: Config w/ NetConf | Oskar Malm | SDC, (VID), SO |
, SDNC, CCSDK, VNFRQTS | 5G - Configuration with NETCONF | 5G: PNF PnP |
SDC: C (VID) SO: C |
SDNC: C |
CCSDK: C |
SDC: depends on CDS (interaction) Partial
VID: depends on CDS to define W/F. Partial
SO: Commit: PNF configuration committed (some CDS dependencies)
SDNC: NETCONF/TLS support in controller committed from Ericsson Additional development for PNF configuration UC is coordinated with CDS / e2e automation. See separate line for details. PNF configuration testing: Ericsson |
AT&T, Ericsson | NetConf is in development with high corporate commitment | |||||||||||||
2 | 5G Use Case (Dublin) | 5G: FM Meta PM Dictionary | SDC, VNFRqmt, VES Specification (Done) | 5G - FM Meta Data / 5G - PM Dictionary | 5G: Bulk PM 5G: PNF OB | SDC: C | SDC: Commit | AT&T, Ericsson, Nokia | FMPM Dictionary is in development with high corporate commitment | |||||
2 | 5G Use Case (Dublin) | 5G: OOF & PCI | SDC, APP-C, DCAE, OOF, Policy, VNFRqmt | 5G - OOF and PCI (Casablanca carry-over items) | 5G: PNF OB Control Loop U/C | SDC: C SDN-C: C DCAE: C OOF: C Policy: C | SDC: Commit SDN-C: Commit DCAE: Committed based on Wipro contribution OOF: Commit Policy: Committed based on Wipro contribution | AT&T, Wipro, Tech Mahindra | OOF/PCI Enhancements is in development with high corporate commitment Dublin Release Requirements I added policy because my understanding from Dublin Release Requirements there are additions for 5G - OOF and PCI | |||||
2 | 5G Use Case (Dublin) | 5G: PNF Plug and Play & PNF Re-registration | Benjamin Cheung | SDC, Portal, VID, SO, A&AI, SDN-C, DCAE | 5G - PNF Plug and Play (Casablanca carry-over items) | BBS | SDC: C Port: C VID: C SO: C A&AI: C SDN-C: C DCAE: C AAF: C | SDC: Commit Portal: Partial VID: Partial SO: Committed based on the contributions from Nokia (to be confirmed) A&AI: Commit CCSDK/SDN-C : Committed to Tosca ingest changes DCAE: Committed based on the contributions from Nokia AAF: Commit | AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability (Jan 30 James Forsyth has ok'ed A&AI commitment) PORTAL: Targets only the top menu integration required for 5G use case functions from VID and SDC/AAI VID: No enhancements dev | AT&T, Huawei, Ericsson, Nokia | PNF PNP Enhancements is in development with high corporate commitment | |||
2 | 5G Use Case (Dublin) | 5G: Network Slicing | Borislav Glozman | SDC, Modeling Sub-committee | 5G - Slicing | SDC: C Model: TO | SDC: Commit Model: Commit | AT&T, Amdocs, Ericsson | Network Slicing has only modeling work that is being done in R4. | |||||
2 | 5G Use Case (Dublin) | #action - Final assessment to be provided by 2/4 during the PTL Call | 5G (see above rows) | |||||||||||
0 | #action (Chaker): Add a risk concerning dependenecy with 5G Use Cases | BBS | David Perez Caparros | DCAE, ExternalAPI, Modeling, SDNC, SO | BBS Broadband Service Use Case (Dublin) | PRH - 5G Use Case | AAI: DCAE: C ExtAPI: C SDC: TO SO (using 5G use case PNF discovery and re-registration): TO Policy: TO CLAMP: TO SDNC: C Modeling: design | DCAE: Committed based on contribution from Huawei, TechM and Nokia ExternalAPI: Committed SO: 5G PNF Committed based on the contributions from Nokia /Huawei SDNC: Committed based on contributions from BBS team Modeling: contributions from Swisscom/Huawei/Nokia | AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability | Nokia, Swisscom, Huawei, |
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
...