CSSE 220 – Object-Oriented Software Development

Homework 14

Objectives

Practice with designing and implementing classes. Learn the UMLet tool for drawing UML class diagrams.

Tasks

Complete the assigned reading for the next session, according to the course schedule.
- As you read, see if you can answer the self-check questions (for the Big Java reading).
- Bring your questions to class!
Complete the assessment exercises over this reading on ANGEL (under Lessons → Assignments).
Individual Programming: Complete the Static project that you began in class, as follows:
- Run the program.
- Note that the least/most number of sides data is shown but is -1 (not yet implemented).
- Read all the TODO’s in the Polygon class.
- Do and test the TODO’s for most number of sides, asking questions as needed.
- Do and test the TODO’s for least number of sides.
  - You might find Integer.MAX_VALUE helpful.
You should have completed the following in class, nothing to turn in for this item for homework:
1. Using CRC cards, develop a design for a program that lets two players play chess against each other.
  - Assume that the players enter moves in the (single, shared) console, but that the board is displayed in a window.
  - You will do this in groups of 3 or so, who share a single set of about 10 index cards.
2. Convert your CRC cards to a UML class diagram. Show the relationships between the classes, but you need not show the details (attributes and operations) for each class.
  - Each individual should draw their own diagram.
Install UMLet: Download and install the UMLet program for drawing UML diagrams by following these instructions.
CRC card and UML class diagram exercise : Use UMLet to draw a UML class diagram for our CRC cards for Chess.
- Draw only the classes and relationships (NOT the insides of the classes).
- Exception: Draw the insides (that is, the attributes (that correspond to fields) and operations (that correspond to methods)) for the ChessDisplayer and ChessMove classes.
- Print your completed UML class diagram and bring paper copy to class.

Remember, in all your code:

Write appropriate comments:
- Javadoc comments for public fields and methods.
- Explanations of anything else that is not obvious.
Give self-documenting variable and method names:
- Use name completion in Eclipse, Ctrl-Space, to keep typing cost low and readability high.
Use Ctrl-Shift-F in Eclipse to format your code.
Take care of all auto-generated TODO's.
- Then delete the TODO comment.
Correct ALL compiler warnings.
- Quick Fix is your friend!

Here is the grading rubric for this assignment.

Turn-in Instructions

Turn in your programming work by committing it to your SVN repository for this project. Bring your written work to class.