Create Class Diagram

[mhh916]

Consider the first 5 (more is fine) or so use cases and develop a neat, legible, properly sized UML class diagram(s) showing your initial design. Classes should show state and behavior. It is not important to capture every detail. Every time you look at your document, you will see new things you didn’t think of before: a required instance variable, a parameter for a method, a missing method, a method in the wrong class, a new class, etc. The important point is to establish a starting point for the design.