NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 31

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

Init1pm16.6

Brief Description

ISO 21090 data types have a specific encoding scheme that is significantly different than what has been used thus far in caBIG services.  Rather than reengineering existing services entirely, it may be desirable to have a common translation service interface and implementation toolkit that can be used to "wrap" existing non-compliant services.

Actor(s) for this particular use case

Software Engineer

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

One or more services exist that expose datatypes that are not ISO 21090 compliant.

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

A new service is implemented that exposes the same semantics but with ISO 21090 datatypes.

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 Software Engineer enters a service into the toolkit for remapping
  2. The Software Engineer uses the toolkit provided to create mappings from the original datatypes to the ISO 21090 datatypes with minimal coding
  3. The Software Engineer generates the new information model automatically and registers it
  4. The Software Engineer deploys the new and (if necessary) old service

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.

Init1bes12 - Mapping_transformation support for ISO21090 data types

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

As little coding as possible should be required.

...


Scrollbar
iconsfalse