-Under the Moosique class we designed three classes that modifies different parts of an midi-file. \r
-MooSequence [...], MooTrack [...] and MooNote [...]. \r
+In a hierarchy below the Moosique class, we placed three classes that represented the different parts of a MIDI file: \r
+x MooSequence The functional representation of a MIDI sequence. Was to extend Java's Sequence class.
+x MooTrack The functional representation of a MIDI track. Was to extend Java's Track class.
+x MooNote The functional representation of a MIDI note. Was to encompass the two MIDI events that constitute a note: NoteOn and NoteOff.
+
+The second part of the program was the graphical user interface, including all the graphical classes. The main class of the interface was named MooGUI. Since we had decided to use Swing in building the interface, this class was naturally to extend JFrame. Here, all other GUI components were to be created. Most of these components - maintaining different kinds of data, having listeners and requiring different methods for update their content - were to be quite complex, and were therefore given their own classes. Among these are graphical classes that construct the menu, the toolbar and the view of the MIDI tracks. All these classes [...]. \r