![]() |
Page History
...
Use
...
Case
...
-
...
Descriptive
...
Name
...
Use |
...
Case |
...
Number |
...
|
...
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 | 1. Their exists a mapping between LexGrid and RDF in the form of LexRDF |
Post condition | Developer gets the entire information associated with the data element if it is available in LexRDF in triple constructs |
Steps to take | User queries using LexEVS API |
Alternate Flow | A corresponding mapping does not exist between Lexgrid and RDF |
Priority | Medium |
Associated Links |
|
Fit criterion/Acceptance Criterion | Actor can look up data using a semantic search rather than a keyword search. |
Use Case - Descriptive Name
Use Case Number | n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition |
|
Steps to take | 1. |
Alternate Flow |
|
Priority |
|
Associated Links |
|
Fit criterion/Acceptance Criterion |
|
Use Case - Descriptive Name
Use Case Number | n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition |
|
Steps to take | 1. |
Alternate Flow |
|
Priority |
|
Associated Links |
|
Fit criterion/Acceptance Criterion | 1. |
Use Case - Descriptive Name
Use Case Number | n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition |
|
Steps to take | 1. |
Alternate Flow |
|
Priority |
|
Associated Links |
|
Fit criterion/Acceptance Criterion |
|
Use Case - Descriptive Name
Use Case Number | n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition |
|
Steps to take | 1. |
Alternate Flow |
|
Priority |
|
Associated Links |
|
Fit criterion/Acceptance Criterion |
|