Assignment 4: SE2-Software Design & Architecture
(CS446/CS646/ECE452) Spring 2011

Assignment 4:

Note:

If your project is at a stage where you don't have a working demo available, then use mock objects, UML diagrams, or other visualizations to present your ideas. I understand that the early presenters will be in this situation. In this exercise you are not being evaluated based on code/feature completion of your project. You are being marked for how well you can present your term project to your classmates.

Marking Scheme (5*)

• Presentation of the core components (3/5*)
  • Summary of the key components (.5/3)
  • Main use cases and how they are realized (1.5/3)
  • Justification of your design: Why do you think the design you used is the right design for your problem(1/3)
• Presentation of the realization(1.5/5*)
• Presentation quality: starting on time, engaging the audience, answering questions (*.5/5)

Goal:

You are to present your implemented system. This will include demo'ing the key features of your system. The audience should learn what you have done and not done, and what is your overall architectural structure.

Presentation:

• Presentation Length: 15 mins (will be enforced) – Please rehearse your presentation and make sure that you make good use of the 15 minutes.
• Slides: You should use slides (such as Power Point Slides) and as well you should show your system in operation. You are to turn in your slides (hardcopy and softcopy). There is no separate report for this assignment. Your slides should include the following:
  • Title slide: Title of about 3 to 6 words, including names of team.
  • Overview slide: Give clear overview of entire presentation.
  • Purpose of project: Make clear the purpose and proposed use of your software.
  • Body of presentation: Give slides for each major point you want to make.
  • Conclusion slide: List essential points and what you accomplished in the project.
• Important Presentation Requirements:
  • Ensure that your presentation material (slides & demo) can start quickly.
  • Make sure you get across your main points and you don't get lost in details.
  • Make sure that your architecture is clear from you slides.
  • On a slide, state who in the team was responsible for what part of your project.
  • Do not try to show too many slides. A rule of thumb is that each slide takes 1 to 3 minutes.
  • Ideally, half of your time will be for slides and half for your demo.
  • You are responsible for making sure that all audio/visual equipment is working for your presentation.

  ---

  Last updated on: Jun 26^th, 2011 by Atif Khan.