(subject to change)
Group No._______
Group Members:
1:
2:
3:
4:
Important
Note: All students are expected to be present at your group demo.
The demo presentation
consists of a short overview of the team work, a planned demo from a user's
perspective, a code walkthrough upon request from instructor or TA, and a
summary Q&A.
1)
Description of
the demo process, including (1) the components you will demo, and (2) the
components you won't demo, and the reasons.
2)
Description of
two most interesting design and implementation decisions made by the group,
including a rationale for each and an analysis of how good they turned out to
be.
3)
Description of
the test strategies and the types of tests conducted prior to demo.
4)
Demo to the end
users (instructor/TA), including GUI/Command line functions, example code
walkthrough.
5)
Group
cooperation, sample questions:
-
The distribution of tasks within the group
-
What have been done and what have not, in terms of the goals, requirements, and
plan defined in the design phase
-
Three most important lessons you have learned as a group through hand-on
experience with this project.
-
Is the course project useful for understanding the principles of this course?
-
Instructor/TA's wrap-up questions
*
Optional: Anything that you want to tell us related to your project or the
course in general?
6)
Each group member hands in a half page description of what you did in
the project and your evaluations for other members. Give this to the
instructor/TA in folded paper. All information will be kept confidential by the
instructor and TA.
Check
List for documents of Phase II
1)
A hard copy of
your final report, describing
i.
the purpose of
the phase II
ii.
revisions made to
the specification and the design in the previous phase
iii.
The problems you
encountered in this phase and your solutions
iv.
System
architecture
v.
Design and
description of all functions
vi.
Evaluation about
your system, the limitation and the potential improvement
2)
Source code (.zip
file) with a simple user manual for your system (readme
file).