CPSC 431 Final Demonstration - Fall 2004

27-minute presentation. Practice to be within this timing frame as we will also evaluate this.
2-3 minutes of questions (not included in the time above).
All members should present.

Details

Your presentation should cover at least the following items. The purpose of the presentation is to demonstrate your project, reflect on Software Engineering concepts in the context of your project, present your progress since the last presentation, and lessons learned.

1. Software Engineering Concepts

Most of the teams mentioned some Software Engineering terms in the Progress Report Presentation; however, they were not covered in the level of detail as expected. Hence, elaborate on at least the terms assigned to each team (see Table 1). Similarly as described in the Individual Report, avoid saying general statements such as "We iterated." Give specifics to backup your claims.

It should be clear when you are discussing such terms during your presentation.
If the term does not fit within your particular case, say why not and what actions you would have taken to accomplish it, adapt it, use it, etc.
Give the abstraction of the topic then details according to your project. Include consulted references.

Table 1. Software Engineering Terms Per Team
Section 501 (12/02/04)	Section 502 (12/01/04)	Section 503 (11/29/04)
Team 501-1 * Design rationale capture * V&V	Team 502-1 * Software configuration management * V&V	Team 503-1 * Cost estimation * V&V
Team 501-2 * Software development environment CASE * Management (plan, estimate, scheduling)	Team 502-2 * White box/black box testing * Management (plan, estimate, scheduling)	Team 503-2 * Life cycle model * Management (plan, estimate, scheduling)
Team 501-3 * Requirements * V&V	Team 502-3 * Automated software development - AP * V&V	Team 503-3 * Visibility * V&V
Team 501-4 * Product, Process, People, Project * Management (plan, estimate, scheduling)	Team 502-4 * Scale-up * Management (plan, estimate, scheduling)	Team 503-4 * Iterative * Management (plan, estimate, scheduling)

Table 1. Software Engineering Terms Per Team

Section 501
(12/02/04)

Section 502
(12/01/04)

Section 503
(11/29/04)

Team 501-1

* Design rationale capture
* V&V

Team 502-1

* Software configuration management
* V&V

Team 503-1

* Cost estimation
* V&V

Team 501-2

* Software development environment CASE
* Management (plan, estimate, scheduling)

Team 502-2

* White box/black box testing
* Management (plan, estimate, scheduling)

Team 503-2

* Life cycle model
* Management (plan, estimate, scheduling)

Team 501-3

* Requirements
* V&V

Team 502-3

* Automated software development - AP
* V&V

Team 503-3

* Visibility
* V&V

Team 501-4

* Product, Process, People, Project
* Management (plan, estimate, scheduling)

Team 502-4

* Scale-up
* Management (plan, estimate, scheduling)

Team 503-4

* Iterative
* Management (plan, estimate, scheduling)

2. Design Process

Describe the design process followed with an example.

Choose a use case and trace it all the way to the related classes in your design class diagram.
When showing collaboration diagram(s), describe which GRASP patterns were used and why.

3. Software Metrics

Report at least the software measurements specified in the Project Summary Report.

4. Team responsibilities

5. Project and Test Plan

6. Project Demonstration

Take the time to clearly show your final prototype. Avoid rushing. Be organized.

7. Conclusions

Include lessons learned and possible improvements.

Notes:

Post your presentation file on your Team Web site.
Submit your CD with all the artifacts created in this project (Team Web page and linked documents, presentation files, source code, UML diagrams, etc.).