VisiChord Chord Visualizer
Design Review as of 2 April 2002

Adrian Mettler, Gabe Neer, Erika Rice, Jeff Scherpelz

Purpose

The chord visualizer will be used to display chords both on a piano keyboard diagram and in music staff notation. Chords can be input via the keyboard, mouse, from a file or via MIDI input device. Chords can be transcribed, played, edited and saved to a file via the interface.

Actions

There are a limited number of actions that the user can do. They are as follows: What each of these events actually entails is outlined in the Use Cases and sequence diagrams. Alternate actions taken when a user is trying to do one of these things incorrectly, and the actions taken when a user tries to do anything else are outlined in the Acceptance Tests.

Architecture

The overall architecture of the project can be seen in the class diagram or the simplified class diagram. The basic architecture is as follows: the user interacts with the GUI. This in turn interacts with an adaptor which decides what to do with events after they have been interpreted. The adaptor acts as a way to interact with the Document class. This class stores information about a set of chords, including the actual chords, the title of the set and the UndeleteBuffer. The chord set is then made up of chords, and chords are made up of notes. As can be seen in the class diagrams and sequence diagrams, this architecture ensures a very definite flow of action during the course of any event.

About this document ...

VisiChord Chord Visualizer
Design Review as of 2 April 2002

This document was generated using the LaTeX2HTML translator Version 2K.1beta (1.48)

Copyright © 1993, 1994, 1995, 1996, Nikos Drakos, Computer Based Learning Unit, University of Leeds.
Copyright © 1997, 1998, 1999, Ross Moore, Mathematics Department, Macquarie University, Sydney.

The command line arguments were:
latex2html -split 0 -no_navigation DesRev.tex

The translation was initiated by Jeff Scherpelz on 2002-04-03


Jeff Scherpelz 2002-04-03