Course Website:

Prerequisite Course

• All students taking COP 3363 are required to have previously taken and passed (with a C- or higher final grade) MAC 1140 or MAC 2311 or MAC 2233.
• If you have not completed this pre-requisite requirement, the CS department will most likely drop you from this course in the first week of classes. To be sure that your course schedule is correct, if you do not have the pre-req you should drop yourself from this course and then adjust your class schedule appropriately with the help of your academic advisor.

Textbooks:

• Starting Out with C++: From Control Structures through Objects, 8th ed., Tony Gaddis. This is available at the FSU bookstore, as well as online from multiple retailers. This is the only book you will need for this course. If you have a previous edition, just ensure you're reading the appropriate sections by checking with someone who has the current version (8th edition)

Course Objectives:

• After the segment on the Introduction to Unix the student should be able to:
  use the basic set of Unix commands to manipulate directories and files
  create and edit files using standard text editor
  transfer files from a laptop to the Unix server
  use the G++ compiler to compile programs
  Run programs
• Demonstrate a basic understanding of computer concepts, including software and hardware.
• Solve computing problems using a top-down approach in a well-structured design using procedural programming techniques
• Design, implement, test, and debug a C++ program to solve a given problem
• Demonstrate knowledge and use of control structures used in procedural programming, including sequence, selection, iteration, and functions.
• Make use of data types and structures in C++ including integer and floating point types, arrays (one-dimensional, two-dimensional, strings) and structs; arrays of structs and structs containing arrays. Have a introductory-level understanding of the C++ class and be able to utilize the standard IO and string classes and their member functions.
• Utilize fundamental algorithms studied to perform common tasks, such as finding the max and min of a data set, counting, summing, tracking a previous value, searching and sorting, reading until EOF, etc.
• Consider, compare, and evaluate code segments or simple algorithms for relative efficiency in a basic fashion
• Make use of pointers: understanding their relationship with arrays, their use in function parameters and returns, and their importance in dynamic memory allocation.
• Understand the basics of a c++ class and be able to use a minimal class

Grading Policy:

*** 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 * 17.5) + (Test2 * 17.5) + (FinalExam * 25)) / 60

Also: Graduate students taking the course on S/U basis must earn a B- or better in the course to earn a S for their final course grade.
NOTE: THE GRADE SHOWN IN CANVAS MAY NOT BE AN ACCURATE REPRESENTATION OF YOUR ACTUAL GRADE IN THE COURSE. ALWAYS USE THE SYLLABUS BREAKDOWN TO CALCULATE YOUR OVERALL GRADE.

Letter Grade Scale:

S/U Grading: For undergraduates, any grade A through C- will be considered an S (Satisfactory). Any grade less than a C- will be considered U (unsatisfactory). (added 3/28/2020)

Tests:

Quizzes / Attendance:

• 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. We follow FSU's excused absence policy.

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 up to 24 hours after the due date, with the deduction of a letter grade (10%). Assignments more than a day late will not be accepted. Students are not permitted to "re-do" assignments. Assignment deadlines are STRICTLY enforced.
• STUDENTS are responsible for ensuring that their program file was submitted correctly. This means making sure their file was submitted without error, ON TIME, and also submitting the correct .cpp file.
• 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). If there are more than 10 compilation errors the program receives a zero. SO... Make sure your code COMPILES before you submit it!!! Also, your programs must compile without warnings - warnings are not the same as errors (programs can still "run" even with warnings) but they are NOT acceptable and not good practice to submit programs with warnings. 3% will be taken off for EACH WARNING present in student's submitted code.

Web References:

Miscellaneous Policies:

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).
  • It is NOT appropriate to share any amount of code with your classmates
  • It is NOT appropriate to copy/paste, or use any amount of code from any web sources, fourms, etc. Our course notes, and examples in our textbook are fair game, however.
  • DO NOT POST YOUR CODE ONLINE. If I find your code online (online compilers, text sites, blogs, help sites, etc...), no matter what the intent was in posting your code, this is automatically in violation of the Academic Honor Policy and the appropriate actions will be taken. DO NOT USE online compilers, chat rooms, or post any amount of your code on the web. I'll find out, trust me.
  • 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 you have previously taken the course, you are NOT permitted to submit your old work for any assignment in the current semester. You must do your work from scratch. This is included in the FSU honor policy. See the link above.
  • If it is found that a student has violated the academic honor policy the student is not permitted to drop or withdraw from the course, and must complete the course with the sanctions accessed via the policy. This is a UNIVERSITY policy. (Added for clarification, 2/17/15)
• Examples found in the course textbook or in the course notes 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.