NIH | National Cancer Institute | NCI Wiki  

WIKI MAINTENANCE NOTICE

Please be advised that NCI Wiki will be will be undergoing maintenance on Monday, June 24th between 1000 ET and 1100 ET.
Wiki will remain available, but users may experience screen refreshes or HTTP 502 errors during the maintenance period. If you encounter these errors, wait 1-2 minutes, then refresh your page.

If you have any questions or concerns, please contact the CBIIT Atlassian Management Team.

Error rendering macro 'rw-search'

null

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

Compare with Current View Page History

« Previous Version 47 Next »

This page is a draft template, To use the template, on the wiki page where you want to start, click Add Page to create a "child page." Then click the link to apply a template and select the Semantic Infrastructure Con Ops Use Case template.

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 Narrative/Description (a description of the actor, the business objective or goal, and the main success scenario)

---

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 Narrative/Description (a description of the actor, the business objective or goal, and the main success scenario)

---

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 Narrative/Description (a description of the actor, the business objective or goal, and the main success scenario)

---

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 Narrative/Description (a description of the actor, the business objective or goal, and the main success scenario)

---

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