NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Old Version 19

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

Saved on

compared with

New Version 20

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
Wiki Markup
{scrollbar:icons=false}

Page info
title
title

Anchor
ContentsofthisPage
ContentsofthisPage
Panel
titleContents of this Page
Table of Contents
minLevel2

Use Case - Triple store backend for LexEVS

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.

Init4hm1.SD210

Brief Description

This Use case describes the functional usage of mapped LexRDF in a semantic web scenario

Actor(s) for this particular use case

Application developers

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

1.      Their exists a mapping between LexGrid and RDF in the form of LexRDF
2.      The LexEVS API can query using SPARQL

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

Developer gets the entire information associated with the data element if it is available in LexRDF in triple constructs

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

User queries using LexEVS API

User is directed to LexRDF via a direct mapping that exists between LexGrid and RDF

User gets a complete hierarchical and structured information on the data element of interest
 

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

A corresponding mapping does not exist between Lexgrid and RDF

Priority
The priority of implementing the use case: High, Medium or Low

Medium

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?

Actor can look up data using a semantic search rather than a keyword search.


Wiki Markup
{scrollbar:icons=false}