Initpm7.SD200.1

This use case describes the automated loading process of UML metadata on caDSR sandboxreview of XMI submitted by developers using Business Process Management (BPM) tool

Developers

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 metadata creation, submission, storage, review, and acceptance
Developers have access to BPM tool
The BPM tool has the necessary interface with SIW

Automated emails are generated informing the stakeholders of the result from SIW run The metadata is available on sandbox environment on caDSR

1. Developers complete the modelling of a tool have the complete submission package
2. log in to the BPM and submit the XMI
3. The model is successfully loaded on caDSR in sandbox environmentBPM invokes the SIW to validate the xmi
4. Automated emails are sent to the developers to verify model on Sandbox the stakeholders informing them of the result of SIW run.

None  

High

SIW run for a given XMI is automated

Init1PM7 Init1pm7.SD200.23

This use case describes the automated curation of  metadata on caDSR upload of model submitted by developers using BPM to caDSR sandbox

Developers

1) The model creators developers have approved the model XMI after recieving it from the EVS team
2) A BPM tool is configured to understand and perform the steps involved in metadata creation, submission, storage, review, and acceptance
3) Developers have access to BPM tool

The metadata is Curated Metadata available on caDSR Sandbox

1. Developer vets the model on sandbox
2. Okays the metadata for curation
3. Metadata is curated
4.Automated mails triggered to developers Developers log in to the BPM and submit the XMI
2.The model is successfully loaded on caDSR in sandbox environment
3.Automated emails are sent to the stakeholder

  None

High

Metadata curation Uploading on caDSR is automated on cadSR

Init1pm7.SD200.34

This use case describes automated upload process to caDSR production  

  none

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...

1) The Model owners have reviewed and approved the metadata on caDSR sandbox

2) A BPM tool is configured to understand and perform the steps involved in metadata creation, submission, storage, review, and acceptance

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

Metadata is available on Production  

1.
2.
The BPM tool understands that model owners have approved model on caDSR sandbox and uploads it to production

  None

  High

1.
2...

upload to caDSR is automated