Presenter

For a presentation of your designs or a code walk, please proceed as follows:

1. Concisely restate the task, which points you chose to pursue, and which ones you chose to ignore.
2. Provide an overview of your solution. For code walks, this includes two parts:
   1. a (UML class) diagram of the major components and their relationships;
   2. a (UML interaction) diagram that explains the major interactions during a program execution.
   In addition, you may have to explain other aspects of the design.
3. Present the components and their functionality in a top-down fashion, no matter how you designed and implemented them. Refine as requested. Be prepared to defend your code organization, why it matches or doesn't match your design.

In general, be prepared to figure out in real time how changes to your information/data specification are translated into changes in your program organization.

As a listener, you will play three different roles:

• a manager, who is the first "reader" (analyst) and who has the responsibility that the presentation stays on track;
• an assistant reader, who is the second "code reader";
• secretary, who keeps track of the questions that the readers ask, notes discoveries of weak spots, and takes notes as needed.

When you play "secretary" you are responsible to get a copy of the written notes to Sam T-H. and the pair within 48 hours.