NIH | National Cancer Institute | NCI Wiki  

WIKI MAINTENANCE NOTICE

Please be advised that NCI Wiki will be undergoing maintenance on Thursday, May 23rd between 1200 ET and 1300 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.

Versions Compared

Old Version 36

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

Anchor
ContentsofthisPage
ContentsofthisPage
Panel
titleContents of this Page
Table of Contents
minLevel2

...

Use Case Number

Init1bes8.pm30.U0

Brief Description

Currently CDEs are bound to an object class which hinders reuse for developers. Although this supports domain information modeling, where classes actually represent real life entities, it does not support non-domain information modeling (e.g. summary classes, report classes that combine many attributes from different domain classes). Supporting such non-domain modeling practices and removing object class/DE dependency will be needed.

Actor(s) for this particular use case

Metadata Specialist

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

Several CDEs of interest exist in the metadata repository.

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

A new object class is registered and mapped to multiple existing CDEs.

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 creates a new class
  2. The Metadata Specialist discovers existing common data elements to reuse in this class
  3. The Metadata Specialist selects more than one common data element to map to the new object class as reused
  4. The Metadata Specialist registers the new object class, which reuses multiple common data elements.

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

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?

The newly formed object class must be marked and discoverable as reusing each of the common data elements.

...


Scrollbar
iconsfalse