CISC181-052 -- Spring 06

Introduction To Computer Science

Lecture: TR 6:00 - 7:30PM 209 Smith Hall
Lab: R 5:00PM - 5:50PM - Willard 009
Prerequisites: CISC105 OR Prior Programming Experience in another high level language (This is IMPORTANT!)
Course Project Number: 2003 What is a project number?

Instructor: Chris Fischer
E-mail: cfischer@cis.udel.edu
Office hours: Before Class and by Appointment
Web: http://www.cis.udel.edu/~cfischer/

Teaching Assistant: Sherol Chen
E-mail: schen@cis.udel.edu
Office:
Office hours:


Grades


What's new for this semester:
More coding to be done in class (past students have requested this.) More emphasis on coding style and memory management, less emphasis on Operator Overloading. New (and improved) book! Some slides will need updating.
What to expect in this course:
A lot of work. This course has to teach both the basic features of the C++ language, many of which the concepts you may know already, and the advanced features (Pointers, Operator Overloading, Classes, Inheritance, Polymorphism..) in one semester. If you're looking for a course to show up to twice a week with minimal outside work, this is not the class for you. This course moves very quickly and has a lot of outside work (labs, homeworks, 3 programming assignments, 3 tests).

You can also expect that I will provide you a LOT of resources to succeed in this course. I will provide as many outside references and sample code as I can. I will also make myself available for questions as much as possible. If possible, reach me by email, during the week. I will usually get back to you very quickly. However, I do have two rules.

  1. I am not here to debug your programs. That is a part of the assignment. Do not email me your program saying "It doesn't work, what's wrong?". This does not mean I'm not going to help you, I will, but ask specific questions, not "what's wrong with this".
  2. I get very unsympathetic to questions the night before/day of/after the project due date. They should really be done by then.  I also am unsympthetic towards people that email questions but don't come to class.
There rules are here not to make life difficult for you, but to encourage you to think the problems through on your own. If you're really stuck, of course I'm going to help you, but I don't want you to email immediately when you get to a hard problem.

Other important points:
You are strongly encouraged to come to class. While I will put some material up on the web, it will be hard to do well in this course without coming to class. Reading the relevant chapters ahead of time is also a good idea. Last semesters class convinced me to post the Powerpoints ahead of time. I'll do that again, but only if people show up regularly for class.



Course Policies:

Special Rule: Your final grade cannot be more than one letter grade higher than your exam average. This ensures that your final grade reflects your mastery of the basic concepts of the course.

Lab/Project submission: All Labs must be submitted to the TA, either in person on in their mailbox. All Projects must be personally handed to the TA - if you place it in their mailbox, you will receive a zero on it.

Homework Submission: Homeworks should be submitted to me. If the homework involves a programming assignment, it has to be done on a computer, with appropriate test runs.
All papers MUST be stapled. Unstapled papers will lose 10 points.

Coding conventions: I will go over coding conventions in the second or third lecture. Your code should generally follow it, or you will lose points. Code that can't be followed clearly by other people is far less useful (more on this later.)

Lateness: Assignments are due by the end of class on the date they are due. After that, they lose 5%/day, up to a maximum of 7 days late. Labs can be turned into my or the TA's mailbox, with the DATE and TIME of submission clearly marked on it. Any paper that doesn't have the date and time clearly marked on it on the first page (Either circled, if the printout shows a timestamp, or otherwise written) will lose 10 points.

Academic Dishonesty: DO YOUR OWN WORK. You as specifically NOT permitted to discuss solutions to problems with other students or share code.

I haven't been out of school long enough to forget how rampant cheating is. So before you think about sharing solutions, know this much going in.

  1. I am a professional Software Engineer - I stare at code all day long. I've also TA'ed this course 3 times, and this is my 6th time teaching it. So if anyone can spot copied code/cheating, it's p6obably me.
  2. The tests will have a large amount of the material that comes straight from the homeworks/projects. This will make them fairly easy for students who have completed and understood the projects on their own, and very difficult for those that haven't.
Cheating will be dealt with per University guidelines. I really don't want to waste everyone's time by doing this, but I will. Please do your own work.

Grading Policies: I'm going to grade on the standard curve (>93=A, >90=A-, >87 B+, etc.). This is guaranteed. Depending on class performance or other factors, I might adjust this scale down (to help everyone) I will never adjust it up.
Also, all your grades will be posted online (via a code name) so that you always know exactly where you are throughout the semester. Please check online and make sure all your grades are correct.

Your grade for the semester will be based on:
Tests:   50% of final grade
Projects:   25% of final grade
Labs + Homeworks   25% of final grade

Class participation can positively affect a borderline grade. 


Textbooks


Absolute C++, Savitch, ISBN: 0321330234
Just Enough Unix, 5th Edition, by Anderson,   ISBN: 0072952970

Schedule

You are expected to attend all classes, and to be prepared for each class by reviewing notes from the previous lecture and reading the scheduled reading assignments. You are responsible for all announcements and material presented during classes, whether you are present or not.
This schedule is tentative and subject to change.
Date Topics Resources Readings  What's Due
February 7 Introduction To Course Lecture 1
February 9 C++ Basics Lecture 2 Savitch Chapter 1
February 14 Coding Standards
February 16 File Processing Lecture 3 Savitch Chapter 2, Using Unix 1 Lab 1
February 21 File Processing, Start functions Lecture 4 Code Savitch Chapter 3, Using Unix 2
February 23 Return Codes, More Functions, Random Numbers Lecture 5 scope.cc random.cc Lab 2
February 28 Recursion, Functions Lecture 6 Savitch Chapter 4
March 2 Pass by Reference, Function Overloading Lab 3
March 7 Return Codes, Start Arrays Lecture 7
March 9 Review for Exam Project 1
March 14 Exam 1
March 16 More Arrays, Structs Lecture 8
March 21 Pointers Lecture 9 Code More Code
March 23 More Pointers Lecture 10 Lab 4 AND Lab 5
March 28 Spring Break!
March 30 Spring Break!
April 4 Begin Linked Lists PtrSize LinkedList
April 6 More Linked Lists Code From Class
April 11 Dynamic Memory allocation
April 13 Work on Projects Code from Class Lab 6
April 18 Linked list help/Begin Classes Lecture 12 Savitch Chapter 6
April 20 More Classes/Review for Exam 2 Project 2
April 25 Exam 2
April 27 Constructors Lecture 13 Savitch Chapter 7
May 2 this pointer, friend functions, operator overloading Lecture 14
May 4 Inheritence Lecture 17 Lab 7
May 9 Virtual Functions Lecture 18 Code from class
May 11 More Inheritence and Virtual Functions Lecture 19 Code from Class
May 16 Review for Final Project 3
Final Exam, May 24, SHL 130 Final Exam

Resources

 Professor Conrad's CISC181 Page
 C++ Reference
 C++ FAQ (Lite version)
 U. of Hawaii's VI tutorial
 VI Lover's homepage
 EMACS tutorial
 STL String Reference
 Pointer Fun With Binky (and other help with Pointers + Linked Lists)
 Sun Ray Reference / Tips ( Thanks to Professor Conrad for this )
 Sorting Algorithms (Look at Bubble and Selection - than look at one that uses better than 0(n^2) - merge or quick sort should be fine.
 Linked List Tutorial