|
Difference between
current version
and
current version:
| At line 0 added 34 lines. |
| + !!! Use Case: ''Select Naming System'' |
| + |
| + !! Actors |
| + ; Primary Actor : |
| + |
| + !! Description |
| + When querying SEEK the user may prefer to have results returned acording to a particular naming scheme offered by the provider, e.g. common names rather than full scientific name. The SEEK system must allow the user to be able to specify this and ensure providers can respond to the request accordingly. |
| + |
| + !! Flow of Events |
| + |
| + ! Pre-conditions |
| + * Data providers must have different naming schemes if functionality to be supported through SEEK |
| + |
| + ! Basic Flow |
| + # User optionally restrict the authority with which they wish to work |
| + # |
| + ! Post-conditions |
| + |
| + None |
| + |
| + ! Alternative Flows |
| + * |
| + |
| + !! Further Details |
| + |
| + ! Non-functional Requirements |
| + None |
| + |
| + ! Issues |
| + Does SEEK have a default naming scheme for returning all results? - I suggest it does. What different naming schemes will we allow? Do these have to be pre-defined or can each data provider supply their own naming schemes? - suggest pre-defined (but extensible) not at discretion of provider. |
| + What happens if the result list does not have a name for a particular concept under the scheme chosen by the user?- suggest default naming scheme is used - implication that each data provider must have a name for each concept in the default naming scheme. or user must be notified that it is a partial result. |
| + |
| + !! History |
| + ; 30 Jan 2003 : (group) Entry created at meeting |
Back to Select Naming System,
or to the Page History.
|
