Course Organizer COP 3330 Object Oriented Programming in C++ Fall Semester 2010

Root View: Course Components
Syllabus jump	The course syllabus establishes course policies on grading, attendance, and exams. The syllabus should be read in detail at beginning semester.
Calendar jump	The course calendar provides a detailed temporal view of the course, including lecture coverage, assignments, and due dates. The calendar will be updated regularly.
Lectures new window	Lectures are in the form of a slide show with an accompanying narrative. (Click "Narrative on" to see the narrative. Click "Frames[Windows]" to toggle between displaying the narrative in a separate frame or a separate resizeable window.) Lectures provide a compact view of the important topics of the course, while the textbook and reading assignments provide more detail. Lecture slides and narrative will be created "on the fly" during the semester, so you should visit them regularly. Report bugs/corrections in the appropriate Blackboard discussion forum.
Assignments new window	Assignments will be released through the Calendar. You need the specific file name appended to this URL. See also Submitting Assignments (below) and Grading Assignments.
My FSU new window	The FSU/Blackboard Portal, where you will find this course. The course site is the main communication resource for the class. Here you can get help, talk to other students, retrieve your grades, and generally keep up with course news and announcements.
Textbook new window	The textbook for the course is C++ - How to Program, 7th edition, by Deitel, Prentice Hall, 2010 (ISBN 0-13-611726-0). (Students with 5th or 6th editions should be OK, but page references may be incorrect.)

Extras: Miscellaneous Resources and References
SSH new window	The version of ssh software that FSU pays for and recommends.
Unix/Emacs Hints new window	A few Unix and Emacs hints to get started
Make new window	A good tutorial on Make, from the College of Engineering, U of Hawaii.
Unix new window	Online Linux man pages, maintained in UK
C++ Style new window	A C++ coding style guide - required for this course.
FAQ new window	A growing collection of factoids and frequently asked questions, mostly harvested from discussions on BB. Topics include C++, Make, Emacs, Elm, Unix, and Spam.

Temporal View: Course Calendar
Week	Dates	Lecture Notes Chapters	Text Chapters	Assignment	Due Date
1	8/23 - 8/29	1: Introduction 2: C/C++ Basics	Review 1, 2	Activate CS Account Homework 1: Getting Started	9/3 9/19
2	8/30 - 9/5	3: C/C++ Control Flow	Review 4, 5	Homework 2: Stats	9/26
3	9/6 - 9/12	4: C/C++ Functions	Review 6
4	9/13 - 9/19	5: C/C++ Pointers	Review 7, 8	Homework 3: StatServer	10/10
5	9/20 - 9/26	6: C++ Classes 1	Review 3, Study 9
6	9/27 - 10/3	7: C++ Classes 2	Study 10, 11	Homework 4: String Objects	10/24
7	10/4 - 10/10	8: C++ Classes 3	Study 12	Project 1: Tracker	11/7
8	10/11 - 10/17	Midterm Exam: See Syllabus for policy and schedule. RQ1 released 10/1.
9	10/18 - 10/24	C++ String Objects	Study 8.10, 18.1 - 18.3, 18.10
10	10/25 - 10/31	9: C++ Classes 4	Study 13
11	11/1 - 11/7	11: I/O	Study 15, 17	Homework 5: I/O	11/14
12	11/8 - 11/14	10: C++ Templates	Study 14	Homework 6: TStats<T>	11/21
13	11/15 - 11/21	Introduction to Data Structures: See Project 2 document.	Study 20	Project 2: Stack and Queue	12/5
14	11/22 - 11/28	Happy Thanksgiving	Study 13
15	11/29 - 12/5	Review/Misc
16	12/6 - 12/10	Final Exam Week: See Syllabus for policy and schedule. RQ2 released 11/25.
Ω	12/13 - 1/1	Semester Break: Have a wonderful holiday, we hope to see you in COP 4530 next semester.

Unix Script Submission Process:

Most programming assignments will be submitted via a specific Unix script from your CS Majors account logged in to shell.cs.fsu.edu. The submission script for a particular assignment will be located in the assignment distribution directory.

Submission via script should generate two email responses:

1. When your submission is received, a receipt is sent via email. The date/time stamp of this email is the official submission time.
2. After your submission has been unpacked and placed in your portfolio, a second message is sent containing a copy of all files that were unpacked. This is a record of exactly what was received and placed in your portfolio.

After submission, be sure to check your email for these two messages. Normally these would arrive within a few seconds of submission. If you do not get both email responses, a malfunction occurred. When you do receive these confirmation emails, save them. If a problem were to arise with your files, these emails are your proof of submission.

Note that revisions may be submitted any time prior to the deadline and will automatically replace the previous submission.