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.

Initpm7.SD200

Brief Description

This use case describes the automated loading process of UML metadata on caDSR sandbox

Actor(s) for this particular use case

Developers

Pre-condition
The state of the system before the user interacts with it

The developers are ready with the UML model and an annotated xmi

A BPM tool is configured to understand and perform the steps involved in registering metadata in sandbox
developers have access to BPM tool

Post condition
The state of the system after the user interacts with it

The metadata is available on sandbox environment on caDSR

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. Developers complete the modelling of a tool
2. log in to the BPM and submit the XMI
3. The model is successfully loaded on caDSR in sandbox environment
4. Automated emails are sent to the developers to verify model on Sandbox

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

High

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?

Uploading metadata on caDSR is automated without needing a human intervention
 
 

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.

Init1PM7.SD200.2

Brief Description

This use case describes the automated curation of  metadata on caDSR

Actor(s) for this particular use case

Developers

Pre-condition
The state of the system before the user interacts with it

The model creators have approved the model
A BPM tool is configured to understand and perform the steps involved in curating metadata
developers have access to BPM tool 

Post condition
The state of the system after the user interacts with it

The metadata is Curated on caDSR

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. Developer vets the model on sandbox
2. Okays the metadata for curation
3. Metadata is curated
4.Automated mails triggered to developers

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

High

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? 

Metadata curation is automated on cadSR

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.

Init1pm7.SD200.3

Brief Description

This use case describes the automated loading process of UML metadata on caDSR production

Actor(s) for this particular use case

Developers

Pre-condition
The state of the system before the user interacts with it

Metadata has been curated on caDSR
The model has passed compatibility check
A BPM tool is configured to understand and perform the steps involved in registering metadata in production

Developers have access to BPM tool 

Post condition
The state of the system after the user interacts with it

Metadata available on caDSR production

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.Developers request moving model to production
2. log in to the BPM and submit the XMI
3. The model is successfully loaded on caDSR in production environment
4. Automated emails are sent to the developers and other stakeholder

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

High

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?

Uploading on caDSR is automated

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?

1.
2...

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?

1.
2...