Design Patterns in OO Programming
Fall, 2009

CIS 4930
Term Project Deliverables

 

Details

Presentation contents

On Monday at 5:10pm you (and your team) are expected to a) deliver a paper describing your project and justifying the design decisions you made and a hard copy of all visuals that will accompany your presentation and b) be prepared to make a coherent presentation covering both:

  1. General goals and an overview of the functionality provided. Discuss specific features and how a (card) designer would interact with your system. Use specific examples: have at least 5 different reference cards that illustrate different aspects/capabilities of the system (that includes output mockups, script and configuration file inputs).
  2. In depth discussion of how the system work, design decisions, etc. Describe how the system is structured, the responsibilities of each of its parts, how its parts interact to solve the problem, what design patterns were used (where and why).

Presentation tips

  1. The projector's native resolution is 800x600: keep that in mind when preparing your visuals. Each "slide" should contain just the information required—nothing more, nothing less. For example, a slide showing an overview of the relationship between classes in a subsystem does not need to list the attributes and behaviors of those classes; when discussing a particular class (or a small group of them), then it probably will be appropriate to show more detail.
  2. Powerpoint is not a requirement. Visuals are.
  3. Everyone is expected to spend an equal amount of time speaking
  4. Practice giving your presentation!
  5. If you use a tool to generate UML from your project's source code, please clean up the resulting diagram as such tools usually produce messy results. (ROTFL!)
This website is an original work, Copyright © 2009 by Dave Small. All rights reserved.