/
Use Case Definition
Use Case Definition
- Brian Hedstrom
Owned by 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. |