...
- Green: Use Case will be fully implemented and tested
- Yellow: Use Case will be partially implemented. Testing will be performed on the new developed 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 | vFW | Policy/(APPC) HPA | vFirewall Use Case Upgrade | XS | All: Test Only except Policy APPC(TO) | Policy: Committed | Policy: Committed | AT&T | ||||||
1 | vDNS | Integration Team | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | ||||||||
1 | VoLTE | Integration Team | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | ||||||||
1 | vCPE with or without TOSCA | Integration Team | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | ||||||||
2 | 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 | 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 : Committee based on contributions from Huawei and ZTE VF-C: Committed Modeling: Committed Usecase-UI: Committed Holmes Multi-VIM/Cloud: Committed based on VMware contribution Policy: Committed base on Huawei contribution | SDC: not enough resources | Dev/Test privided by Chinamobile, Vodafone, Huawei, ZTE, WindRiver, VMWare, Intel, Lenovo, ChinaTelecom, Fujitsu | ||||||
2 | 5G | SDC, SO, VNFSDK, AAI, DCAE, SDNC,CCSDK,VID, PORTAL, AAI/ESR, VFC,APPC, DMaaP, Policy | 5G Use Case | AAI: M | SDC: Committed based on Nokia/Ericsson/Amdocs contribution DCAE: Committed based on Ericsson contribution for 5G - Bulk PM (Casablanca carry-over items) and Wipro contribution on - 5G - OOF and PCI SO: Partial Committed based on the contributions from Nokia (to be confirmed) AAI: Partially committed CCSDK/SDN-C : Committed to Tosca ingest changes PORTAL: Partial committed VID: Partial committed Policy: Committed based on wipro contribution | SO: Resource commitment to be confirmed AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability PORTAL: Targets only the top menu integration required for 5G use case functions from VID and SDC/AAI VID: No enhancements dev | - Benjamin Cheung I added policy because my understanding from N.K. Shankaranarayanan there are additions for 5G - OOF and PCI | |||||||
0 | BBS | David Perez Caparros | DCAE, ExternalAPI, Modeling, SDNC, SO | BBS Broadband Service Use Case (Dublin) | PRH - 5G Use Case | AAI: TO DCAE: C ExtAPI: C SDC: TO SO (using 5G use case PNF discovery and re-registration): TO (to be confirmed) Policy: TO CLAMP: TO SDNC w/new DG: TO (to be confirmed) Modeling: design | DCAE: Committed based on contribution from Huawei, TechM and Nokia ExternalAPI: Committed SO: Committed based on the contributions from Nokia /Huawei? 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 |
...
- Green: The functional requirement will be fully implemented and tested
- Yellow: The functional requirement will be partially implemented. Testing will be performed on the new developed It is possible to identify capabilities for this use case functional requirement that can be tested (phasing approach).
- Red: The functional requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy
...
- Green: The non-functional requirement will be fully implemented and tested
- Yellow: The non-functional requirement will be partially implemented. Testing will be performed on the new developed It is possible to identify capabilities for this use case non-functional requirement can be tested (phasing approach).
- Red: The non-functional requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy
...