NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 5

changes.mady.by.user Unknown User (deshpans)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (wileyal)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Scrollbar
iconsfalse

Page info
title
title

Anchor
ContentsofthisPage
ContentsofthisPage
Panel
titleContents of this Page
Table of Contents
minLevel2

Use Case -

...

Automated review

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

Brief Description

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

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

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

Automated emails are generated informing the stakeholders of the result from SIW run 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 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 environment BPM 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.

Alternate Flow
Things which would prevent the normal flow of the use case

None  

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?

SIW run for a given XMI is automated Uploading metadata on caDSR is automated without needing a human intervention
 
 

Init1pm7.SD200.

...

3-Automate

...

model

...

upload on Sandbox

 

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 Init1pm7.SD200.2 3

Brief Description

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

Actor(s) for this particular use case

Developers

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

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 curating metadata
developers metadata creation, submission, storage, review, and acceptance
3) Developers have access to BPM tool  tool

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

The metadata is Curated Metadata available on caDSR Sandbox

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

Alternate Flow
Things which would prevent the normal flow of the use case

  None

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 Uploading on caDSR is automated on cadSR

Init1pm7.SD200.

...

4-Automate caDSR model submission on production

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 4

Brief Description

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

Actor(s) for this particular use case

Developers none

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

Metadata has been curated 1) The Model owners have reviewed and approved the metadata on caDSR
The model has passed compatibility check
sandbox

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

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

Metadata is available on caDSR productionProduction

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 - Descriptive Name

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

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

  None

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?


1.
2...

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?

upload to caDSR is automated


Scrollbar
iconsfalse

...