Page History
...
Use
...
Case
...
-
...
Descriptive
...
Name
...
Use |
...
Case |
...
Number |
...
|
...
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. |
...
Initpm7.SD200.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.2-Automate caDSR model submission
Use Case Number | Init1PM7.SD200.2 |
Brief Description | This use case describes the automated review of xmi submitted by developers using BPM |
Actor(s) for this particular use case | Developers |
Pre-condition | 1) The EVS team has approved the concept mappings in the XMI |
Post condition | Automated emails are generated informing the stakeholders of the result from SIW run. |
Steps to take | 1) Developers receive a mail from EVS team for successful review of concept mappings |
Alternate Flow | none |
Priority | High |
Associated Links |
|
Fit criterion/Acceptance Criterion |
|
Init1pm7.SD200.3-Automate caDSR model submission
Use Case Number | Init1pm7.SD200.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 | 1) The developers have approved the XMI after recieving it from the EVS team |
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 | Uploading on caDSR is automated |
Init1pm7.SD200.4-Automate caDSR model submission
Use Case Number | Init1pm7.SD200.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. The BPM tool understands that model owners have approved model on caDSR sandbox and uploads it to production |
Alternate Flow | None |
Priority | High |
Associated Links |
|
Fit criterion/Acceptance Criterion |
|
Use Case - Descriptive Name
Use Case Number | n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition |
|
Steps to take | 1. |
Alternate Flow |
|
Priority |
|
Associated Links |
|
Fit criterion/Acceptance Criterion |
|