Inspirational interfaces in other contexts

Intended operation

Within this part we describe what tasks one can actually perform when using RaceClocker, and most importantly what phases of action a user has to go through to complete tasks and what the goals of users are. Use cases and flow diagrams have been used to visualize the intended operation.

As mentioned on the previous pages, we identified two main phases for the use of race clocker. Therefore, using RaceClocker and performing tasks can be seen as two different parts as its use exists within different environments. For each phase an use case has been constituted to create insights in the intended user flow, which can be found in Appendix 1. Use case 1 shows the process of the first phase, creating a race. The first use case is divided into three subcases, 1A shows the process for creating a race with individual start, 1B for mass start and 1C for wave start. Use cases 2 show the process for phase 2, time keeping during the race. Again, this case is divided into subcases. 2A demonstrates assigning start times for individual races, 2B for mass start, 2C for wave start and finally 2D demonstrates the process of timing for split and finish points. These use cases were used to create a flow diagram. The flow diagram shows in more detail in what way a user can navigate back and forth through the website (Appendix 2). A simplified version of this diagram can be found in Figure 11.

Both user types, direct and indirect users, have different goals. The goal of the first direct user, race managers, is to make sure the process of the race is smooth and the results of the race are accurate and correct. For a timekeeper, the goal is to easily assign the correct time to the correct participant. Indirect users, racers and audience, have the goal to directly see and review results of the race, during and after.

Figure 11 General overview of the three phases of organising a race