3 Use cases

This chapter contains detailed use cases. These use cases are expansions of the use case presented in the requirement specification [Larsson, 2003]. First a brief overview, then use case diagrams follow.

Use cases will help developers to come to a common understanding of the system. Use cases not only represent the desired behavior, but they can also be used as the basis of test cases of system components.

The use cases also capture the functional requirements of the system. The architecture must support the functional requirements and therefore it is important to have a good understanding of what is required.

3.1 Subsystems

The use cases of Audio Jury have been divided into the following groups, each of them representing a high level subsystem.

3.1.1 Project management

This subsystem deals with the project creation, modification, status change, project running, generation, etc.

3.1.2 Test management

This subsystem's responsibilities are to create tests, edit tests, run tests, etc.

3.1.3 Result management

This subsystem performs import of results that were generated in the client while running a test, result viewing, deletion and export to a portable text format for further statistical analysis.

3.1.4 Configuration management

This subsystem's responsibility is to create, save and retrieve system configuration information.

Figure 3:  Subsystems and modules at Action Layer

3.2 Fulfilment of requirements

The following use case diagrams contain references to reqirements in the requirements specification. They explicitly state in which subsystem and module of the action layer the respective requirement will be fulfilled.

Figure 4:  Project Manager use cases and requirements

Figure 5:  Test Manager use cases and requirements

Figure 6:  Result Manager use cases and requirements

Figure 7:  Configuraion Manager use cases and requirements

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