ICSG707 -- Programming Practices

Group Project -- Demo & Final Submittion

Last change date: May 12, 5pm

1. Problem description

For this part of the project you will be implementing the project that you have been designing. In addition, your team will be putting on a demo for the class.

1.1. Demo

Each team will have 25-30 minutes to discuss its project and present its final product. Every team member will be getting an individual grade for the demo, and should have a role in the presentation. The presentation must address the following four main topics:

• A recap of the product's design (at a very high level), with a brief discussion of how the design evolved from the LLD document.
• A discussion of the main features of your product, and how these relate to your original specification and your planned delivery levels.
• An assessment of the project, process, and product. What are the product's strengths and weaknesses? What did you learn about the process of software development? What would you do different next time?
• A demonstration of the product.

Each team must decide how to apportion its time among these areas; part of the grade will depend on your adherence to the minimum of 25 and the maximum of 30 minutes.

1.2. Final Project Code

You will be submitting all the files needed to build your project. All files should be checked out from the RCS system will full revision history in place (if RCS was used). All files should be placed in a directory called fin_proj which will be submitted to the grading account.

In addition, if your project created data-files that are used in the execution of your program, I want you to submit copies of these files with the submittion. These can be placed in the fin_proj directory, or in a subdirectory. Just make sure that your README contains instructions on how to run your program using these files (ie. copy executable file to subdir. or whatever).

2. Final Due Date

All documents are due in class on Tuesday May 19th and the code is due to me by midnight May 19th. All demos will be held during the normal class period on Tuesday May 19th

Basically, everything is due Tuesday May 19th.

3. Deliverables

The team should submit the following components:

• The in class demo.
• All files associated with the project including a README file.
  • All your files for the project should be placed in a single directory called fin_proj The README file should also be in the in the directory.
  • This should be submitted electronically using the command:
    submit -v paw-grd project fin_proj

• The Users Guide document (with cover page for title, authors, date, etc.)
• A separate document with a description of the work done by each person.

• Self evaluation
• One evaluations for each person on your team

3.1. README

You must submit a file named README with your project. This file should contain information that I should know about your program. This must include how to compile and run your test program (this should document just the basics of executing the program (ie. what needs to be typed from the command line to execute it. Complete descriptions of how to use your project should be included in the Users Guide).

It should also contain a list of all the files submitted describing what the files contain, and why they were submitted. In addition, you include any notes you think would be useful while I grade the assignment.

4. Grading

Grading will be done using the following criteria:

    Deliverable                         Weight
    --------------------                ------------------
    Code
	Execution			65%
	Style, README			20%
	Evaluations			15%
    Users Guide 
	Quality				80%
	Evaluations			20%
    In Class Demo
	Individual part			50%
	Overall 			50%