 |
Page History
| Scrollbar | ||
|---|---|---|
|
| Page info | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Panel | ||||
|---|---|---|---|---|
| ||||
|
Creating Statistical Computing Environment in a caGrid framework
Use Case Number | SMDSD1 |
|---|---|
Brief Description | This use case captures the requirements for creating a Statistical Computing Environment in a caGrid framework. |
Actor(s) for this particular use case | System Architect |
Pre-condition | None |
Post condition | User should be able to use the statistical computing environment thus created for running the analytical services. |
Steps to take |
|
Alternate Flow | None |
Priority | High |
Associated Links | — |
Fit criterion/Acceptance Criterion | This is a non-functional requirement and therefore the creation of such an environment would be the acceptance criteria. |
Creating sharable metadata
Use Case Number | SMDSD2 |
|---|---|
Brief Description | This use case describes creation of sharable metadata for analytical services |
Actor(s) for this particular use case | Study manager |
Pre-condition | There is a set of agreed upon standards which can be used as benchmark standards for data exchange |
Post condition | A widely accepted and lowest common minimum metadata is created |
Steps to take |
|
Alternate Flow | None |
Priority | High |
Associated Links | — |
Fit criterion/Acceptance Criterion | Metatdata for analytical services is available. |
Use Case - Descriptive Name
Use Case Number | n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition |
|
Steps to take | 1. |
Alternate Flow |
|
Priority |
|
Associated Links |
|
Fit criterion/Acceptance Criterion | 1. |
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?
...
| Scrollbar | ||
|---|---|---|
|
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?
...
