Department of Computer Science and Engineering

College of Engineering, University of Nevada, Reno

 

CS 426 Senior Projects

 

Project Part IV:

Implementation, Integration and Testing

 

April 14, 2004

 

Due:        Tuesday, April 27,  2004 @ 12:00 pm (noon) by email

Points:    100

Weight:   29% of the course grade

 

 

                                                                                                                                      

A  Deliverables of Part IV of the Project

     

This final part of the project involves submitting the complete, commented source code of your software (by email, in a zip file, before noon, 12:00 pm, Tuesday April 27, 2004) and demonstrating your project to the instructor and the TA on April 27 or April 28). All the members of the team should be present at the demonstration.

 

Deliverables:     

t of  user interfaceplete shanshanpshots

A1   Introduction and overview. The introduction file should concisely indicate changes and additions, if any, of your project’s specification and design (recommended maximum size: one page). The overview file should provide a summary of your source code (see A2 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 Tuesday April 27 in a zip file that should also include the entire source code indicated next.    

 

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

 

A3   Test cases. These will be illustrated by demonstrating the functionality of your software to the instructor and the TA. 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 and the TA will try additional uses (tests) of the program and will ask you questions regarding the project.

 

B  Grading of Part IV 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.