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

Compare with Current View Page History

« Previous Version 3 Next »

The page is intended to summarize all the requirements for Guilin Release.

These requirements have been prioritized by the TSC to realistically fit within the Guilin Release Timeline.

The Release Scope should be finalized during the M1 Release Planning milestone on TBD

TSC Prioritization (Ranking)

  • RANK #0  – Special GO - quick wins, fully covered by involved companies
  • RANK #1 – TSC Must Have – Mandatory for the release
  • RANK #2 – Continuity  - Items continued from previous releases
  • RANK #3 – PTL Go – items that PTLs is OK to include since team has bandwidth
  • RANK #4 – NO GO – items not approved for various reasons

Requirements Milestones Summary

See also Documenting Release Requirements in JIRA

Epic Link Fix For Versions (all)
Frankfurt Release Guilin Release Honolulu Release Istanbul Release Jakarta Release Kohn Release London Release Montreal Release New Delhi Release Istanbul Maintenance Release 1 Unscheduled T:
5G / OOF SON Enhancement 3 0 0 0 0 0 0 0 0 0 0 3
5G / ORAN & 3GPP Standards Harmonization 3 0 0 0 0 0 0 0 0 0 0 3
5G OOF SON use case requirements for Guilin release 0 1 0 0 0 0 0 0 0 0 0 1
5G Service Modeling in R8 0 0 15 0 0 0 0 0 0 0 2 17
5G SON use case enhancements for Istanbul release 0 0 0 13 0 0 0 0 0 0 0 13
5G SON use case enhancements for Jakarta release 0 0 0 0 14 0 0 0 0 0 0 14
5G SON use case enhancements for Kohn release 0 0 0 0 0 14 0 0 0 0 0 14
5G SON use case enhancements for London release 0 0 0 0 0 0 14 0 0 0 2 16
5G SON Usecase R8 0 0 16 0 0 0 0 0 0 0 2 18
A1 Adapter Extension & A1 Policy Management 0 1 0 0 0 0 0 0 0 0 0 1
A1 Policy Functions Extension - Istanbul 0 0 0 12 0 0 0 0 0 0 0 12
A1 Policy Functions Extension - Jakarta 0 0 0 0 12 0 0 0 0 0 0 12
A1 Policy Functions Extension - Kohn 0 0 1 1 1 13 0 0 0 1 0 13
A1 Policy Functions Extension - London 0 0 0 0 0 0 13 0 0 0 0 13
Add VSP Compliance and Verification Check feature Phase 2 3 0 0 0 0 0 0 0 0 0 0 3
Akraino Distributed Analytics use case 3 0 0 0 0 0 0 0 0 0 0 3
All Control Loop Policy Models should be TOSCA Compliant 3 0 0 0 0 0 0 0 0 0 0 3
APPC Ansible automation with VNF-C LCM support 3 0 0 0 0 0 0 0 0 0 0 3
Architecture - modelling alignment 7 0 0 0 0 0 0 0 0 0 0 7
ASD onboarding package IM / DM 0 0 0 0 12 0 0 0 0 0 0 12
Bulk PM / PM Data Control Extension 0 1 0 0 0 0 0 0 0 0 0 1
Bulk PM / PM Data Control Improvements 0 0 11 0 0 0 0 0 0 0 0 11
Bulk PM / PM Data Control Improvements 0 0 0 12 0 0 0 0 0 0 0 12
Bulk PM / PM Data Control Improvements 0 0 0 0 13 0 0 0 0 0 0 13
CCVPN-E-LINE Service over OTN NNI 3 0 0 0 0 0 0 0 0 0 0 3
Total Unique Issues: 196 22 248 184 189 107 187 1 1 1 84 1216
Showing 25 of 166 statistics.
Show more

View in Jira

Use Cases 

Release 6 (Guilin) proposed use cases and functional requirements

M1 Scorecard:

  • 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.

Architecture:

  • Pink - NO  GO
  • Purple - GO
  • Green - Considered OK not requiring architecture review
  • Black - Architecture not yet performed
Use Case

JIRA link (REQ)

One issue per requirement.

Instructions

Owner(s)TSC Ranking

M1

Scorecard

TSC M1 ApprovalLink(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 project


If Partially or not Committed, what are gaps/ project (people/FTEs; HLD/LLD; etc)Integration Lead

Company

Engagement

Notes


























































































(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.

Requirements

M1 Scorecard:

  • Green: The requirement will be fully implemented and tested
  • Yellow:  The requirement will be partially implemented. It is possible to identify capabilities for this functional requirement that can be tested (phasing approach).
  • Red: The requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy


Architecture:

  • Pink - NO  GO
  • Purple - GO
  • Green- Considered OK not requiring architecture review
  • Black - Architecture not yet performed
Requirement

JIRA link (REQ)

One issue per requirement.

Instructions

OwnerTSC RankingM1 ScorecardTSC M1 ApprovalLink(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), Documentation Only (DO)Committed (C)/Partially Committed (P) or not (N) per Impacted projectsIf Partially or not Committed, what are gaps/ project (people/FTEs; HLD/LLD; etc)Integration LeadCompany EngagementNotes













































































(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.

POC / Experimentation

POC definition

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