NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

  • Created by Unknown User (deshpans), last modified on Feb 04, 2010

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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.

Init1pm6.SD100.1

Brief Description

This use case describes the Automation of process leading to uploading of metadata on caDSR production

Actor(s) for this particular use case

Model owners

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

<!-- /* Font Definitions */ @font-face

Unknown macro: {font-family}

@font-face

Unknown macro: {font-family}

/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal

Unknown macro: {mso-style-unhide}

.MsoChpDefault

Unknown macro: {mso-style-type}

.MsoPapDefault

Unknown macro: {mso-style-type}

@page Section1

Unknown macro: {size}

div.Section1

Unknown macro: {page}

-->A tool is created and configured to understand and perform the iterations and the steps involved in metadata creation, submission, storage, review and acceptance.

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

Model owner

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

Please refer to use case available at

https://wiki.nci.nih.gov/display/VCDE/Init1pm7.SD200-Automate+caDSR+model+submission\\

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.

https://wiki.nci.nih.gov/display/VCDE/Init1pm7.SD200-Automate+caDSR+model+submission

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? 


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?

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?


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?


1.
2...

  • No labels