Use Cases
Following use cases are available:
| Code: | 101 |
| Summary: |
A user creates a new experiment consisting of different types of data. |
| Actors: |
User |
| Preconditions: |
|
| Basic sequence: |
User selects the action from the menu and selects the data
files that are included in the experiment. A new experiment is initialised. |
| Exceptions: |
|
| Post conditions: |
User can either choose to save the new experiment, create
synchronisation information for it or discard it. |
| See test case(s): |
t001 |
| Code: | 102 |
| Summary: | User loads an existing experiment dataset. |
| Actors: | User |
| Preconditions: | An experiment data set exists. |
| Basic sequence: | User selects the action from the menu. He then selects the
experiment datafile from a file selector window. All data items are shown to
the user in the basic view, i.e. the timeline view. |
| Exceptions: | Experiment file is corrupted. Insufficient disk space for untarring
the experiment data set. |
| Post conditions: | User has all data items displayed, and he can start reviewing
them simply by pressing the start button from the timeline window. |
| See test case(s): |
t002 |
| Code: | 103 |
| Summary: | User saves an experiment dataset |
| Actors: | User |
| Preconditions: | User has modified the experiment. |
| Basic sequence: | User selects the action from the menu. |
| Exceptions: | User doesn't have write rights to the target directory. There is
not enough disk space left on disk. |
| Post conditions: | The experiment is stored. |
| See test case(s): |
t003 |
| Code: | 104 |
| Summary: | User reviews an experiment by playing the associated data in a
synchronised manner. |
| Actors: | User |
| Preconditions: | User has opened an existing experiment. |
| Basic sequence: | User first opens an experiment. He then starts reviewing the
experiment. The timeline shows all hot spots, so that a user can easily select
a hot spot and all data that is visible is instantly moved to that point in
time. User can use the controllers provided by the timeline window to start,
stop and play the experiment. |
| Exceptions: | Computer is not fast enough to play all data items. Parts of data
have been corrupted. |
| Post conditions: | |
| See test case(s): |
t004 |
| Code: | 105 |
| Summary: | User chooses a single data item and reviews that. Every data item has
its own time slider and buttons for play, stop and pause. |
| Actors: | User |
| Preconditions: | User has opened an experiment |
| Basic sequence: | User presses button in timeline view to free data from
synchronization and uses the individual controllers which every data item has
to play and review a single data item. |
| Exceptions: | |
| Post conditions: | Data synchronisation is lost. |
| See test case(s): |
t005 |
| Code: | 106 |
| Summary: | When recording an experiment, a user creates hot spots consisting
of a time stamp and additional comments about the hotspot. |
| Actors: | User |
| Preconditions: | User has opened a new experiment. |
| Basic sequence: | User starts the hot spot recorder from a menu. Whenever he
wants to record a hot spot, he presses space. The system records the time and
opens a text box for inserting additional comments related to the hot spot. |
| Exceptions: | |
| Post conditions: | User saves the experiment. |
| See test case(s): |
t006 |
| Code: | 107 |
| Summary: | User arranges data items in the GUI. Each data item that is shown has
its own window, its size depending on the data. Every window has a time bar and
control buttons, e.g. play, stop, pause. Each window can be individually moved
around and hidden from the working area. Each window has also two buttons in
its upper right corner for quickly hiding or removing it. |
| Actors: | User |
| Preconditions: | User has opened an existing experiment. |
| Basic sequence: | User can move, hide or remove individual windows. |
| Exceptions: | |
| Post conditions: | |
| See test case(s): |
t007 |
| Code: | 108 |
| Summary: | User synchronises the data for simultaneous playing. |
| Actors: | User |
| Preconditions: | User has opened existing experiment or created a new one. |
| Basic sequence: | User selects each data item and synchronises them related to
the experiment timeline. |
| Exceptions: | |
| Post conditions: | Experiment data is synchronised. |
| See test case(s): |
t008 |
| Code: | 109 |
| Summary: | User loads previously created synchronization data. |
| Actors: | User |
| Preconditions: | Previously created synchronisation data exists and at least one
data file is out of this synchronisation. |
| Basic sequence: | User presses button in timeline view that reloads the
synchronization. |
| Exceptions: | Synchronisation data is corrupted. |
| Post conditions: | Experiment data is resynchronised. |
| See test case(s): |
t009 |
| Code: | 201 |
| Summary: | User searches through the data using different criteria based e.g. on
the experiment parameters. |
| Actors: | User |
| Preconditions: | User has opened an existing experiment. |
| Basic sequence: | User selects the action. He gives desired parameter values when
prompted. |
| Exceptions: | Parameters are not in the given range. |
| Post conditions: | User is shown data which matches his search criteria. |
| See test case(s): |
t010 |
| Code: | 202 |
| Summary: | User views recorded hot spots and modifies them. |
| Actors: | User |
| Preconditions: | User has opened an existing experiment, which has recorded
hot spots. |
| Basic sequence: | User first selects the action from the menu. He is presented
a list of recorded hot spots, and by clicking a hot spot he can see the
comments related to it. User can also change existing comments. |
| Exceptions: | |
| Post conditions: | User can see all hot spots and comments to them. |
| See test case(s): |
t011 |
| Code: | 203 |
| Summary: | User adds, modifies or deletes text comments to the project. |
| Actors: | User |
| Preconditions: | User has created a new project. |
| Basic sequence: | User first selects the action from the menu. A window is opened
with existing comments visible. User adds new comments by inserting text
into a text field and pressing enter. User can modify an existing comment by
clicking on it and modifying the text. User can delete comments by clicking on
them and pressing a delete-button. User saves the log file. |
| Exceptions: | |
| Post conditions: | User has an XML file of all the comments. |
| See test case(s): |
t012 |
| Code: | 301 |
| Summary: | User chooses another view to the data. Basic view is the timeline
view. User can also choose to review the experiment in an activity view, where
the experiment is divided into color bars marking different activities. |
| Actors: | User |
| Preconditions: | User has opened an existing experiment. |
| Basic sequence: | User selects another view from the menu. The system changes
into the other view, displaying data in a new window. In activity view user can
see different state of activies from color bars and make conclusions of
interesting parts of experiment. |
| Exceptions: | |
| Post conditions: | Data is now displayed in a new kind of window. |
| See test case(s): |
t013 |
