NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 41

changes.mady.by.user Unknown User (wileyal)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (wileyal)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Scrollbar
iconsfalse

...

Page info
title
title

Panel
titleContents of this Page
Table of Contents
minLevel2

...

Use Case Number

Otherhm2.pm13.5

Brief Description

In data collections forms, sometimes it is important to define a set of CDEs that must be asked completely in a certain order.  The question and answer pattern within the module itself has semantic meaning, and, if broken, is invalidated.  A module it sometimes combined with the non-editable flag to indicate that it cannot be altered.

Actor(s) for this particular use case

Metadata Specialist, Clinical Researcher

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

Data is collected for the modules of a form

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. The Metadata Specialist selects and defines a set of CDEs for use within a data collection form
  2. The Metadata Specialist selects a subset of CDEs to be contained within a module
  3. The Metadata Specialist deploys the form for data collection.
  4. The Clinical Researcher captures data using the form
  5. When a module is reached, all questions must be answered in the pattern described by the module
  6. If the module is not completed as specified, no values are captured for it

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

None.

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.

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

None.

...

Scrollbar
iconsfalse