This description uses OSM version 2 (for full paper, see Blandford and Green 1998)
date: Feb 98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
domain constraint: |
time shown should be same as GMT |
|
affects: |
changing the minutes angle affects hours angle |
|
device constraint: |
watch can only work if it has enough energy; only a finite amount of energy can be stored |
How users use the device: Fob watches are mainly used for telling the time of day, of course. They are also used to work out elapsed time (how long has this process been going on?), time-remaining (how much longer will it go on?), time-of-completion (what will the time be when this process has continued for X minutes?), and current time in other time zones.
Domain concepts and relationships: From the above, three domain concepts need to be introduced, time-elapsed, time-remaining, and time-of-completion.
Context of usage, and related tools or devices: Because the fob watch has no alarm system, it is frequently used in conjunction with separate devices for countdown timing (e.g. egg-timers) and for reminders at set times (e.g. alarm clocks). Transferring data from one of these to another may require translation between digital and analogue time representations.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|