Overview of Design
Composite Design 3 This is a web application designed with safety in mind design that focuses on safety while striving for reasonable efficiency. Such a design should assist more error-prone users who might be less computer-savvy while still remaining efficient enough for high-volume music directors to get their job done without much fuss. Unlike other designs, this design has been designed without a focus on playback, instead focusing on the editing and uploading portions of the task, since these are common tasks for both music directors and elves. The
- Motivation: This design focuses on the most critical task of the three identified in GR1 (importing music). The CMJ lists, which are used less often (submitted on the order of once a week) are not a major focus of the design, but may be accessed through a tab interface at the top.
- Design Idea: This design keeps editing separate from uploading by fusing a master-detail design like those used on iPad applications with the pane-based design of Windows 8 applications for the purpose of selecting editable components in a modal interface ("Metro"-style)
- Scope: Since importing and reporting are the most important tasks of a music director, these tasks have been emphasized for the purposes of this interface.
- *Pro: *By emphasizing safety, more error-prone users who might be less computer-savvy will be able to be sure that they will not import data with incorrect data. The compromise in using a master-detail design should add efficiency for high-volume music directors to get their job done without much fuss.
- Con: Aspects of the interface (including the questions asked and modal nature of most of the detail view) may be less efficient than would be ideal for high-volume music directors.
An overview of the entire interface is shown here, details regarding each component will be explained in the storyboard below.
|
|
A detailed example of the main KaJaM! interface | The KaJaM! interface when editing an album |
...