NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 27

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

Init1pm1.2

Brief Description

The modeling tool and metadata registry should facilitate easy reuse of existing metadata.  Specifically, this includes sophisticated/seamless type-ahead functionality for finding common data elements and semantic concepts, the metadata repository should support the notion of common data elements that overlap between system and provide touch-points for interoperability, the registration process should be linked directly with the modeling tool, and Information Modelers should have the ability to perform metadata loads into a "sandbox" metadata repository on their own.

Actor(s) for this particular use case

Information Modeler

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 model has been created, semantic metadata has been added, and it has been registered in the metadata repository.

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 Information Modeler creates a model in the modeling tool
  2. The Information Modeler is able to search for specific common data elements and semantic concepts directly from the modeling tool using type-ahead functionality (or an equivalently user friendly technology)
  3. The Information Modeler is able to search for common data elements that have been identified as key touchpoints for other systems to "link" with or "interoperate" on
  4. Whenever the Information Modeler feels it is helpful, he should be able to load the model into a sandbox environment through functionality built into the modeling tool

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.

Init1pm1 - ICR IRWG Requirements

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

  • As many of the described steps and as much of the functionality as possible should be built into the modeling tool

...


Scrollbar
iconsfalse