NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 33

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

INIT1SD13.pm23.3

Brief Description

Legacy datasets and existing services have a rich set of data that has not been indexed and is not accessible to natural language searching.  It is desirable that users are able to use common tooling to index these datasets using domain ontologies and make them available for searching and discovery.

Actor(s) for this particular use case

Software Engineer

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

A legacy dataset or existing service exists.

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

The dataset or service is indexed and available.

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 identifies the legacy dataset or existing service to index.
  2. The Software Engineer identifies the ontologies to use to index
  3. The Software Engineer sets up the parameters for indexing
  4. The Software Engineer performs the indexing
  5. The Software Engineer exposes the index as a searchable and discoverable service

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

The Software Engineer sets up a strategy for index maintenance.

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