OHJ-1156 Programming II, Periods III & IV 2011-2012

General info

• In order to pass the course the student needs to turn in programming assignments implemented in the C++ programming language. There are two assignments in total.
• Each homework assignment is graded with 0-15 points.
• These points are added to the exam points and the final grade will be given based on the total.
• Homework assignments must be implemented with C++, no C.
  • The ADTs identified
  • The properties (operations and attributes) of the ADTs
  • The data representation used
  • The course topics that have been covered in the assignments

Help on homework assignments

The assignments:

• The schedule of the homework assignments:
  
• The assignments:
  
  • Available in the main page!

Submitting your program

Note! The method of turning in the assignments uses your proffa account email. The TA's feedback is also sent to this email address. If you normally use an email account outside the university, make sure you regularly check your TUT inbox or forward TUT emails to your regular inbox.

• Submit your files as a .ZIP/.RAR files or directly attaching files to the mail.
  
  Submit the source code of your program to prog2@cs.tut.fi as an attachment in an email. The name of the code file must be [student number].cc where the [student number] is your own student number, e.g. 123456.cc. The subject of the email should be HW1: [student number], e.g. HW1: 123456.
• Submit your solution BEFORE the deadline as an e-mail attachment to prog2@cs.tut.fi with:
  
  • Body: "Hi, here's my assignment."
• Overdue submissions won't be graded

Remember to check the style of your program before submitting. Instructions on how to use Style++ and what things are checked by the program are available here.

Grading the assignments

• The programs must compile without warnings with tutg++.
• The program works according to the specification. Note! also unnecessary extra features may reduce the grade
• at least 90% style grade from the style checker
• No C-code: No goto, printf etc. No global variables.
• Programs are commented properly. Each file starts with a comment stating the name and student number of the programmer and briefly describes the contents of the file
• The names of the functions and variables make sense and the program is readable.
• The program is well structured
• Classes are well defined

Academic dishonesty and other unpleasantness