For R7 PNF Pre-onboarding
...
USE CASE
| PNF Preonboarding / Onboarding |
| |||||||||
| VNF SDK STORY JIRA |
| |||||||||
| Architecture Sub-committee Jira tracker |
| |||||||||
| Key Contacts | Benjamin Cheung damian.nowak |
NON FUNCTIONAL REQUIREMENT CONTRIBUTION
| Component | U/C VNFSDK Story Jira | VNFSDK NFR | Company | Description | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| VNF-SDK |
|
| Nokia | Non functional requirement contribution: (1) VNF-SDK Java 11 migration and (2) JJB update Ubuntu 18.04 See VNF Planning Jira:
| ||||||||||||||||||||||||
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 | |||||||||||
| APPC | |||||||||||
| CLAMP | |||||||||||
| CC-SDK | |||||||||||
| DCAE | |||||||||||
| DMaaP | |||||||||||
| External API | |||||||||||
| MODELING | |||||||||||
Multi-VIM / Cloud | |||||||||||
| OOF | |||||||||||
| POLICY | |||||||||||
| PORTAL | |||||||||||
| SDN-C | |||||||||||
| SDC | |||||||||||
| SO | |||||||||||
| VID | |||||||||||
| VNFRQTS | |||||||||||
| VNF-SDK | EPIC #1 Package Validation enhancements notable Package security (option 2 security on entire package) - Signatures Hashchecks per artifact (applicable for both Option 1 & 2) – in R4/R5/R6 signature Hashcheck may exist for option 1.
|
| |||||||||
| CDS |
List of PTLs:Approved Projects
*Each Requirement should be tracked by its own User Story in JIRA
...
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).
...
USE CASE FUNCTIONAL DEFINITIONS
Use Case Title |
Description
Short overview of the Use Case
Points of Contact
Authors and maintainers of the Use Case.
Use Case Lead, Key Use Case members and code contributors.
Preconditions
A list of conditions that are assumed to be true before the Use Case is invoked
Includes description of Information Consumed
PNF Pre-onboarding & Onboarding |
Actors (and System Components) |
The list of Actors and System Components that participate in the Use Case
#1 - Vendor / #2 - SDC / #3 - VNF-SDK / #4 - ONAP Components | |
Description | The base PNF pre-onboarding / onboarding use case is at this wiki: 5G - PNF Pre-Onboarding & Onboarding SOL004 specifies Package integrity/authenticity OPTION #1 open package create sign each artifacts of package & create a digest; store calculated hashes in manifest file. Calculator checksum of each artifact. OPTION #2 – same but on entire CSAR package. Sign the entire package put with signature. |
Points of Contact | |
Preconditions | The PNF Vendor package is delivered to ONAP The PNF Vendor package is described in detail in the "base" wiki page |
Triggers / Begins when | Describes the trigger for beginning the Use Case |
Steps / Flows (success) | Describes the sequence of steps and interactions that occur during the Use Case (may include: description, data exchanges, functionality, state changes) Interaction diagrams may be included or referenced |
Post-conditions | The expected results of the execution of the Use Case Includes description of Information Produced |
Alternate / Exception Paths | Description of any exceptions or special process that could occur during Use Case |
Related Use Cases | List of the Use Cases referenced by this Use Case |
Assumptions | Describes any assumptions that are made for this use case |
Tools / References / Artifacts | List of any tools or reference material associated with this Use Case as well as any JIRA trace-ability. List of any associated diagrams or modelling artifacts associated with the Use Case |
...
TESTING
Current Status
Testing Blockers
- High visibility bugs
- Other issues for testing that should be seen at a summary level
- Where possible, always include JIRA links
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 |