SWE 2410 Presentation Project, Phase 2

Introduction

This is a continuation of the first phase of the presentation project. This phase is to complete the work started in phase 1, particularly focusing on your JavaFX program which illustrates how the key advantage contributes to the software design. You will also finalize your presentation by inserting missing diagrams, adding snippets of the code you write, adjusting the presentation based on your instructor’s feedback, and capturing changes needed to strengthen the presentation.

Implementation Requirements

• You will write all code for your project. In all cases, be sure to properly attribute any code written by someone other than a team member. Where your idea for your example application is inspired by an online source, be sure to share that source with your instructor early in the project.
• Be sure you use interface classes for your patterns. The base class name should make it very clear what pattern is being used. For example, if you are applying the State Pattern to washing machines, you should have an interface with a name like WashingMachineState.
• Document each class with its author and primary responsibilities. A significant portion of your grade will be based on this documentation.
• Ensure all fonts in the application are large enough to be read from the back of the classroom. This generally means font sizes that are at least 50% larger than the default. Any output you want your audience to view must be on a JavaFX window, not a console. Make good user experience (UX) choices fitting to your application.
• Check that the application is “real”. That is, that it makes sense as the part of a larger application. Changes on the screen must be more than just a change from one graphic to another; something must be computed that has potential value to a user. Discuss with your instructor if you are not sure what this means.

Finalizing Presentations

• Presentations should be between 10 and 15 minutes long (before questions, depending in part on the number of teams). If you discover your presentation is too short as you practice it, delve a little deeper into the pattern and/or examine whether your key advantage was stated too narrowly.
• Review the requirements for the presentation shared at the start of the project.
• Practice the full presentation and be sure it fits within time limits.
• Ensure the presentation uses large fonts. In most cases, 22-point font should be considered a minimum. In some cases, however, the minimum is a 30-point font. When the presentations are in a classroom, go to that classroom and check that your full slide deck and any examples are easily read from the back row.
• Before the presentation: run the code on the presentation laptop and make sure it is working, then do not make any changes to it.
• Presentations will be given during the last lab period of the term. Your instructor will announce the order at the start of class. All teams must be ready to present at the start. Working on your presentation during other presentations is not allowed.
• All students are expected to present part of the material unless the group is very large or there are other extenuating circumstances. Get approval from your instructor for exceptions.

Evaluation

You will be evaluated on the effectiveness of your presentation, including defining your terminology, tying concepts to the examples you provide, and highlighting the key advantage. The presentation is to be targeted at your peers: students who have studied design patterns but may have no knowledge of the pattern you are presenting. While the final grade will include many factors, a primary portion will be based on the SWE2410 Exhibit Curiosity Rubric:

• Exemplary: the pattern and associated demonstration program are well-described in a way that is understandable by peers, and the presentation reinforces clear goals.
• Accomplished: the pattern and associated demonstration program are well-described in a way that is understandable by peers.
• Proficient: the pattern and associated demonstration program are adequately described in a way that is understandable by peers.
• Developing: the pattern and associated demonstration program are partially described, possibly lacking needed information or being overly technical.
• Beginning: the pattern and associated demonstration program are not sufficiently described to explain their purpose. Be sure to address any comments made by your instructor based on earlier drafts of the presentation.

Submission

Submit the following:

• All code for your demonstration project must be pushed to the main branch in your repository.
• Capture screen shots of your demonstration project in action (from the user’s perspective) and submit a PDF of that to Canvas.
• Submit your final slide deck for your presentation to Canvas.
• Submit individual contributions reports as directed by your instructor.