NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 4

changes.mady.by.user Unknown User (deshpans)

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

Init1pm5.1 - Metadata Load Rollback

Use Case Number

Init1pm5.1

Brief Description

Once an Information Modeler registers a model in the metadata repository, there should be an easy way for the Information Modeler himself, a Metadata Curator, or a Metadata Administrator to easily remove all information associated with the registered model.  In the database domain, this is typically termed a "rollback", and no remnants except the fact that a rollback occurred should be left in the metadata repository.

Actor(s) for this particular use case

  • Information Modeler
  • Metadata Curator
  • Metadata Administrator

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

A model has been registered in the metadata repository
 

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

The model in its entirety is removed from the metadata registry.

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. An Information Modeler, Metadata Curator, or Metadata Administrator enters the model "rollback" administration interface.
  2. The user selects the model to remove
  3. The user is warned that this is an irreversible process
  4. The user confirms the rollback

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.

Init1pm5 - Data rollback functionality

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

  • The process should be quick (hours or less)
  • The process should be simple
  • The process should not effect other users of the metadata repository


Scrollbar
iconsfalse