|
|
 |
 |
|||
 | ||||||
|
|
|
|
|
|||
|
| ||||||
 | Sub-flows are useful for re-using a common flow or as outcomes of a case statement |
| If the sub-flow is common between two use cases, or very large, then it may be splt out into a seperate use case document and shown as a seperate use case symbol on the diagram with and 'include' relationship showing its use. |
| An alternate flow is a conditional flow that knows how to insert itself in the original flow. |
| If the alternate flow is very large, or optional functionality, then it may be moved to a seperate use case document and shown on the diagram as a seperate use case symbol with an 'extend' relationship to the use case it extends. |
| An activity diagram can be created to show the overall flow of the use case but should not replace the use case text. |
| A prototype screen is a useful second user-facing view of a use case and should be consistent with the use case text. |
| A use case document template is useful to ensure consistency of use case text standards across a project. |
 |
|