NIH | National Cancer Institute | NCI Wiki  

Versions Compared

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

Init1hm2.pm6.4

Brief Description

It is often more convenient to pull back or push entire models rather than single elements at a time.  This is especially important for systems that are using models to build queries and allow for the extension of models.

Actor(s) for this particular use case

Metadata Specialist

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

The entire model is fetched from the 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 Metadata Specialist creates a model in local tooling and publishes it in its entirety to the metadata repository.
  2. The Metadata Specialist is building a query based upon a model, and the tool fetches the entire model in one service call

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

It is not necessary that a tool enter a model in its entirety in order for it to be retrieved in its entirety.

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.

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