This is considered a draft. |
<give it a name>
<who wrote the use case>
<provide a description on what the use case does>
< who would benefit from this use case, how and under what scenarios >
< list the VNFs this use case will automate/impact/use, be both generic like EPC and specific in terms of software used e.g. which EPC code or vendor product>
< describe the work flows which are part of the use case. E.g. Instantiation, Deletion of VNF >
< describe any control automation that is part of the use case E.g. auto scaling, auto fault detection or recovery>
< list all projects that are impacted by this use case and identify any project which would have to be created >
< identify who is committing to work on this use case and on which part>
<Insert UML 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).
Each Use Case from the UML Use Case Diagram is defined in this section.
Section | Description |
---|---|
ID | |
Title | |
Description | |
Primary Actor | |
Preconditions | |
Main Success Scenario | |
Alternate Scenarios | |
Exception Scenarios | |
Post Conditions | |
JIRA Traceability |