Interim Demonstration (Discussion)
Contents:
This is an interim Prototype Demonstration.
- You do not need to have a complete prototype.
- Your prototype interface(s) do not need to be “pretty”.
You must be able to demonstrate progress.
1 Managing Expectations
Your team (together) must convince the class (i.e., teacher, teammates and classmates) that:
- there is still a plan.
- 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 is being tracked systematically and electronically (e.g., using openproject).
- Everyone understands the “Big Picture”.
2 Schedule
- (5 to 10 Minutes) - The Big Picture
- Briefly summarize the problem (no more than one slide).
- Briefly summarize current development tools.
- (15 to 30 minutes) - Prototype Progress
- Describe the current design (algorithms and architecture).
- Describe any changes to your design since the previous demo.
- Justify all changes to your design since the previous demo.
- Summarize issues encountered with:
- selected frameworks
- selected language(s)
- Summarize where you will be in
- 1 week
- 2 weeks
- 4 weeks
- 6 weeks
- Describe the current design (algorithms and architecture).