h1. 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 {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:0in; margin-right:0in; margin-bottom:10.0pt; margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:115%;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} -->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. \\
.. |
h1. 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... |
h1. 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... \\ |
h1. 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... |
h1. 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... | |