|
Difference between
current version
and
current version:
| At line 0 added 39 lines. |
| + !!! Use Case: ''Editor Concept Mapping Comparison'' |
| + |
| + !! Actors |
| + ; Primary Actor : An editor of concepts (or part thereof) |
| + |
| + |
| + !! Description |
| + A "(Concept, Name, Reference) author" can query the SEEK system to retrieve the relationships between concepts. |
| + |
| + When editing a concept and/or the relationships between concepts, an editor should be presented with existing mappings to assist with determination of the need for a new mapping. |
| + |
| + The intent is to make both the process of mapping easier, and to reduce the likelihood of duplicate mappings. |
| + |
| + !! Flow of Events |
| + |
| + ! Pre-conditions |
| + * User has privileges to access the SEEK taxonomy system |
| + |
| + ! Basic Flow |
| + # Editor has concept that is to be attached to a classification scheme within the SEEK taxonomy system |
| + # The editor is presented with the current mappings for the concept in question |
| + # The editor creates a new concept mapping orverifies an existing one |
| + |
| + ! Post-conditions |
| + * The system should check the validity of changes made |
| + |
| + ! Alternative Flows |
| + |
| + !! Further Details |
| + |
| + ! Non-functional Requirements |
| + None |
| + |
| + ! Issues |
| + This is likely to be a highly visual interaction within an editor environment. Must be very responsive. |
| + * Again no implication that the new concept mapping is stored in SEEK |
| + !! History |
| + ; 30 Jan 2003 : (group) Created |
| + ; 31 Jan 2003 : (Vieglais) Use case expanded to template form |
Back to Editor Mapping Comparison,
or to the Page History.
|
