...
| TOPIC | DESCRIPTION | WIKI PAGE | ||||||||
| Requirements Proposal | This is a link to the requirements proposal made on the Requirements Sub-committee | ONAP_OOF_SON_R10_Requirements_2021117_v1.1.pptx | ||||||||
| Architecture S/C info | Information on the Architecture sub-committee presentation | Wiki page | ||||||||
| Prior Project "Base" Wiki | Link to the Honolulu 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: N.K. Shankaranarayanan, krishna moorthy USE CASE KEY CONTACTS: N.K. Shankaranarayanan | |||||||||
| Meetings Register & Recordings | Link to Use Case Team meetings. |
|
...
| PROJECT | PTL | User Story / Epic | Requirement | ||||||||
| A&AI | No impact | ||||||||||
| AAF | No impact | ||||||||||
| APPC | No impact | ||||||||||
| CLAMP | No impact | ||||||||||
| CC-SDK |
| (Carryover work): Incorporate new Yang model in edit-config to RANSim. Stretch goal for processing CMNotify update. | |||||||||
| DCAE |
| Develop stndDefined VES message formats for FM/PM/CM. Stretch goal to modify SON-Handler MS and RAN-Sim for FM/PM. | |||||||||
| DMaaP | No impact | ||||||||||
| External API | No impact | ||||||||||
| HOLMES | No impact | ||||||||||
| MODELING | No impact, CPS related modeling aspects will be covered by CPS project | ||||||||||
Multi-VIM / Cloud | No impact | ||||||||||
| OOF | No impact | ||||||||||
| OOM | No impact | ||||||||||
| POLICY | No impact | ||||||||||
| PORTAL | No impact | ||||||||||
| SDN-C | No impact | ||||||||||
| SDC | No impact | ||||||||||
| SO | No impact | ||||||||||
| VID | No impact | ||||||||||
| VF-C | No impact | ||||||||||
| VNFRQTS | No impact | ||||||||||
| VNF-SDK | No impact | ||||||||||
| CDS | No impact | ||||||||||
| CPS | Models, and interface to store/retrieve OOF SON use case related data |
List of PTLs:Approved Projects
*Each Requirement should be tracked by its own User Story in JIRA
...
**This should be a summary level Sequence diagram done in Gliffy** 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 |
...
| Date | Description | File | |
|---|---|---|---|
| Mar 29, 2021 | Presentation given to Requirements Sub-committee | ||
| May 21, 2021 | Yang models and CPS APIs for SON (links) | ||
| June 1, 2021 | June 1ArchCom | Add file | |
| Nov 3, 2021 | ONAP_SON_R9_ArchCom_20210601_v1.0ITU-T FG AN presentation on SON Use Case |