Table of Contents
| Table of Contents |
|---|
Use Case Overview & Description
...
| TOPIC | DESCRIPTION | WIKI PAGE | ||||||||||
| Requirements Proposal | This is a link to the requirements proposal made on the Requirements Sub-committee | Honolulu release - functional requirements proposed list#PNFSoftwareUpgradeenhancement | ||||||||||
| Architecture S/C info | Information on the Architecture sub-committee presentation | |||||||||||
| Prior Project "Base" Wiki | Link to the "base" wiki for the Use Case, or work from a prior release. | |||||||||||
| Requirements Jira (REQ-###) Ticket | Link to the REQ Jira ticket for this use case |
| ||||||||||
| Key Use Case Leads & Contacts | USE CASE LEAD: USE KEY CONTACTS: | |||||||||||
| Meetings Register & Recordings | Link to Use Case Team meetings. |
BUSINESS DRIVER
This section describes Business Drivers needs. These business drivers are presented on the Requirements Sub-committee and should also be put into the release requirements sub-committee page.
...
Executive Summary: In Rel 6 (REQ-84) and Rel 7 (REQ-324), PNF sw upgrade requirement in ONAP has progressed covering both with/without schema updates.
...
Use Case Title | Title of the Use Case |
Actors (and System Components) | The list of Actors and System Components that participate in the Use Case |
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 |
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 |
Epic Status
Jira server ONAP JIRA columns key,summary,assignee,arch review,tsc priority,scope status,t-shirt size,m1 approval,m2 approval,m3 approval,m4 approval,rc0 approval,status maximumIssues 20 jqlQuery key = REQ-446 serverId 425b2b0a-557c-3c0c-b515-579789cceedb
REQ Status
Jira server ONAP JIRA columns key,summary,assignee,reporter,integration test plan status,integration test status,integration test time to complete,status maximumIssues 1000 jqlQuery "Epic Link" = REQ-446 and project = REQ serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Development Status
Jira server ONAP JIRA columns key,summary,type,created,updated,assignee,reporter,priority,status,resolution,subtasks,fixversions maximumIssues 100 jqlQuery "Epic Link" = REQ-446 and project != "REQ" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
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
...
| 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 |
Slides
View file name PNF update improvement RelH.pdf height 250