UML diagram and relational scheme problem

INTRODUCTION: In Western music, the key of a piece of music tells the musicians playing the music which notes to sharp and which notes to flat?. For instance, the key of A major" has three sharps: F, C, and G. Each key will have zero or more sharps or zero or more flats, never both sharps and flats. The key of C major has no sharps or flats. The notes of the scale are {A, B, C, D, E, F, G}. A given note can be sharped or flatted just once in any key. You will want to represent the definition of the key in your model. A particular piece of music always starts in one key. It may stay there the whole way through, or the composer may decide to change the key at one or more points along the way. A given piece of music can change keys any number of times, and it is possible for a piece of music to change to a given key more than once. When you lay out the route that you take on a vacation, you talk about the number of miles you are from home at each stop along the way. When you lay out the sequence of events in a piece of music, you indicate which measure something happens in. The measures are numbered, starting at 1 (unlike array indexes in C) and follow consecutively. A piece might start off in F major (measure 1), modulate up to G major in measure 45, and then modulate back down to F major for a final reprise in measure 107. For our purposes, we will assume that you can identify a piece of music by the composer and the year that it was written. Remember that this is data about the music itself, not any performances of the piece. PROCEDURE: 1. UML model the above information. Broad hint: there will be two many to many associations: one without history, and one with history. 2. Make your relation scheme diagram for the UML