...
TOPIC | DESCRIPTION | WIKI PAGE | ||||||||
Requirements Proposal | This is a link to the requirements proposal made on the Requirements Sub-committee | |||||||||
Architecture S/C info | Information on the Architecture sub-committee presentation | |||||||||
Prior Project "Base" Wiki | Link to the Istanbul release page for this use case | |||||||||
Requirements Jira (REQ-###) Ticket | Link to the REQ Jira ticket for this use case |
| ||||||||
Key Use Case Leads & Contacts | USE CASE LEAD: Kevin Tang , LIN MENG Ahila P USE KEY CONTACTS: Kevin Tang , LIN MENG , Ahila P , Henry Yu , Dong Wang , Borislav Glozman LIN MENG | |||||||||
Meetings Register & Recordings | Link to Use Case Team meetings. | J-release: E2E Network Slicing use case weekly meetings (Dec - May 2022) I-release: E2E Network Slicing use case weekly meetings (May - Oct 2021) |
...
PROJECT | PTL | User Story / Epic | Requirement | ||||||||
A&AI | No impact | ||||||||||
AAF | No impact | ||||||||||
APPC | No impact | ||||||||||
CC-SDK |
| CPS integration in RAN Slicing | |||||||||
CPS | Toine Siebelink |
| Using CPS-NCMP from TBDMT to store/read RAN configurations | ||||||||
DCAE |
| Capacity based NSI/NSSI Selection | |||||||||
DMaaP | Mandar Sawant (Old) → Fiachra Corcoran (New) | No impact | |||||||||
External API | No impact | ||||||||||
HOLMES | No impact | ||||||||||
MODELING | No impact | ||||||||||
Multi-VIM / Cloud | No impact | ||||||||||
OOF |
| Capacity based NSI/NSSI Selection | |||||||||
OOM | No impact | ||||||||||
POLICY/CLAMP | Liam Fallon | No impact | |||||||||
PORTAL | No impact | ||||||||||
SDN-C | No impact | ||||||||||
SDC | No impact | ||||||||||
SO |
| Dynamic endpoints discovery, OOF involvement in TN slicing, TN model enhancements, Support for activation, deactivation scenarios in external NSSMFs | |||||||||
VID | No impact | ||||||||||
VF-C | No impact | ||||||||||
VNFRQTS | No impact | ||||||||||
VNF-SDK | victor gao (Old) → Former user (Deleted) (New) | No impact | |||||||||
CDS | No impact |
List of PTLs:Approved Projects
*Each Requirement should be tracked by its own User Story in JIRA
...
Gliffy | ||||||
---|---|---|---|---|---|---|
|
Test Cases and Status
1 | There should be a test case for each item in the sequence diagram | NOT YET TESTED |
2 | create additional requirements as needed for each discreet step | COMPLETE |
3 | Test cases should cover entire Use Case | PARTIALLY COMPLETE |
...