Team Project Deliverables

These are the deliverables for the team project.

The Code

The final version of your code should be in your “main” repository.

Important: In your report (see next section), include the URL of this repository.

The Report

Submit a 2-3 page report describing:

Of the requirements you proposed initially, which you completed and which you did not complete
The most important technical challenges your team faced, and how you overcame them
What development practices your team used, how well they worked, and what you might do differently for future projects
How you might continue to develop and enhance the system in the future

Also, don’t forget to include the “main” repository URL as mentioned above.

Submit the report to Marmoset as assign08report. Use only PDF: do not upload a Microsoft Word or rich text document.

Your report must be submitted in PDF format. Submissions in any other format may receive a grade of 0.

The Presentation

At the conclusion of your team project, your group will give a 15-20 minute presentation.

Here is a suggested structure for your presentation, with approximate times to spend on each part:

1. Background: (2 minutes) What problem were you trying to solve? Discuss the system requirements.

2. Analysis and design: (3-4 minutes) Discuss your design model. In this part of the presentation, you must show a UML class diagram illustrating the most important classes and methods in your system, and how they relate/interact with each other. Use Violet UML to create the diagram. In order for the diagram to be legible during the presentation, it should contain at most 8 or so classes, and each class should show at most 1-3 methods. You can use multiple diagrams if you want to show more classes than would fit in a single diagram.

This is also a good opportunity to discuss how the design of the system changed as you worked on the implementation.

3. Implementation: (3-4 minutes) What were the most interesting things you learned when you implemented the system? If you used any interesting programming techniques, this is a good opportunity to discuss them.

4. Demonstration: (5-7 minutes) Show your system working. Demonstrate the most important/interesting features.

5. Conclusions: (2-3 minutes) Sum up what you learned. If there are aspects of the project you would do differently if you started again from scratch, mention them. You can also talk about how you might want to extend the system in the future.

Your presentation should include no more than 6 slides.

Please rehearse your presentation! Do a dry run of the demonstration before the presentation. Make absolutely sure everything is working and ready to go before you present.

This is a formal presentation, including appropriate dress. All of the members of your team must participate in the presentation.

Plan on giving the presentation and demonstration using your own laptop, as the instructor PC has been quite unreliable this semester.

Make sure that your presentation is ready to go immediately when it is your group’s turn.