Team Project Deliverables

These are the deliverables for the team project.

The Code

The final version of your code should be in the main branch of your GitHub repository.

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

NOTE: Make sure that you assign me as a contributor to your GitHub repository so that I can see the “Insights” for your project in GitHub.

The Final Presentation

At the conclusion of your team project, your group will give a 30 minute (3 teams in your section) or 45 minutes (2 teams in your section) presentation.

Here is a suggested structure for your presentation, with approximate times to spend on each part. The time estimates for each portion of the presentation are based on THREE teams presenting in a 2 hour period. You can expand those esimtate by 50% if there are only TWO teams presenting in your section:

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

2. Analysis and design: (4-5 minutes) Discuss your design model. In this part of the presentation, you must show your updated UML class diagram illustrating the most important classes and methods in your system, and how they relate/interact with each other. 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/eveolved as you worked on the implementation.

3. Database Schema: (3-4 minutes) Present the Schema for your SQL database. The DB Schema should include all tables with their attribute names (columns) and their respective data types, as well as how the tables are related to each other.

4. Implementation: (4-5 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.

5. Demonstration: (8-10 minutes) Show your system working. Demonstrate the most important/interesting features, and run your JUnit test cases.

6. Conclusions: (5 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 between 7-10 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 - business casual. All of the members of your team must participate in the presentation.

Please make sure that your presentation is ready to go immediately when it is your group’s turn, including have your demo ready to run.

The Final Project Report

Submit a 4-5 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

Feel free to ere on the side of more content, rather than less. Also, don’t forget to include the “main” repository URL as mentioned above, with me assigned as a contributor to your project.

Submit the report to Marmoset as assign08report-usernames as you have done for other team assignment submissions. 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.