Page History

Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

FMRSD2

Brief Description

This use case describes the registeration of metadata on federated metadata registry

Actor(s) for this particular use case

Curator

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

Fully annotated metadata has been created

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

User is able to view the data that he has registered on 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. Actor creates the metadata
2. Invokes the metadata registry service
3. Metadata is registered on the local repository

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.

User is able to view the data that he has registered on the repositoryThe local repository should expose a common API to allow federation

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

1. User is able to view the data that he has registered on the repository
2. The local repository should expose a common API to allow federation