Description
Start from use case analysis for xNF License Management and derive any requirements to ONAP. The aim is for ONAP to support various types (simple, complex, vendor specific) commercial licensing models and use cases. The use cases to start with include xNF onborading, PNF introduction/ONAP PnP, VNF instantation. Based on agreed use cases review relevant ONAP xNF requirements. No impacts to ONAP components foreseen in R6 Frankfurt, potentially minor update of ONAP architecture.
BUSINESS DRIVER
Executive Summary -
Start from use case analysis for xNF License Management and derive any requirements to ONAP. The aim is for ONAP to support various types (simple, complex, vendor specific) commercial licensing models and use cases. The use cases to start with include xNF onborading, PNF introduction/ONAP PnP, VNF instantation. Based on agreed use cases review relevant ONAP xNF requirements. No impacts to ONAP components foreseen in R6 Frankfurt, potentially minor update of ONAP architecture.
Business Impact - xNF License Management is a critical business function. Agreed use cases should allow ONAP to flexibly support commercial licensing models.
Business Markets - This use case applies to any domain (wireless, transport, optical, wireline) that ONAP will manage. It is not a market specific function.
BUSINESS DRIVER
This section describes Business Drivers needs.
Executive Summary - (Give a short description of your Use Case, the "Executive 2 min elevator pitch", this describes the "WHAT")
Business Impact - (This is the Business Impact which describes why this use case is important from a business perspective, this describes the "WHY").
Business Markets - (This is the marketing analysis, which can include but not limited to applicable markets, domains, marketing projections, this can describe the "WHERE").
Funding/Financial Impacts - (The Funding requirements and Financial impacts can describe the financial savings, or CAPEX, OPEX impacts for a Use Case)The use case is fundamental for supporting efficiently business agreements between the operator and the vendor.
Organization Mgmt, Sales Strategies - (It is suggested that you use the following wording): 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. (This would typically describe the "WHO", but because use cases are all deployed with ONAP itself, these two areas come with the actual ONAP deployment and uses the organizational management and sales strategies of a particular service provider's ONAP deployment).
SUPPORTING FILES:
| View file | ||||
|---|---|---|---|---|
|
Use Case Contacts & Team
DEVELOPMENT IMPACTS
There is no expected Software Impact to any of the ONAP platform components for this Use Case, aside from possibly modeling and architecture work.
| PROJECT | PTL | User Story / Epic | Requirement |
| A&AI | |||
| AAF | |||
| APPC | |||
| CLAMP | |||
| CC-SDK | |||
| DCAE | |||
| DMaaP | |||
| External API | |||
| MODELING | Epic #1: Introduction of basic Licensing Modeling | Modeling for Licensing Management (Kevin Scaggs ) | |
Multi-VIM / Cloud | |||
| OOF | Shankaranarayanan Puzhavakath Narayanan | ||
| POLICY | |||
| PORTAL | |||
| SDN-C | |||
| SDC | |||
| SO | |||
| VID | |||
| VNFRQTS | |||
| VNF-SDK | |||
| CDS |
List of PTLs:Approved Projects
*Each Requirement should be tracked by its own User Story in JIRA
Test Cases and Status
| # | Test Case | Status | ||||||
|---|---|---|---|---|---|---|---|---|
| 1 | There should be a test case for each item in the sequence diagram |
| ||||||
| 2 | create additional requirements as needed for each discreet step |
| ||||||
| 3 | Test cases should cover entire Use Case |
| ||||||
| 4 | Test Cases should include enough detail for testing team to implement the test |
|