NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 7

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

Init1pm10.pm20

Brief Description

The metadata/semantic tools in caBIG provide a rich set of functionality that may be useful to Information Technologists (especially Software Engineers) in a programmatic/service manner.  The tools themselves would need to be refactored to expose the underlying functionality as services so that an application engineer could invoke the services to perform add, change or delete content in the metadata registry, or retrieve content to use the metadata in their user interface.  In this scenario, the same business rules that are applied in the manual curation of content would need to be in the services.  Examples also include new services to perform Value Domain matching, CDE and/or UML oriented searches that easily bring back associated components

Actor(s) for this particular use case

Software Engineer

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

The metadata tooling has been exposed as a service.

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

The metadata tooling functionality has been invoked.

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 discovers the semantic tooling functionality that he wishes to utilize via a service
  2. The Software Engineer invokes the service, passing in the appropriate data
  3. The Software Engineer gets the results

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?

None.

...


Scrollbar
iconsfalse