CS 48, Spring 2018

Progress Report 6
Special Instructions

Oral report

Present some details of one of your (most interesting) interaction diagrams. Interaction in this case means the way objects internal to your system interact with one another (by sending messages in the form of function calls) to complete an operation. It does NOT mean interaction between the system and an actor - that is the subject of a use case diagram, and you already presented one of those in Progress Report 3.

It would be most entertaining, and probably most informative to have more than one team member present the interaction together. Each speaker would represent a different object, and the speakers would alternate their responses as if they were executing the interaction, something like the following imaginary case:

Member1 (representing a TargetButton)
I detect the user clicked me, so I call the respondToClick method of all objects in my list of ClickListeners, and pass them each a reference to myself.
Member2 (representing a ButtonMonitor)
My respondToClick method is called by a TargetButton, so I tell the Game package about it by passing a code that identifies the target to the TargetRecorder's recordTarget method.
Member3 (representing a TargetRecorder)
My recordTarget method is passed a target code, so I update the score for the target by calling the GameData's updateScore method.
... and so on until the interaction is complete (hopefully a bit longer and more interesting than this one).
It is okay if one member wants to present it alone too, but please don't skip this step.

Be sure to leave time for telling us your general progress, to-do items and problems as well.

Written report

Please do not include the interaction diagram in your written report. We can see that and much more in your Draft Project document. Just tell us your progress, to-do items, and problems as usual.

And remember to submit it to Gauchospace before the 6:30pm deadline.

Updated May 11, 2018 by C. Michael Costanzo

CS 48 homepage