2 System overview and data flow

2.1 Introduction

This chapter deals with the data flows within the AudioJury system. While this may seem a little too detailed for a system overview chapter there are good reasons to have it right here:

Firstly, overviews have already been given in both the requirements specification [Larsson, 2003] and the architecture document [Johansson, 2003]. Secondly, interesting output from the AudioJury system will only be produced when data has made a round trip from the administrator program to the client program and back again. This chapter doesthat journey.

2.2 Distribution of project

When a project has been created it must be distributed to the clients so the test participants can run it.

2.2.1 Manual distribution

This method is not recommended, but is designed for since it is a requirement that the system should work even without a network connection being available.

Here are the steps that the administrator must take to bring a project from the administrator program to the client program:

1. Copy the directory containing the project to removable media.

2. Bring the removable media to the client computer.

3. Copy the project directory from the removable media into the installation directory of the client program.

For information on directory structure see chapter 6, "Directory structure".

Note: The copying is made using operating system commands or interfaces. Other third party software such as CD-burning software might have to be used if CD:s are used as removable media.

2.2.2 Networked distribution

This method of distribution is recommended since it will provide most convenience for the administrator.

In this method, the administrator program will copy a project to the shared folder when the project gets activated. The client program will then, if configured correctly, fetch the projects from the shared folder before running them. Projects can be fetched upon program startup or when requested. It is a good idea to cache fetched projects locally since a project may be in the order of 100 - 200 MB in size.

For further details see:

· chapter 6, "Directory structure".

· section 5.3.1, "Activate project".

· section 9.1, "AudioJuryAdministrator configuration file".

2.3 Result collection

When results have been produced after running a project they must somehow find their way back to the administrator program.

2.3.1 Manual collection

In manual collection the administrator has to perform the following steps for each client computer in order to bring the results to the administrator program:

1. Copy the contents of the local result folder to removable media.

2. Take the removable media to the computer running the administrator program.

3. Perform manual import using the interface in the project manager view in the administrator program.

For further details see:

· section 6.3, "AudioJury directory (Client)".

· user interface section of the architecture document [Johansson, 2003].

2.3.2 Networked collection

Here is a description how and when the client program submits results:

1. If it is not possible to write to the shared folder the result is written to the local result directory.

2. Additionally, at each startup the client program checks if the shared folder is available. If it is, all results in the local result folder are moved to the shared folder.

For further details see:

· section 4.5, "Name of result file".

· section 6.3, "AudioJury directory (Client)".

· section 6.4, "Shared folder directory".

· section 7.4, "Duplicate results".

· section 9.3, "AudioJuryClient configuration file".

The administrator program also has to perform some actions for the networked collection of results to be complete. Here is a description of what the administrator program shall do:

1. If the shared folder is available, each result file inside it is examined and then moved to the local result folder of the corresponding project.

2. Action 1 can be performed upon administration program startup, by user input or both.

For further details see:

· section 4.5, "Name of result file".

· section 6.4, "Shared folder directory".

· section 7.4, "Duplicate results".

· section 9.2, "AudioJury Administrator configuration file".

· section 9.7, "Result file".

2.4 Recommended setup

For most convenience when using the AudioJury system, it is recommended to use the network distribution and result collection methods. For them to work, there are a number of prerequisites that need to be fulfilled:

1. A so called "shared folder" must be available somewhere on the network. See section 1.8, "Glossary".

2. The shared folder must allow write access. See Microsoft Windows documentation.

3. Both the administrator and client program must be configured to use the mentioned shared folder.

For further details see:

· section 9.2, "AudioJury Administrator configuration file".

· section 9.3, "AudioJuryClient configuration file".

· section 7.8, "Multiple administrator programs".

Quadralay Corporation http://www.webworks.com Voice: (512) 719-3399 Fax: (512) 719-3606 sales@webworks.com