NIH | National Cancer Institute | NCI Wiki  

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

Version 1 Next »

Create form module

Use Case Number

Init8pm25.pm24.1

Brief Description

A form module is a reusable section of a form that contains one or more questions/CDEs.  These can be created from a set of existing questions or from scratch.

Actor(s) for this particular use case

Forms Curator

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

None.

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

A form module is created.

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. A Forms Curator creates a new form module from scratch.
  2. The Forms Curator updates the form module metadata, including its name, visibility, etc.
  3. The Forms Curator associates a number of CDE questions to the form module.
  4. The Forms Curator saves the form module.
  5. The Forms Curator optionally selects forms in which to include the form module.

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

The Forms Curator could select a number of existing CDEs (whether on a form or not) for which to create a form module.  This essentially combines steps #1 and #3 and possibly #5 above.

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.

None.

Fit criterion/Acceptance Criterion 
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?

None.

Copy form module

Use Case Number

Init8pm25.pm24.2

Brief Description

 

Actor(s) for this particular use case

Forms Curator

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

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.

None.

Fit criterion/Acceptance Criterion 
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement? 

None.

Update form module

Use Case Number

Init8pm25.pm24.3

Brief Description

 

Actor(s) for this particular use case

Forms Curator

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

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.

None.

Fit criterion/Acceptance Criterion 
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?

None.

Update form module copy

Use Case Number

Init8pm25.pm24.4

Brief Description

 

Actor(s) for this particular use case

Forms Curator

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

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.

None.

Fit criterion/Acceptance Criterion 
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?

None.

Retire form module

Use Case Number

Init8pm25.pm24.5

Brief Description

 

Actor(s) for this particular use case

Forms Curator

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

Medium.

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.

None.

Fit criterion/Acceptance Criterion 
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?

None.

  • No labels