Cell Society : Project Presentation

If I went back to college again, I’d concentrate on two areas: learning to write and to speak before an audience. Nothing in life is more important than the ability to communicate effectively. — Gerald Ford (38th American President)

Now that the project has been submitted, your team will present it in-class during the Lab period. Your presentation must be limited to 25 minutes with all team members presenting some of the content.

Start by showing off the features of your running program:

• run the program from the main branch through a planned series of steps/interactions (including showing how bad data or interactions are handled)
  NOTE, it is very helpful to have different people running the program and describing the feature (goals, errors, tests, design, etc.)
• show a selection of interesting data files and describe how they are used within your program
• show a selection of JUnit (at least 6) and TestFX (at least 3) test metods (include at least one negative test for each) and discuss why you chose the values used in the tests

Then present your team's design goals:

• describe your two APIs in detail (Simulation and Configuration):
  • show the key abstractions and their public methods
  • describe how it provides a service that is open for extension to support easily adding new features
  • describe how it supports users (your teammates) to write readable, well designed code, that is hard to misuse
  • describe the key implementation details it hides
  • show a Use Case that clearly shows off the API's effectiveness
• describe two designs
  • one that has remained stable during the project
  • one that has changed significantly based on your deeper understanding of the project: how were those changes discussed and what trade-offs ultimately led to the changes
• describe two features impacted by your design
  • one whose implementation was helped or made significantly easier by good design
  • one whose implementation especially challenged your design or uncovered hidden assumptions

Conclude by presenting what was learned about teamwork during this project:

• describe two specific significant events that occurred during the project (one positive and one that caused issues) and what the team learned from each
• describe two things regarding your teamwork and communication (one that worked well and one specific thing that could be improved)
• describe how each of you have worked to improve your teamwork during the project and, in the future, what evidence you could collect to validate improvement

Submitting your Work

Use GIT to push any materials specifically for your presentation in the folder doc/presentation to the main branch, such as code, images, UML diagrams, or written text (using Markdown, Javadoc or a wiki page on Gitlab) specifically to support your presentation.

If you choose to use slides, PowerPoint is discouraged because it is a separate from the code and unlikely to be maintained even if added to the repository. Here are some tools to convert Markdown to a slide style format.

Individual Requirements

When you are not on the team presenting, you will provide feedback that is focused on the content rather than the quality of the presentation itself (e.g., things you did not understand, felt were incomplete, or ideas you had to improve their work).

Use this form to submit your feedback for each team (three total submissions).

After each presentation, a few people will be asked to share their feedback synchronously while the remainder of the feedback will be sent electronically.

Giving and receiving feedback is also a skill you can work on!

Resources

Good presentations are practiced, presenting features in a planned order and using specific input values, rather than just capturing a team meeting — you do not have a lot of time to fit in everything asked of you.

• Slides with DOs and DONTs advice from my project course
• The original iPhone demo from 2007 is worth watching and studying

Giving demos is a skill you can work on!