Department of Computer Science

College of Engineering, University of Nevada, Reno

CS 425/625 Software Engineering

Team Project Part 3:

Implementation, Integration and Testing

November 17, 2003

Due: Monday, December 8, 2003 @ 12:00 pm (noon)

Points: 100

Weight: 13% of the course grade

A Introduction

Your team of software engineers has completed both the Requirements Analysis & Specification part and the Design part of the Xanadu Cup project. Now, you have to complete the final part:

Part 3: Implementation, Integration, & Testing [due Monday 12/09, 2002; worth 13%]

Please refer to section B of Project Part #1 for the text of the problem.

B Deliverables of Part 3 of the Project

This final part of the project will involve submitting the complete, commented source code of your software (by email, in a zip file, before noon, 12:00 pm, Monday December 8) and demonstrating your project to the instructor and grader on December 8 or December 9 (please contact the instructor as soon as possible to schedule your demo). All the members of the team should be present at the demonstration. Deliverables:

t of user interfaceplete shanshanpshots

B₁ Introduction and overview. The introduction file should concisely indicate changes and additions, if any, of your project’s specification and design. The overview file should provide a summary of your source code (see B₂ below) in terms of program units and modules (classes and packages) included in the souce code. Both files should be submitted by email before noon Monday December 8, in a zip file that should also include the entire source code indicated next.

B₂ Source code. The entire, documented source code of your program should be submitted by email in the zip file mentioned above.

B₃ Test cases. These will be illustrated by demonstrating the functionality of your software to the instructor and the grader. At the time your demo is scheduled you should be prepared with the program “ready to run” and have a sequence of tests prepared. The instructor will try additional uses (tests) of the program and will ask you questions regarding the project.

C Grading of Part 3 of the Project

The final part of the project will be assessed using to the following criteria: completeness, correctness, and robustness of the software; programming style used, including code documentation; quality of the user interface; and quality of the demonstration, including answers to questions.