Page History
Scrollbar | ||
---|---|---|
|
Page info | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Panel | ||||
---|---|---|---|---|
| ||||
|
Use Case - Automated review
Use Case - Descriptive Name
...
Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.
...
n.n
...
Brief Description
...
...
Actor(s) for this particular use case
...
...
Pre-condition
The state of the system before the user interacts with it
...
...
Post condition
The state of the system after the user interacts with it
...
...
Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function
...
1.
2.
..
...
Alternate Flow
Things which would prevent the normal flow of the use case
...
...
Priority
The priority of implementing the use case: High, Medium or Low
...
...
Associated Links
The brief user stories, each describing the user interacts with the system for the one function only of the use case. There would potentially be a number of user stories that make up the use case.
...
...
Fit criterion/Acceptance Criterion
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?
...
Use Case Number | n Initpm7.SD200.n 1 |
---|---|
Brief Description | This use case describes the automated review of XMI submitted by developers using Business Process Management (BPM) tool |
Actor(s) for this particular use case | Developers |
Pre-condition | The developers are ready with the UML model and an annotated xmi |
Post condition | Automated emails are generated informing the stakeholders of the result from SIW run |
Steps to take | 1. Developers have the complete submission package |
Alternate Flow | None |
Priority | High |
Associated Links |
|
Fit criterion/Acceptance Criterion |
...
SIW run for a given XMI is automated |
Init1pm7.SD200.3-Automate model upload on Sandbox
Use Case Number | n Init1pm7.SD200.n 3 |
---|---|
Brief Description | This use case describes the automated upload of model submitted by developers using BPM to caDSR sandbox |
Actor(s) for this particular use case | Developers |
Pre-condition |
|
Post condition |
|
Steps to take | 1. |
Alternate Flow |
|
Priority |
|
Associated Links |
|
Fit criterion/Acceptance Criterion | 1. |
Use Case - Descriptive Name
1) The developers have approved the XMI after recieving it from the EVS team | |
Use Case Number | n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition | Metadata available on caDSR Sandbox |
---|---|
Steps to take | 1.Developers log in to the BPM and submit the XMI |
Alternate Flow | None |
Priority | High |
Associated Links |
|
Fit criterion/Acceptance Criterion | 1.
...
Uploading on caDSR is automated |
Init1pm7.SD200.4-Automate caDSR model submission on production
Use Case Number | n Init1pm7.SD200.n 4 |
---|---|
Brief Description | This use case describes automated upload process to caDSR production |
Actor(s) for this particular use case | none |
Pre-condition | 1) The Model owners have reviewed and approved the metadata on caDSR sandbox |
Post condition | Metadata is available on Production |
Steps to take | 1. |
Alternate Flow | None |
Priority | High |
Associated Links |
|
Fit criterion/Acceptance Criterion |
|
Scrollbar | ||
---|---|---|
|