Changeset 18
- Timestamp:
- 01/16/08 16:56:55
- Files:
-
- docs/trunk/usecases/DO_UseCase05 (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
docs/trunk/usecases/DO_UseCase05
r12 r18 1 1 Use Case 5: Find devices associated with certain real-world properties. 2 2 3 In this use case the use wants to measure a given environmental property, for example conductivity, or know what instruments are capable of doing so. In this case the important concept is not what variables are ultimately produce, but what measurements are directly sensed. Note the relationship (but not equivalence) to Use Case 8. 3 The user wants to know what instruments can measure a given environmental property, for example conductivity (for example, to obtain an instrument to perform the measurement, or to analyze those instruments for some other purpose). 4 4 5 This use case may have more than one potential user. The obvious user is a scientist with a budget but no equipment pool wanting to study a particular phenomenon who would like better access to instrument catalogues than typing the phenomenon name into Google. The workflow in this case is simply: 6 1. User enters phenomena of interest into search engine 7 2. Search engine returns a list of instruments associated with that phenomenon, including links to manufacturer's on-line catalogue 5 In this case the important concept is not what variables are ultimately produced, but what measurements are directly sensed. That is the primary distinction from Use Case 4. 8 6 9 However, another user is the developer of tools to support metadata creation from data that are (or at least should be) labelled with the parameters: 10 1. Parameter labels may be transformed into a set of observed phenomena 11 2. Observed phenomena transformed to a list of instruments 12 3. Instruments transformed into categories using ontology classification 13 4. Instrument categories used to populate discovery metadata fields 7 Note the relationship (but not equivalence) to Use Case 8, which focuses on the sensors rather than the device as a unit. 8 9 There is another use case, Use Case 12, which is almost the inverse of this use case. It involves using the variable terms to produce higher-level documentation of an instrument. 10 11 A scientist wants to buy equipment to study a particular phenomenon, and wants to find ALL the instruments that are capable of studying that phenomenon (not just those discoverable through manual or on-line searches through catalogs, or through Google entry of a keyword). 12 13 The workflow is: 14 1. User enters phenomena of interest into search tool. 15 2. Search tool returns a list of instruments associated with that phenomenon, including links to manufacturer's on-line catalogue.
