[Java] - UML Diagram

Howdy, so I am currently enrolled in a university-level Object Oriented Programming & Design class where Java is the language being utilized. The current project is to create a Flashcards program, complete with OOP-style programming and a GUI.

We are building this in steps over the entire quarter (10 weeks long). The step I am currently stuck on is a UML Diagram of the code. I am not allowed to turn in any future parts of the project until I turn in the diagram.

So here are the requirements for the project itself:
Introduction
• Using the MVC (model/view/controller) architecture paradigm, you will first complete the model and controller with a text-based view.
• In the future you will replace the text-based view with a GUI view.
• Eventually Flash Card sets will be permanently store in text files on the disk.
Requirements
• The flash card application must run from the command line (not an IDE).
• The flash card application should allow a user to create sets of flash cards. The user should be able to name the set and then create flash cards within the set. The flash cards should be able to be ordered in the set.
• The flash card application should allow a user to create two different kinds of flash cards: manual flash cards that can be “flipped” (show the answer) upon user request, and timed flash cards that will display the question and then wait a specified period of time before automatically displaying the answer.
• When studying the flash cards the user does not need to enter the answer. The application only needs to display the question and then display the answer either after time expires or user input (depending on the type of flash card).
• For this first lab the flash cards and flash card sets only need to be stored in memory – not written to disk. This means that the information will only last until the application exits.
• You should create test classes to unit test the methods of your objects.
• You should validate all user input.
• Your model classes should generate exceptions on invalid data.
• Your view classes should handle those exceptions and display friendly error messages to the user.
• Your design must include classes and inheritance.
• Your design must not duplicate any methods or properties.
• Properties and methods should be placed in the classes that make the most semantic sense.

To try and help myself build the UML Diagram, I have designed all of the GUI interfaces using Photoshop. This is what it looks like:

http://puu.sh/6ASUh.png

Lastly, here is what I have come up with so far for my UML Diagram. I am using UMLet for this. I'm open to any alterations that would need to be done to my UML diagram if they lead me in a better direction or would be a better way of putting everything together.



I'm more than happy to answer any questions related to this. Any help would be heavily appreciated!