Changeset 14

Show
Ignore:
Timestamp:
01/16/08 16:54:20
Author:
graybeal
Message:

Reformatted and edited for clarity.

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • docs/trunk/usecases/DO_UseCase01

    r11 r14  
    1 Use Case 1: Discover and plot data from common sensor types via SOS Services 
     1Use Case 1: Discover and plot data from common sensor types automatically 
     2  -> e.g., via SOS Services 
    23 
    341.      Portal presents a category "CTD" for a user to get data from a CTD sensor 
    …… 
    12137.      Portal knows how to plot CTD data and presents a preview to the user 
    1314 
    14 CTD could be replaced by vertical profiler or any other type of sensor. 
     15The term 'CTD' could be replaced by vertical profiler or any other type of sensor. 

  • docs/trunk/usecases/DO_UseCase02

    r12 r14  
    11Use Case 2: Classify devices according to functionality. 
    22 
    3 1.     User begins entering a device record into a data base.  
     31.  User begins entering a device record into a data base.  
    44    (Could also be creating a device metadata record, e.g., in XML). 
    5 2.     User is prompted to enter the functional capability of the device.  
     52.  User is prompted to enter the functional capability of the device.  
    66    (Selects from drop down list or controlled vocabulary.) 
    7 3.     Auxiliary functional capabilities are solicited. (Any number may be entered.) 
     73.  Auxiliary functional capabilities are solicited. (Any number may be entered.) 

  • docs/trunk/usecases/DO_UseCase03

    r12 r14  
    1 Use Case 3: Find out devices that can be deployed from given platform. 
     1Use Case 3: Find devices that can be deployed from a given platform. 
    22 
    3 This use case involves searching for devices that can be deployed from a given platform, for example a ship. It is one that would be performed by system operators, and asks where a device is capable of being deployed (e.g., what medium? what platform? tethered or not?). 
     3This use case involves searching for devices that can be deployed from a given platform, for example a ship. It is one that would be performed by system operators, and asks where a device is capable of being deployed.  (Other criteria besides platform include  medium in which the device is deployed, and whether the device is tethered or not.) 

  • docs/trunk/usecases/DO_UseCase04

    r12 r14  
    1 Use Case 4: Find devices that can produce certain output variables (or provide all the information necessary to produce those output variables?). 
     1Use Case 4: Find devices that can produce certain output variables  
     2  -> or provide all the information necessary to produce those output variables? 
    23 
    34(This may not be different than Use Case 1.)  
    …… 
    56Salinity might be a direct output variable for some CTD devices, and a post-processed variable for data from other CTD devices. See for example email from J Zedlitz [http://mmi.mbari.org/pipermail/ontdev/2007/000013.html]. The mechanism by which the device produces the outputs -- direct measurement or measurement plus calculation -- is not relevant to this use case. 
    67 
    7 For more detail on the concept of output variables, you can visit the device variables page [http://marinemetadata.org/examples/mmihostedwork/ontologieswork/observableont/ontdevices/ontdevices/devicedata]. 
     8For more detail on the concept of output variables, visit the device variables page [http://marinemetadata.org/examples/mmihostedwork/ontologieswork/observableont/ontdevices/ontdevices/devicedata]. 

  • docs/trunk/usecases/DO_UseCase08

    r12 r14  
    11Use Case 8: Find all sensors that perform a particular measurement. 
    22 
    3 This use case focuses not on the devices, but on the sensors contained within them. 
     3This use case focuses not on the devices, but on the sensors contained within them. Otherwise it is identical to Use Cases 4/5. 

  • docs/trunk/usecases/DO_UseCase09

    r12 r14  
    11Use Case 9: Find devices that can obtain certain physical samples. 
    22 
    3 The workflow is essentially similar to the first workflow given under Use Case 5, except that the scientist's target is samples for subsequent analyis rather than in-situ measurements. A mechanism is needed for adequately describing samples. For example, is it sufficient to use 'sediment sample' or do we need additional attributes such as 'sediment sample with undisturbed sediment/water interface? 
     3The workflow is essentially similar to the first workflow given under Use Case 5, except that the scientist's target is samples for subsequent analyis rather than in-situ measurements.  
     4 
     5A mechanism is needed for adequately describing samples. For example, is it sufficient to use 'sediment sample' or do we need additional attributes such as 'sediment sample with undisturbed sediment/water interface? 

  • docs/trunk/usecases/DO_UseCase10

    r12 r14  
    1 Use Case 10: Find all the devices that have a certain characteristic or meet certain criteria. 
     1Use Case 10: Find all the devices that meet certain criteria. 
    22 
    3 Use Case 3 above is an example of this type of scenario. Others follow. 
     3Use Case 3 is one example of this type of scenario. Others follow. 
    44 
    55Use Case 10A: Find all the devices that can operate at all depths from 50 meters to 3000 meters. 
    6 Presumably to be combined with other criteria, this enables users to find devices that can be deployed on platforms at those depths. To respond the operational depth limits of each device would have to be provided in the device description. 
     6 
     7Presumably to be combined with other criteria, this enables users to find devices that can be deployed on platforms at those depths. To respond to this query, the operational depth limits of each device would have to be provided in the device description.