The page is intended to summarize all the requirements for Dublin Release.
These requirements have been prioritized by the TSC to realistically fit within the Dublin Release Timeline: Dublin Proposed Scope_V11_Draft.xlsx
This is not yet the Dublin Release scope. Release Scope will be finalized by M1 Release Planning.
Projects intended to participate within Dublin release are posted in wiki.
New projects proposal are posted here. These projects need to be reviewed and approved by TSC.
Some of the Use Cases, Functional and non functional requirements are carried over from previous releases as they required multiple releases to be implemented.
The Requirements extracted from SP lists of priorities for Dublin are covered either by the Use Case, the functional requirements, the non functional requirement or within a project scope of work.
- Use Cases
- Functional Requirements
- Non Functional Requirements
TSC Prioritization
- RANK #0 – Special GO - fully covered by involved companies
- RANK #1 – GO “Must Have”
- RANK #2 - GO “Continuity of previous releases”
- RANK #3 –GO if PTLs are OK since the impacted applications are less “stretched” i.e. CLAMP, Policy, DCAE etc.
- RANK #4 – NO GO – Mostly new requirements/features/projects
Use Cases
| Priority | 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 | AT&T Marco Platania | Policy/(APPC) HPA | XS | All: Test Only except Policy/(APPC) | Policy: Committed (APPC): ? | Policy: Committed (APPC): ? | AT&T | ||||
| 1 | vDNS | AT&T | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | AT&T | |||||
| 1 | VoLTE | China Mobile | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | ||||||
| 1 | vCPE | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | |||||||
| 2 | CCVPN | China Mobile | CCVPN Use Case (Dublin) | |||||||||
| 2 | 5G | Nokia Benjamin Cheung | 5G Use Case | |||||||||
| 0 | BBS | David Perez Caparros | AAI, CLAMP, DCAE,ExternalAPI, SO, Policy, OOF, ExternalAPI | BBS Broadband Service Use Case (Dublin) | Nokia, Swisscom, Huawei |
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
- XS - <4 Man/Weeks;
- S - ~6 Man/Weeks;
- M - ~8 Man/Weeks;
- L - ~12 Man/Weeks;
- XL - > 12 Man/Weeks.
Functional Requirements
| Priority | Functional Requirement | Owner | Project Impacted | Link(s) to HLD/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 | M4 Status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Consistent ID of a Cloud Region (Dublin) | Bin Yang | |||||||||||
| Continuation of HPA (Dublin) | Alexander Vul | |||||||||||
| Scaling Use Case (Dublin) | Scott Blandford | |||||||||||
| K8S based Cloud Region Support | ||||||||||||
| Distributed Analytics as a Service (Dublin Summary) - Edge Automation | ||||||||||||
| Change Management Dublin Extensions | Ajay Mahimkar | |||||||||||
| Ease of creating analytic components and on-boarding DCAE micro services (part of Close Loop sub-committee) | Adam Krysiak | |||||||||||
| Model driven Control Loop Design (part of Close Loop sub-committee) | Gervais-Martial Ngueko |
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
- XS - <4 Man/Weeks;
- S - ~6 Man/Weeks;
- M - ~8 Man/Weeks;
- L - ~12 Man/Weeks;
- XL - > 12 Man/Weeks.
Non-Functional Requirements
| Priority | Non Functional Requirement | Owner | Project Impacted | Link(s) to HLD/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 | M4 Status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Improve our E2E Process Automation | AAI, SO, SDC, APPC, VFC, CCSDK + Documentation | TSC 2018-12-20 Meeting Agenda | |||||||||
| 1 | ||||||||||||
| 1 | ||||||||||||
| 1 | ||||||||||||
| Security Subcommittee |
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
- XS - <4 Man/Weeks;
- S - ~6 Man/Weeks;
- M - ~8 Man/Weeks;
- L - ~12 Man/Weeks;
- XL - > 12 Man/Weeks.