Course Outline
Pre-requisites
Work Load
Homeworks and exams
Sample Programs Used in the class
References
Weekly schedule
Tips and guidelines for good programming
Academic dishonesty policy

Ramana Isukapalli's Columbia University Page

My contact information

I work at Alcatel-Lucent.

Mailing address:
67, Whippany Road
Lucent Technologies, Bell Labs Innovations
Whippany, NJ 07981

Columbia email:

Course outline

This course covers C++ from an "Object Oriented Programming" (OOP) perspective. At a high level, we will cover the concepts of classes, objects, data encapsulation, inheritance, polymorphism, etc. in C++. This will be a hands on course --- we will see many programming examples throughout the course. Homework assignments are intended to make the students familiar and confident of writing C++ programs. The aim of this course is to make students design and write C++ programs in the area of their study/research.

Pre-requisites

  • It is highly recommended that students taking this class know C programming or Java programming.
  • If not, they should be good with any other programming language and should be capable of learning C "quickly" (less than a week).

Work load

  • Four programming assignments: 60%
  • A midterm: 15%
  • A final exam: 25%

Homeworks

  • Each programming assignment is due by 9 AM the following Monday.
  • Late submission policy: I don't encourage late homeworks, but considering the issues in setting up your account, getting familiar with the compiler in a relatively short time, every student can have a total of 7 late days to submit your homeworks. That is, you can use 3 extra days for your first homework, 3 for your second and 1 for your third, etc. All the home works need to be submitted before Feb 24 .

Homeworks and exams

  • Jan 23, 9:44 PM -- HW1 is posted, due Jan 30 9 AM.
  • Jan 30, 11:18 PM -- HW2 is posted, due Feb 06, 9 AM.
  • Feb 08, 12:26 AM -- HW3 is posted, due Feb 15.
  • Feb 17, 1:14 AM -- HW4 is posted, due Feb 25.
  • Feb 13 -- Midterm.
  • Feb 25 -- Final exam.

Solutions

Sample Programs Used in the class

As requested by some students in the class, I am giving access to the sample programs that I used in the class. Please note that these programs are kept simple intentionally, to explain the concepts. Programs used in:

References

There are many textbooks available on C++; there is a lot of material available on the web. Any of these should be fine. Lecture notes will be provided prior to each lecture. In addition to these, you can use the following material:

Weekly schedule

    Date Topics Notes
    Jan 23
    • Course highlights
    • Overview of C
    • C data types, statements, expressions
    • Usage of if, else, for, while, do, etc.
    • functions and pointers.
    		 Lecture1
    Jan 30
    • Design principles of C++,
    • Class, object, data and methods
    • Constructor and destructor,
    • Data encapsulation.
         		Lecture2
    Feb 6
    • Inheritance and polymorphism
    • virtual functions, abstract classes
    • friend functions/classes
      •
    		Lecture3
    Feb 13
    • const functions
    • passing arguments by value or reference
    • Templates
         		Lecture4 Midterm
    Feb 20
    • Operator overloading
    • STL: vector, list classes, iterators.
         		Lecture5
    Feb 27 No lecture No lecture

Tips and guidelines for good programming

Here are some tips you may find useful when writing code. Please follow these when you submit your homeworks.
  • Include comments wherever you can. Make sure that your code can be easily understood by others (and you yourself, in future).
  • Use meaningful names for variables and constants.
  • If some code segmenet ( e.g., computing the outcome of some mathematical functions like factorial or exponent) has to be used in several places, it is better to have a separate function for it. In general, the same piece of code should, in general, not appear twice anywhere in your code. If you have to change it future, it is much easier to change it in one place, than in many places.
  • If a constant (like "pi") value has to be used in many places, define it as a const variable once ( e.g., const double pi) instead of using the value (3.1415..) in many places.

Academic dishonesty policy

The aim of the course is to learn C++ in a relaxed and informal atmosphere. If you have problems following the course material or doing any homeworks, please discuss with me. Go through the academic dishonesty page and please do not cheat in the homeworks or in the exams. I will be forced to follow the rules strictly if such a situation arises.
Ramana Isukapalli
Last modified: Sun Mar 9 23:35:14 EDT 2008