Use Case Definition
- Brian Hedstrom
The following use cases are work in progress.
Table of Contents
- 1 Table of Contents
- 2 Amsterdam Use Cases
- 2.1 Detailed Use Case Definitions
- 2.1.1 Design VNF Package
- 2.1.2 Upload New VNF Package
- 2.1.3 Update Existing VNF Package
- 2.1.4 Manage Marketplace Users (Deferred)
- 2.1.5 Manage Marketplace VNF Package Content
- 2.1.5.1 Onboard VNF Package
- 2.1.5.1.1 Validate VNF Package
- 2.1.5.1.2 Test VNF Package Lifecycle
- 2.1.5.1.3 Test VNF Package Function
- 2.1.5.1 Onboard VNF Package
- 2.1.6 Download New VNF Package
- 2.1.7 Receive Update Alerts (Deferred)
- 2.1.8 Download Updated VNF Package (Deferred)
- 2.2 Use Case Personas
- 2.2.1 VNF Supplier
- 2.2.2 Marketplace Operator
- 2.2.3 Service Provider
- 2.1 Detailed Use Case Definitions
Amsterdam Use Cases
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).
Detailed Use Case Definitions
This section defines each use case in greater details.
Design VNF Package
Section | Description |
|---|---|
ID | VNF-SDK-UC-01 |
Title | Design VNF Package |
Description | In this use case, the VNF supplier uses the TOSCA Common Toolkit or the VNF SDK to design and create a new VNF package which performs a specified network function. |
Primary Actor | VNF Supplier |
Preconditions | |
Main Success Scenario | |
Alternate Scenarios | |
Exception Scenarios | |
Post Conditions | A fully designed and specified VNF package ready for the market. |
JIRA Traceability |
Upload New VNF Package
Section | Description |
|---|---|
ID | VNF-SDK-UC-02 |
Title | Upload New VNF Package |
Description | In this use case, the VNF Supplier uploads the market-ready VNF package to the marketplace staging area. |
Primary Actor | VNF Supplier |
Preconditions | |
Main Success Scenario | |
Alternate Scenarios | |
Exception Scenarios | |
Post Conditions | VNF package resides in the staging area of the marketplace and Marketplace Operator has been notified |
JIRA Traceability |
Update Existing VNF Package
Section | Description |
|---|---|
ID | VNF-SDK-UC-03 |
Title | Update Existing VNF Package |
Description | In this use case, the VNF Supplier needs to update a VNF package that has already been published, perhaps fixing a defect in the existing package, or adding a new feature to the package. |
Primary Actor | VNF Supplier |
Preconditions | |
Main Success Scenario | |
Alternate Scenarios | |
Exception Scenarios | |
Post Conditions | The updated VNF package resides in the staging area of the marketplace and Marketplace Operator has been notified |
JIRA Traceability |
Manage Marketplace Users (Deferred)
Section | Description |
|---|---|
ID | VNF-SDK-UC-04 |
Title | Manage Marketplace Users |
Description | |
Primary Actor | Marketplace Operator |
Preconditions | |
Main Success Scenario | |
Alternate Scenarios | |
Exception Scenarios | |
Post Conditions | |
JIRA Traceability |
Manage Marketplace VNF Package Content
Section | Description |
|---|---|
ID | VNF-SDK-UC-05 |
Title | Manage Marketplace VNF Package Content |
Description | In this Use Case, the Marketplace Operator has the responsibility of managing all VNF Package Content in the marketplace. |
Primary Actor | Marketplace Operator |
Preconditions | |
Main Success Scenario | |
Alternate Scenarios | |
Exception Scenarios | |
Post Conditions | All new and updated VNF package content is managed and controlled according to Marketplace Operator policies. |
JIRA Traceability |
Onboard VNF Package
Section | Description |
|---|---|
ID | VNF-SDK-UC-05-01 |
Title | Onboard VNF Package |
Description | In this Use Case, the Marketplace Operator onboards a VNF package placed in the staging area (e.g., newly uploaded package). |
Primary Actor | Marketplace Operator |
Preconditions | |
Main Success Scenario | |
Alternate Scenarios | |
Exception Scenarios | |
Post Conditions | The new VNF package has been successfully onboarded |
JIRA Traceability | VNFSDK-29: Align VNF packaging tools with new VNF packaging modelClosed VNFSDK-27: Support handoff to SDC for VNF onboarding (may need TOSCA/HEAT translator)Closed |
Validate VNF Package
Section | Description |
|---|---|
ID | VNF-SDK-UC-05-01-01 |
Title | Validate VNF Package |
Description | In this Use Case, the Marketplace Operator validates the VNF package to ensure it complies with package rules. |
Primary Actor | Marketplace Operator |
Preconditions | |
Main Success Scenario | |
Alternate Scenarios | |
Exception Scenarios | |
Post Conditions | The VNF package is validated. |
JIRA Traceability | VNFSDK-31: Support VNF Validation project tooling requirementsClosed |
Test VNF Package Lifecycle
Section | Description |
|---|---|
ID | VNF-SDK-UC-05-01-02 |
Title | Test VNF Package Lifecycle |
Description | In this Use Case, the Marketplace Operator tests the end-to-end lifecycle of the VNF package. |
Primary Actor | Marketplace Operator |
Preconditions | |
Main Success Scenario | |
Alternate Scenarios | |
Exception Scenarios | |
Post Conditions | The VNF Package passed the lifecycle testing. |
JIRA Traceability | VNFSDK-28: Align VNF validation tools with new VNF packaging modelClosed |
Test VNF Package Function
Section | Description |
|---|---|
ID | VNF-SDK-UC-05-01-03 |
Title | Test VNF Package Function |
Description | In this Use Case, the Marketplace Operator tests the network function of the VNF package. |
Primary Actor | Marketplace Operator |
Preconditions | |
Main Success Scenario | |
Alternate Scenarios | |
Exception Scenarios | |
Post Conditions | The VNF Package passed the function testing. |
JIRA Traceability | VNFSDK-28: Align VNF validation tools with new VNF packaging modelClosed |
Download New VNF Package
Section | Description |
|---|---|
ID | VNF-SDK-UC-06 |
Title | Download New VNF Package |
Description | In this Use Case, the Service Provider searches, finds and downloads a VNF package that meets their network service needs. |
Primary Actor | Service Provider |
Preconditions | |
Main Success Scenario | |
Alternate Scenarios | |
Exception Scenarios | |
Post Conditions | VNF SDK package successfully downloaded by Service Provider |
JIRA Traceability |
Receive Update Alerts (Deferred)
Section | Description |
|---|---|
ID | VNF-SDK-UC-07 |
Title | Receive Update Alerts |
Description | |
Primary Actor | Service Provider |
Preconditions | |
Main Success Scenario | |
Alternate Scenarios | |
Exception Scenarios | |
Post Conditions | |
JIRA Traceability | VNFSDK-42: Supporting notifications for VNF package updatesClosed |
Download Updated VNF Package (Deferred)
Section | Description |
|---|---|
ID | VNF-SDK-UC-08 |
Title | Download Updated VNF Package |
Description | |
Primary Actor | Service Provider |
Preconditions | |
Main Success Scenario | |
Alternate Scenarios | |
Exception Scenarios | |
Post Conditions | |
JIRA Traceability |
Use Case Personas
This section describes the Use Case personas or UML Actors.
VNF Supplier
The VNF Supplier has responsibility for designing, defining and developing a VNF package which Service Provider has a need for.
Marketplace Operator
The Marketplace Operator has responsibility for managing and controlling the marketplace environment, including managing users and VNF content placed in the marketplace.
Service Provider
The Service Provider is the consumer of the VNF packages in the marketplace. A particular VNF is downloaded to meet a business need the Service Provider has.