Instructor Information:

Position	Name	E-mail	Office	Office hours
Course Instructor	Matthew Small	small@cs.fsu.edu	LOV 167	Tues 5-6 PM, Thurs 2-3 PM
Teaching Assistant	Mark Stanovich	stanovic@cs.fsu.edu	LOV 207	Wed 5-6:30pm, By Appt.
Teaching Assistant	Fernando Sanchez	sanchez@cs.fsu.edu	LOV 203F	By Appt.

Class Schedule and General Information:

• Lecture Times

     Tues/Thurs 3:35 - 4:50 PM, HCB 0310

• Recitation Times

Section	Room	Day	Time	Instructor
1	MCH 315A	Monday	12:30 - 1:45 PM	Sanchez
2	MCH 315A	Monday	3:35 - 4:50 PM	Sanchez
3	MCH 315A	Wednesday	3:35 - 4:50 PM	Stanovich


*Recitiation attendance is not mandatory. No new material will be introduced but it will
  provide students with a period of time to get extra help on programming excercises
  and projects.

• Course Website

     http://ww2.cs.fsu.edu/~small/cop3330 (may change)

• Prerequisite Course

     You must have earned a C- or better in COP 3014, or an equivalent introductory programming course. If you have doubts
     whether you satisfy the course pre-requisite, please contact the instructor.

• Textbook (non-required):

     Absolute C++, 3rd ed., Walter Savitch., Addison-Wesley
     ISBN: 0321468937

Course Objectives:

• Understand the Object Oriented Programming concept and be able to discuss the differences between procedural and object oriented languages.
• Demonstrate the ability to create and use classes within the C++ programming language
• Demonstrate the ability to create, compile, and execute programs in multiple compiler environments (typically Microsoft Visual C++ and the GNU g++ compiler in unix) using the Object-Oriented design model.
• Be able to build C++ classes using appropriate encapsulation and design principles
• Be able to program using important C++ techniques, such as composition of objects, operator overloads, dynamic memory allocation, inheritance and polymorphism, file I/O, exception handling, templates, bitwise operations, preprocessor directives, and basic data structures.

Coursework and Point Distribution:

• Weekly Programming Exercises (30%):

A programming exercise will be assigned every Thursday in lecture and be due the following Thursday at 11:59pm. The programming exercises are expected to take no more than 2 hours of work and students will often be provided with a general (non-code) solution/approach in lecture. The exercises are graded all or nothing but will be submitted through an autograding system where students can test their solution before final submission. There will be a style deduction on solutions that are messy, incomprehensible or ineffecient (more on this in future lecture).


• 4-5 Programming Projects (30%):

Programming projects will be assigned throughout the semester to test students ability to generate their own solution to larger programming problems. Students will generally have 2-3 weeks to complete a programming project.


• Midterm Exam (15%) - Date June 21


• Cumulative Final Exam (25%) - Date TBA

Final letter grades:

In order to obtain a course grade of C- or better, a student is required to achieve a test average of C- or better. If the test average is below this level, the highest possible course grade is a D.

Letter	Numerical Average
A	92.00 - 100
A-	90.00 - 91.99
B+	88.00 - 89.99
B	82.00 - 87.99
B-	80.00 - 81.99
C+	78.00 - 79.99
C	72.00 - 77.99
C-	69.00 - 71.99
D	62.00 - 68.99
D-	60.00 - 61.99
F	0.00 - 59.99

Course Policies:

Attendance Policy:

The university requires attendance in all classes, and it is also important to your learning. The attendance record may be provided to deans who request it. If your grade is just a little below the cutoff for a higher grade, your attendance will be one of the factors that we consider, in deciding whether to "bump" you up to the higher grade. Missing three or fewer lectures will be considered good attendance. In rare cases, such as medical needs or jury duty, absences may be excused with appropriate documentation. You should let me know in advance, when possible, and submit the documentation I seek. You should make up for any materials missed due to absences.

NOTE: recitation attendance is NOT required although it is highly recommended.

Missed exam Policy:

A missed exam will be recorded as a grade of zero. We will follow the university rules regarding missed final exams (see http://registrar.fsu.edu/dir%5Fclass/spring/exam_schedule.htm), for all the exams, including the final exam.

Late Assignment Policy:

In order to enable us to provide timely solutions to assignments, we have the following policy regarding submission of late assignments.

• An assignment that is turned in no more than 24 hours late will be scored with a 10% penalty.
• An assignment that is turned in more than 24 and no less than 48 hours late will be scored with a 20% penalty.
• An assignment that is turned in more than 48 hours late will receive the score of zero, though we will review it and comment on it.

Incomplete Grade (Grade of 'I') Policy:

The grade of 'I' will be assigned only under the following exceptional circumstances:

• The final exam is missed with an accepted excuse for the absence. In this case, the final exam must be made up during the first two weeks of the following semester.

ACADEMIC HONOR POLICY:
The Florida State University Academic Honor Policy outlines the University's expectations for the integrity of students' academic work, the procedures for resolving alleged violations of those expectations, and the rights and responsibilities of students and faculty members throughout the process.  Students are responsible for reading the Academic Honor Policy and for living up to their pledge to . . . be honest and truthful and . . . [to] strive for personal and institutional integrity at Florida State University.  (Florida State University Academic Honor Policy, found at http://dof.fsu.edu/honorpolicy.htm.)

AMERICANS WITH DISABILITIES ACT (ADA):

Students with disabilities needing academic accommodation should:
(1) register with and provide documentation to the Student Disability Resource Center; and
(2) bring a letter to the instructor indicating the need for accommodation and what type.  This should be done during the first week of class.

This syllabus and other class materials are available in alternative format upon request.

For more information about services available to FSU students with disabilities, contact the:

Student Disability Resource Center
874 Traditions Way
108 Student Services Building
Florida State University
Tallahassee, FL 32306-4167
(850) 644-9566 (voice)
(850) 644-8504 (TDD)
(850) 644-7164
sdrc@admin.fsu.edu
http://www.disabilitycenter.fsu.edu/

Academic Integrity:

Remember that the goal of programming assignments and homework is to enhance your analysis, reasoning, and programming skills. Indulging in academic dishonesty defeats this purpose apart from being unfair to other students. In case you have any questions about whether an act of collaboration may be construed as academic dishonesty, please clarify the issue with the instructor before you collaborate.

All students should follow FSU Academic Honor Code. You might be assigned a grade of 'F', if you are found to have indulged in academic dishonesty.

• It is understandable that discussing a problem with other people may lead to more insight into the issues involved. Thus discussing a problem in assignments/homeworks with other people is fine. However, discussing the solutions to the problem is NOT acceptable. 

• Every student must write his/her own code and homework. Showing your code or homework to members of other teams, giving it to them, or making it accessible to them (e.g., by making the files world-readable) is academic dishonesty.

• You are responsible for ensuring that your code/documentation/results are adequately protected and not accessible to other teams. Change permissions of your working directory to 0700 ('chmod 0700 <directory>).

• Consulting code/material from a textbook, or from the Internet, in order to understand specific aspects of your assignment is fine. However, copying such code/material will be considered academic dishonesty. If you borrow small parts of code/material from these sources, you must acknowledge this in your submission and additionally you must clearly understand and be able to explain the borrowed code/material.

• Plagiarism detection tools, such as Moss (A system for detecting software plagiarism), will be used in this course.

Syllabus Changes

This syllabus is a guide for the course and is subject to change with advance notice.