ºÝºÝߣ

ºÝºÝߣShare a Scribd company logo

Ds project

?
?
J
Junaid Ghouri

This document provides information about a semester project on data compression using Huffman coding that is due on December 24, 2012. Students are to complete the project in groups of up to three people. They must submit a .rar file with their source code, input and output files, and a readme file. The project report and presentation are also required. Code must follow modular programming style and include meaningful comments. Correct working code earns full credit while code that does not compile or work properly receives only partial credit.

1 of 2
Download to read offline
Data Structures & Algorithms Semester Project Data Compression using Huffman Coding Due Date: Monday 24 December 2012 There is nothing in this document except the Project Title, Submission Details and the Project deadline. So, no lengthy 12 pages statements.. (happy ?) Maximum persons allowed = 03 ? ----- ? Collaboration Policy: You are not allowed to share code. So do not give your code and do not take code from anyone. You might end up in trouble (this time, I will make sure that you will.), and always remember that, ¡°Honesty is the best Policy¡±. Submission Policy: Submit a .rar file burned in a (labeled) Compact Disc (CD) which be having all your .cpp and .h files, a Readme file along-with the input text file (the file to be compressed) and the output text file (the compressed file). Readme file must be having your group name, group members name and any other info that is needed to run your program properly. Deadline will not be extended this time as well, and I expect you to fully utilize your time right from the first day. The Project constitutes 12 absolute marks which will be distributed among proper working Code, Project Report, Presentation and Viva (individual). A proper formatted Project Report (black and white form) must also be presented while submitting your project, which should fulfill proper guidelines that will be conveyed in the coming classes.
Coding Requirements (these carry credit): 1. You have to use modular programming style. 2. Write meaningful comments. Do not litter you code with comments only when they are needed they should be there. 3. If your code does not compile you won¡¯t get any credit. 4. Only correct working gives 80% credit; if your program does not work, code review would only give 20% (these are after we have made other deductions). ? Best of Luck..!! ?

More Related Content

Ds project

  • 1. Data Structures & Algorithms Semester Project Data Compression using Huffman Coding Due Date: Monday 24 December 2012 There is nothing in this document except the Project Title, Submission Details and the Project deadline. So, no lengthy 12 pages statements.. (happy ?) Maximum persons allowed = 03 ? ----- ? Collaboration Policy: You are not allowed to share code. So do not give your code and do not take code from anyone. You might end up in trouble (this time, I will make sure that you will.), and always remember that, ¡°Honesty is the best Policy¡±. Submission Policy: Submit a .rar file burned in a (labeled) Compact Disc (CD) which be having all your .cpp and .h files, a Readme file along-with the input text file (the file to be compressed) and the output text file (the compressed file). Readme file must be having your group name, group members name and any other info that is needed to run your program properly. Deadline will not be extended this time as well, and I expect you to fully utilize your time right from the first day. The Project constitutes 12 absolute marks which will be distributed among proper working Code, Project Report, Presentation and Viva (individual). A proper formatted Project Report (black and white form) must also be presented while submitting your project, which should fulfill proper guidelines that will be conveyed in the coming classes.
  • 2. Coding Requirements (these carry credit): 1. You have to use modular programming style. 2. Write meaningful comments. Do not litter you code with comments only when they are needed they should be there. 3. If your code does not compile you won¡¯t get any credit. 4. Only correct working gives 80% credit; if your program does not work, code review would only give 20% (these are after we have made other deductions). ? Best of Luck..!! ?