CS 471 Fall 2024 > Mini-Project Presentation #2 (Second Progress Report)
CS 471 Fall 2024
Mini-Project Presentation #2 (Second Progress Report)
For general information about the mini-project, see Mini-Project Presentation #0; everything in the General section still applies.
This document covers Mini-Project Presentation #2.
Presentation #2 Requirements
Mini-Project Presentation #2 will be made in class on Monday, October 7, or on the following class meeting day if we run out of time. You will discuss the progress made so far on your team’s mini-project.
As with the previous presentation, your presentation must cover each of the following, with slides and possibly other things, as appropriate, displayed on the classroom projector.
- Title slide at the start of your slide deck.
- General project description, including deliverables.
- Brief description of your MVP.
- Summary of what has been done and challenges encountered.
- Project Kanban board.
- Project repository.
- Demo/mock-up/drawing of your project.
In addition, your presentation must include the following.
- Architecture diagram.
- Testing plan.
The above items do not need to be covered in the order shown.
Your architecture diagram (or diagrams) must be along the lines of the box-and-line diagrams covered in class. If you wish, you may also have one or more diagrams of other kinds—for example, a UML class diagram or a use-case diagram—but these are distinct from the required architecture diagram.
Your testing plan does not need to be a formal document. Simply indicate how you plan to test your work—or how you are already testing it. This must include at least one of the kinds of testing covered in class (other than ad-hoc testing).
Do not assume your audience remembers your earlier presentations. Any necessary information from previous presentations must be presented anew.
Grading & Feedback
Standards for this presentation will be a bit higher. Rather than merely making a good-faith effort to give a good presentation, you are expected to give an actual good presentation.
Your score, along with feedback, will be given in written form within a few days after the presentation.
Thoughts
Reusing slides from week to week is a fine idea. But be sure your reused slides are correct.
While your testing plan is not a formal document, it does need to provide good information about how you intend your testing to work. Here are some things to think about when putting the plan together.
- When is the testing to be done?
- Who does the testing?
- Is your testing an integral part of your process (for example, unit testing that is required at check-in to the repository) or is it separate?
You have been introduced to a great number of tools and practices in the CS program, and perhaps in other experience you have had. Because these are not required in this project does not mean they are forbidden. If you think something would be helpful in your project, then my all means use it. You may wish to put information about it on your slides and to discuss it in your presentation.