COP 3330
Object Oriented Programming in C++
Spring 2012 Syllabus
Instructor Information
| Position |
Name |
E-mail |
Office |
Office hours |
| Course Instructor |
Bob Myers |
myers@cs.fsu.edu |
Love 261 |
Tues/Thurs 2:30 - 3:15 PM, Wed 1:00 - 2:30 PM |
| TA |
Sean Rose |
rose@cs.fsu.edu |
MCH 114 |
M 12:50 - 2:20 PM, W 10:00 - 11:30 AM |
| TA |
Nigel Nye |
nye@cs.fsu.edu |
MCH 102-A |
Mon 3:00 - 4:00 PM, TR 11:30-12:30 |
| TA |
Heidy Khlaaf |
khlaaf@cs.fsu.edu |
LOV 172 |
W 3:30 - 5:00 PM, F 10:00 - 11:30 AM |
Class Schedule
Lecture
| Sections |
Room |
Time |
| 1 - 4 |
HCB 316 |
Tues/Thurs 3:35 - 4:50 PM |
| 5 - 6 |
LOV 103 |
Tues/Thurs 12:30 - 1:45 PM |
Recitation
| Section |
Room |
Day |
Time |
Instructor |
| 1 |
MCH 315A |
Mon |
11:15 AM - 12:05 PM |
Nye |
| 2 |
MCH 315A |
Tues |
12:30 - 1:45 PM |
Nye |
| 3 |
MCH 315A |
Wed |
2:30 - 3:20 PM |
Rose |
| 4 |
MCH 315A |
Fri |
9:05 - 9:55 AM |
Khlaaf |
| 5 |
MCH 315A |
Mon |
2:30 - 3:20 PM |
Rose |
| 6 |
MCH 315A |
Wed |
12:20 - 1:10 PM |
Khlaaf |
Course Requirements:
Prerequisite Course
- A C- or better in COP 3014, or an equivalent introductory programming
course
Course Website:
Textbooks:
- Absolute C++, 4th ed., Walter Savitch., Addison-Wesley
Course Objectives:
Upon completion of the course, the student will:
-
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
- Demonstrate the use of arrays and pointers in the solution of
programming problems using C++
-
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.
Grading Policy:
The final course grade will be computed as follows:
| Programs / Assignments |
30 % |
| Test 1 |
20 % |
| Test 2 |
20 % |
| Final Exam |
30 % |
In addition to the scale listed above, in order to earn a C- or better
in the course, 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. The test average can be computed with
the following formula:
TestAvg = ((Test1 * 20) + (Test2 * 20) + (FinalExam *
30)) / 70
Letter Grade Scale:
| 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 |
Tests:
There will be three tests -- two term tests and a final exam.
On-campus students will be required to bring and show your Student ID on
test days. The final exam will be cumulative.
Test Dates: (Test 1 and 2 tentative)
| Test 1 |
Thurs, Feb 9 |
| Test 2 |
Thurs, March 22 |
| Final Exam |
Sections 1-4: Fri, Apr 27, 3:00 - 5:00 PM
Sections 5-6: Tues, Apr 24, 10:00 AM - 12:00 noon |
Link to Spring 2012 Final Exam Schedule
Recitation / Quizzes
Periodic quizzes may be given, in lecture or in recitation class, to help
students gauge their progress in the class, and to gauge attendance, if
needed. No makeup quizzes will be given (no exceptions). Attendance and
participation is expected, both in lecture and recitation class. There
may also be some hand-in exercises done in recitation class. Any
attendance grades, quiz grades, or graded work from recitation will
count in the assignment average.
- Excused absences include documented illness, deaths in the family
and other documented crises, call to active military duty or jury duty,
religious holy days, and official University activities. These absences
will be accommodated in a way that does not arbitrarily penalize students
who have a valid excuse. Consideration will also be given to students
whose dependent children experience serious illness.
Programming Assignments
- There will be a variety of homeworks and programming projects
assigned. Some will be small and easy to complete in one sitting.
Others
will be larger programming projects. Assignment specifications will be
posted on the web page.
- Turn in all assignments on time! Late assignments
will be accepted one day after the due date, with the deduction of a
letter grade (10%). Assignments more than a day late will not be
accepted.
- Compiling -- Programs that do not compile are very tedious to
grade, and they show a lack of testing, which is a large part of
programming. There will be an automatic 5% point penalty for each compile
error in a student's code that has to be fixed in the grading process.
(This means that program submissions with compile errors will likely earn
very little, if any, credit). Make sure your code compiles before you
submit it!!!
Web References:
The course web page is your friend -- check it frequently! It will be
continually updated with essential course materials, such as assignments,
examples, and notes outlines. It will also include other helpful
supplements, such as instructions for using the compilers, a FAQ
(Frequently Asked Questions) page, suggested exercises, and other useful
help materials. It is your responsibility to check the web page often for
posted materials.
Miscellaneous Policies:
- A student will be allowed to make up a missed test if he or she has
a notice of illness from the Student Heath Center or family physician.
Any other excuses that are not medical or emergency related will be at
the discretion of the instructor, and must be approved in advance.
- Students in the class should have a computer account from the Computer
Science Department (sign up for one if you don't already have one), and
this can and should be used to store project files and access one of the
compilers used in the course.
- Please turn OFF all cellular phones, beepers, etc. in the classroom.
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.)
In addition to this information, please be aware of the
following:
- Students are expected to do their own work on any classwork or
test submitted for a grade (unless designated as a group assignment).
- It is NOT appropriate to work on assignments with other students or
to give or receive solutions to or from anyone before an assignment
is due and handed in (by all parties).
- Discussing solutions and techniques on assignments with other
students after the assignment has been graded and handed back
is okay, and encouraged.
- When you turn in work with your name on it, you are representing that
work as your own. If your submission matches that of
another student, this is considered a violation of the
Academic Honor Code.
- If a group project is given, then names of all group
members would appear on the single program submission. This is
appropriate
- Examples found in the course textbook
may be used in programs, as long as the source is cited. This is
appropriate, as some hand-in assignments may be based on program examples
found in the book or contain other code that is provided to you in the
assignment specification
- A first violation of the honor code will result, at minimum
(but not limited to), a penalty of a 0 grade on the assignment
or test involved, along with a reduced letter grade in the course.
- Any second violation of the honor code will result in an automatic F
in the course, and possible proceedings before the Honor Court.
Americans With Disabilities Act
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)
sdrc@admin.fsu.edu
http://www.disabilitycenter.fsu.edu/
Students approved to take exams at the SDRC office are expected to
take exams at the regularly scheduled time. Any exception to this
will only be granted with a valid documented reason and must be approved
by the instructor a week before the exam.
Syllabus Changes
Except for changes that substantially affect implementation of
the evaluation (grading) statement, this syllabus is a guide for
the course and is subject to change with advance notice.