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

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	Assignments will be released through the Calendar. See also Submitting Assignments (below) and Grading Assignments.
LIB	The course code distribution library is LIB = /home/courses/cop3330p/fall14. Note that this is NOT a URL (web page), it is the actual location of files in the Unix/Linux system.
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: Late Objects Version (7e), by Deitel, Prentice Hall, 2010 (ISBN 9780132165419). (Students with previous editions should be OK.) Page references should be correct for the 7th edition, but only approximate for other editions.
Office jump	Schedule, office hours, and contact information for Chris Lacher

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
Princeton Stanford Gnu new windows	More Emacs help info - from various sources.
Email new window	Very brief reminders on setting up and checking CS Email.
g++ new window	The gnu compiler manual, maintained by gnu itself.
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++ Code Standards 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.
C++ Libraries new window	A good reference to look up the various C++ standard libraries.

Temporal View: Course Calendar [Revised 8/31]
Week		Coverage		Deliverable
#	Dates	Lecture Notes Chapters	Text Chapters	Assignment	Quiz/Exam	Due Date
1	8/25 - 8/31	0: Introduction 1: C/C++ Basics	Review 1, 2 Stroustrup on C++11 Is Technology Destroying Jobs?	Assignment 0: Create Portfolio Homework 1.1: Unix & Emacs Homework 1.2: Unix, g++ & Make	HQ1	8/31 9/7 9/7
2	9/1 - 9/7	2: C/C++ Control Flow 3: C/C++ Functions	Review 3, 4 Review 5	Homework 2: Stats Stats.mp4   Stats.rt	HQ2	9/14 9/14
3	9/8 - 9/14	4: C++ Classes 1   Classes1.mp4   Classes1.rt 5: C/C++ Pointers   Pointers.mp4   Pointers.rt	Study 9 Review 6, 7	Homework 3: The Product Class Product.mp4   Product.rt		9/28
4	9/15 - 9/21	6: C++ Classes 2   Classes2.mp4   Classes2.rt 7: C-Strings & String Objects	Study 10, 11 Study F, 18, 22.8-10	Homework 4: UIntSet		10/5
5	9/22 - 9/28	8: Bit Vectors   BitVectors.mp4   BitVectors.rt 9: C++ Classes 3   Classes3.mp4   Classes3.rt	Study 22.4-5 Study 12
6	9/29 - 10/5	Review Notes 1-9 RQ1 available Week 6 only	Review Chapters 1 - 12, 18, 22, F	Review Homework 1 - 4	RQ1	10/5
7	10/6 - 10/12	Midterm Exam: See Syllabus for policy and schedule.				10/11
8	10/13 - 10/19	10: C++ Classes 4   Classes4.mp4   Classes4.rt	Study 13	Project 1: SunPass   SunPass.mp4   SunPass.rt   Verbose.mp4   Verbose.rt		11/2
9	10/20 - 10/26	11: I/O   IO.mp4   IO.rt	Study 8, 15, 17	Homework 5: I/O		11/16
10	10/27 - 11/2	Review: OOP, I/O (Notes Chapters 9, 10, 11)	Text Chapters 13, 15, 17
11	11/3 - 11/9	12: C++ Templates	Study 14	Homework 6: Stats Templates		11/23
12	11/10 - 11/16	13: Introduction to Data Structures   ADTs.mp4 14: Introduction to fsu::List   ADTs.rt 15: Linked List Programming	Study 20	Project 2: Data Structures		12/7
13	11/17 - 11/23	Introduction to the fsu and std libraries	Study 21
14	11/24 - 11/30	Thanksgiving Week
15	12/1 - 12/7	Review Notes 1 - 12 RQ2 available Week 15 only	Chapters 1-15, 17, 18, 20, 21	hw1 - hw6, proj1, proj2	RQ2	12/7
16	12/8 - 12/14	Final Exam Week: See Syllabus for policy and schedule.				12/13
Ω	12/15 - 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.