Prototype Demonstration I (Discussion)

Contents:

This is the first Prototype Demonstration of the semester. You do not need to have a prototype built, or have user stories, tasks, and milestones finalized.

1 Managing Expectations

Your team (together) must convince the class (i.e., teacher, teammates and classmates) that:

there is a plan.
the plan is reasonable.
your prototype design is flexible.
your design and architectural decisions can be justified.

Most importantly… your team must establish that:

Everyone has access to https://git-community.cs.odu.edu.
Progress will be tracked systematically and electronically (e.g., using openproject).
Everyone understands the “Big Picture”.

2 Schedule

(10 Minutes) - Elevator Pitch & The Big Picture
- Summarize the problem.
- Identify the customers and end users.
- Summarize the Prototype (at a high-level)
(15 Minutes) - Prototype Defense
- Justify current development tools.
- Justify current design.
- Justify architectural decisions.
- Justify selected frameworks.
- Justify selected language(s).