Table of Contents
Use Case Name
| PM Data Control Extension |
Use Case Key Information
| Architecture Subcommittee | Presentations and JIRA Tickets for Architecture Subcommittee made |
| ||||||||||
| Requirement JIRA | JIRA Ticket for Use Case Requirements |
|
Business Driver
This section describes Business Drivers needs.
...
ORGANIZATION MGMT, SALES STRATEGIES - There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
Development Status
| PROJECT | PTL | User Story / Epic | Requirement |
| A&AI | |||
| AAF |
No Active PTL | |||
| APPC | |||
| CLAMP | |||
| CC-SDK (incl. CDS) | |||
| DCAE | |||
| DMaaP | |||
| External API |
| MODELING | |||
Multi-VIM / Cloud | |||
| OOF | |||
| POLICY | |||
| PORTAL | |||
| SDN-C | |||
| SDC | |||
| SO | |||
| VID | |||
| VNFRQTS |
| VNF-SDK |
List of PTLs:Approved Projects
Use Case Diagram
Use cases define how different users interact with a system under design. Each use case represents an action that may be performed by a user (defined in UML as an Actor with a user persona).
...
End to End flow to be Tested
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 |
| 4 | Test Cases should include enough detail for testing team to implement the test | FAILED |
Reference
- ONAP Wiki page Template: Reference Template for UC tracking progressLicensing Management in R7