CSSE 220 – Object-Oriented Software Development

Homework 16

Objectives

Practice implementing a Graphical User Interface (GUI), including event-driven programming. More practice with interfaces and implementing them.

Tasks

Complete the assigned reading for the next session: Big Java §10.1–10.7, plus skim the rest of the introduction to UML class diagrams at http://www.objectmentor.com/resources/articles/umlClassDiagrams.pdf.

As you read, see if you can answer the self-check questions (for the Big Java reading).
Bring your questions to class!
This reading and assessment are longer than most; budget your time accordingly.

Complete the assessment exercises over this reading on ANGEL (under Lessons → Assignments).

Pair programming: SwingDemo2.
1. In Eclipse, checkout the SwingDemo2 project from your shared repository for this project:
  - This is a shared repository where you’ll work on SwingDemo2 with your partner.
  - The URL for your shared repository is:
```
    http://svn.csse.rose-hulman.edu/repos/csse220-201020-swingdemo2-teamXX
```
    where XX is your team number as given by your instructor.
  - Note: Now that you’re working with a partner, you can get hard-to-resolve SVN conflicts with your partner’s code. So please remember to do Team → Update for the project
    - when you first start working in Eclipse, and
    - whenever you are about to commit.
    If you and your partner always work together doing pair programming, then conflicts should not be a problem. (But be sure to ask for help if you get stuck.)
2. Follow the SwingDemo2 instructions on the course web site, under Programs ~ SwingDemo2 ~ instructions.htm.
This project is due at the beginning of Session 18 (so, not the next session, but the one after that), to give you time to meet with your partner out of class.
- But note that other projects will be in progress concurrently.
- Make sure that:
  - You do this project with your partner; do NOT do it alone. If your partner is unavailable or uncooperative, get help from your instructor.
  - Both team members understand all the code the team is turning in.
  - You complete the entire project.
  - You use good style throughout:
    - No errors or warnings should remain in the code that you turn in.
    - Control-shift-F is your friend!
    - You do NOT need to have any documentation in this exploratory exercise.

Turn-in Instructions

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