The code will be demonstrated and tested in class. All written materials must be submitted in a labeled three-ring binder, and must be nicely formatted (including page numbers and a table of contents).
1. Code (50 points)
The complete code of your project, tested and without significant bugs. There must be 8 functional, tested use
cases per team member. The program must have appropriate
nonfunctional qualities, including reliability, performance, and usability (the relative importance of each of these
depends on the nature of the project). Both source code and executable code have to be submitted on a CD.
The source code must be properly formatted and documented. The code will be graded
both on completeness and on quality.
2. Manuals (10 points)
a) A user manual, explaining all aspects of the program to a user. The user manual must be both available on paper
and digitally (for example as part of the help feature of the program).
b) An administrator manual, explaining installation and configuration of the program to a professional system administrator.
3. System Test Reports (30 points)
40 system test cases per team member, and their results (if not fully passed), and two system test reports for
nonfunctional properties, such as a usability test or a load test.
There also has to be a summary discussion of the test results, including the percentage of test cases that have passed.
4. Updates (10 points)
Updated requirements, analysis, and design models, including use-case realizations.
If adjustments to these requirements are necessary due to the nature of your project, please contact the instructor. All models have to be consistent to each other.