You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

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 


Use Cases 

PriorityUse CaseOwnerProjects or functional requirementsLink(s) to HLD/LLD if anyDependency (from/to) another project(s)

T-Shirt Size (star)

Project's Impact: Test Only (TO), Code (C)Committed (C)/ Partially Committed (P) or not (N) per impacted projectIf Partially or not Committed, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc)

Company

Engagement

NotesM4 Status

vFWAT&T



All: Test OnlyN/A - part of regression testsN/A - part of regression tests



vDNSAT&T



All: Test OnlyN/A - part of regression testsN/A - part of regression tests



VoLTE

China Mobile





All: Test OnlyN/A - part of regression testsN/A - part of regression tests



vCPE



All: Test OnlyN/A - part of regression testsN/A - part of regression tests



CCVPN

China

Mobile

CCVPN Use Case (Dublin)


All: Test OnlyN/A - part of regression testsN/A - part of regression tests



5GNokia Benjamin Cheung5G Use Case









BBSDavid Perez CaparrosBBS Broadband Service Use Case (Dublin)








(star) 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

PriorityFunctional RequirementOwnerProject ImpactedLink(s) to HLD/LLD if anyDependency (from/to) another project(s)T-Shirt Size (XS, S, M, L, XL) (star)Project's Impact: Test Only (TO), Code (C)Committed (C)/Partially Committed (P) or not (N) per Impacted projectsIf Partially or not Committed, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc)Company EngagementNotesM4 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 ExtensionsAjay 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









(star) 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

PriorityNon Functional RequirementOwnerProject ImpactedLink(s) to HLD/LLD if anyDependency (from/to) another project(s)T-Shirt Size (XS, S, M, L, XL) (star)Project's Impact: Test Only (TO), Code (C)Committed (C)/Partially Committed (P) or not (N) per Impacted projectsIf Partially or not Committed, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc)Company EngagementNotesM4 Status













(star) 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.
  • No labels