All teams must be prepared to give their report
Monday, March 7, 2022 at 9:30 am (class time).
We will proceed in random team order.
We will have 7-8 presentations on Monday, and 8-7 more on Wednesday in
the class time slot.
All students are required to attend all sessions
We will keep an attendance record. I want each team to honor
the work the other teams have done by listening to their presentations...
just as people will be listening to you.
Each presentation slot is 8 minutes long, and that slot must contain the presentation, time for some questions, and swap time to get the next team in place and running. Therefore, plan for about 6-7 minutes of presentation.
Be sure to do a run-through of your presentation (at least one) for timing purposes. If you are not experienced at public presentations, it is fairly common to try to pack 15 minutes of material into a 6-7 minute talk. It also sometimes happens that the presentation might be too brief; you dont want to finish your "7 minute presentation" in 2 or 3 minutes. Practice.
Identify your project name, date, your team members and your client. After that, you have four main content chunks to present (not necessarily in this order):
Functional overview:
Tell us who your users are (what types if
there are more than one kind of user).
Also tell what services and
functions your system will provide for your users. This is basically
telling us your requirements, but dont just put the requirements
document into powerpoint and read it to us as bullet lists. Summarize.
Hit the high points.
Inform.
Explain your system from the user's viewpoint.
What problem(s) do your users have? How will your software assist them
to solve their problems?
User interface mockup:
To assist in giving us the user's point of view, provide mock
ups for the user interface. This is not anything final, just
whatever idea you have at the moment of how the system will
look and be interacted with. Pretty pictures make nice eye-resters
while you talk about details.
These mockups also give you a good way to talk about
your requirements and system functionality.
Technical overview:
Since almost all projects are very early in code development,
this section will mainly be a presentation and explanation
of your architecture diagram. Feel free to include
any supporting details from the design of subsystems that
you might have, but we are looking in this presentation
for high-level structure. Technical details will be
a larger component of your final presentation at the
end of the semester.
Platform description:
Tell us what language(s) you are writing the code in, what IDE(s)
are supporting your development, what code libraries you are
building on, what sort of hardware your system is intended to
execute on, what operating system is supporting your product.
Unlike the platform discussion on your website (where you
give all the technical options you considered and what you ultimately
chose to use) in this presentation we just want the final
choices for your project.