Official TCC Course Syllabus (CSC201)
Discipline Prefix: CSC / Course Number: 201 / Course Title: Computer Science ICourse Section: D02B
Credit Hours: 4 / Lecture Hours: 4 / Clinical Hours: NA / Lab Hours: NA
Contact Hours: 4 / Studio Hours: NA / Semester: Fall 2016
Meeting Times: Wed 1:30 PM – 5:00 PM
Meeting Location: Virginia Beach Campus, Uboe-E137
Instructor Information
Name: Chuck Cartledge Email (Best way to contact):
Office Location: Virtual office Phone: (757) 633-2581
Office Hours: Mon – Fri: 4 – 5 PM Blackboard site: http://learn.vccs.edu
Google Hangout
Course Information
Course Description
Introduces algorithm and problem solving methods. Emphasizes structured program concepts, elementary data structures and the study and use of a high level programming language.Prerequisites and/or Co-requisites:
Prerequisites – CSC110
Corequisites – None
General Education Core Competencies Supported by this Course
After completion of this course, students will be able to:
· Quantitative Reasoning
A person who is competent in quantitative reasoning possesses the skills and knowledge necessary to apply the use of logic, numbers, and mathematics to deal effectively with common problems and issues. A person who is quantitatively literate can use numerical, geometric, and measurement data and concepts, mathematical skills, and principles of mathematical reasoning to draw logical conclusions and to make well-reasoned decisions.
Required Course Texts and Supplementary Materials
Text
· Programming and Problem Solving with C++, Comprehensive 6th Edition, by Jones & Bartlett Publishers, ISBN 978-1-284-02876-8
Other Materials
· It is also desirable to bring a flash drive to class to transfer work from home to school or vice versa (Or, be prepared to use Google Drive, OneDrive, Dropbox, etc…)
· C++ IDE – We will be using Code::Blocks in class, but you may use any IDE outside of class. (Code::Blocks and Dev-C++ are available on the lab machines in the ATC Bldg.)
Course Learning Outcomes
After completion of this course, students will be able to:
· Write syntactically correct C++ statements
· Identify and correct syntactically incorrect C++ statements
· Write structured C++ code using the major control structures available in the C++ language.
· Analyze C++ code and identify the actual (as opposed to intended) effect of the code
· Identify situations requiring the use of Arrays (homogeneous complex data structures)
· Write efficient code to process data using Arrays
· Identify situations requiring the use of Pointers
· Write efficient code to process data involving Pointers
· Identify situations requiring the use of Records (heterogeneous, complex data structures)
· Write efficient code to process data using Records
· Design and implement solutions to problems of substantial complexity using the C++ programming language (interpreted to mean writing a working program of between 500 and 2000 lines of working code), using structured design methods, functional decomposition and no global variables
Topics Covered in the Course
· C++ Syntax and Semantics
· Numeric Types, Expressions
· Console and File IO
· Conditions and Logical Expressions
· Functions, Return Values, Value and Reference Parameters
· Scope and Lifetime
· Simple and Complex Data Types
· Introduction to Array-Based algorithms
· Pointers and an Introduction to Pointer Based Structures
Description of Assignments/Assessments
Exercises: Written homework assignments will be given for each chapter. Most homework assignments will be graded mainly, but not exclusively, on a “best effort” scale. Grades for completed assignments will also be posted in the Gradebook in Blackboard along with comments. In addition, there will be review “quizzes” posted for most topics. These are mostly self-grading and will give you additional practice in working with the concepts covered in the course.
Computer Programs: One of the objectives of this course will be to learn about writing computer programs using the C++ programming language. A number of programs will be assigned. Students will need to design, code, debug and run these programs. After successfully completing a programming assignment, the student will turn in a copy of the source code used for the program. This source code will be submitted in a text file (either .txt or .cpp), generally developed using the programming environment presented in class. The programs that are submitted should be correct, compilable programs. They should not, for example, be Word documents. And they should not contain programming errors. Programs submitted with errors or in an improper document format will result in a significantly reduced score.
A significant part of the programming process is to write comments in the code that provide important information to an individual reading the code. The complete requirements for this type of documentation will be provided in class. At a minimum, however, it should include (1) the name of the program, (2) the name of the programmer, (3) the date of the program, and (4) a brief description of the purpose of the program. Failure to include appropriate documentation will result in a penalty of at least one letter grade.
As indicated in the grading scale (see below), students are required to score an average of at least 70% over all programs in order to pass the course.
Exams: There will be up to five hourly exams and a comprehensive final exam. All exams will be given in class and closed book. However, students will be allowed to bring one page of notes (8 ½ X 11, double-sided) to the hourly exams and three pages of notes (8 ½ X 11, double-sided) to the final exam.
In the event that more than three hourly exams are given, the lowest test grade will be dropped. No makeups will be given. If an exam is missed, the final exam score will be used to replace that score. (A second missed exam will receive a zero.) Hourly tests will generally pertain to specific chapters or sections; the final exam will be comprehensive.
The final exam must be taken to pass the course. Students with an "A" grade will not be excused from the final exam. A makeup test may be given for the final exam if there are documented extenuating circumstances as to why the final cannot be taken at the scheduled time. Such a makeup will likely be more difficult than the regularly scheduled final exam. Not knowing the time of the final because of lack of class attendance will not be accepted as an excuse.
Cheating on an exam will result in a grade of “0” for that exam. A zero on the final exam or more than one instance of cheating on any exam or assignment will result in failure for the course. (See Academic Integrity statement below.)
Exam dates will be posted in Blackboard announcements. Grades for your exams will also be posted on Blackboard.
Course Schedule (Tentative)
The following course schedule may change due to the progression of the course. The course schedule may change at the discretion of the instructor; however, students will be notified in writing when any changes/additions are made to the schedule. The official schedule will be maintained on Blackboard for the duration of the course. Note: Topics marked “Review” were covered in CSC110 and will be reviewed and covered in more depth here.
/ Week of (Date): / Topic(s) / Reading / Projected Program Due Dates /1 / 8/22 / · Introduction/Syllabus
· Programming and Problem Solving
· C++ Syntax and Semantics (Review) / · Chapter 1
· Chapter 2
2 / 8/29 / · Numeric Types, Expressions, and Output (Review)
· Program Input and the Software Design Process (Review) / · Chapter 3
· Chapter 4
3 / 9/5 / · Conditions, Logical Expressions, and Selection Control Structures (Review) / · Chapter 5
· Program #1 Due
4 / 9/12 / · Exam #1 (Chapters 1 - 5)
· Looping (Review) / · Chapters 1 - 5
· Chapter 6
5 / 9/19 / · Additional Control Structures (Review) / · Chapter 7
· Program #2 Due
6 / 9/26 / · Functions (Review) / · Chapter 8
7 / 10/3 / · Scope, Lifetime, and More on Functions (Review) / · Chapter 9
· Program #3 Due
8 / 10/10 / · Exam #2 (Chapters 6 - 9)
· User-Defined Data Types / · Chapters 6 - 9
· Chapter 10
9 / 10/17 / · User-Defined Data Types / · Chapter 10
· Program #4 Due
10 / 10/24 / · October 27th: Last day to withdraw without academic penalty
· Arrays (Review) / · Chapter 11
11 / 10/31 / · Arrays and Structures Continued / · Chapters 10 & 11
12 / 11/7 / · Exam #3 (Chapters 10 & 11)
· Dynamic Data and Linked Lists / · Chapter 14
· Program #5 Due
13 / 11/14 / · Dynamic Data and Linked Lists / · Chapter 14
11/21 / · Thanksgiving break, college closes noon 11/23
14 / 11/28 / · Recursion / · Chapter 18
· Program #6 Due
15 / 12/5 / · Recursion
· Exam #4, Chapters 14 & 18 --- 12/7
· Review / · Chapter 18
16 / 12/12 / · Comprehensive Final Exam (Minus Chapters 14 & 18) --- 12/14
Blackboard and Course Communication
It is recommended that students check in to Blackboard several times a week to read announcements, and to check for new assignments. Additional communications outside of class will be conducted via email and/or phone. The best way to communicate with the instructor will be via email. You may expect a response within 24 – 48 hours Monday thru Friday, and 48 – 72 hours on weekends and holidays.
In addition to remote communications, students are expected to attend class and to ask questions concerning topics covered in the course, in class. If you do not maintain consistent participation/attendance, you will be dropped from the class. I also will maintain regular office hours, during which students are welcome to come and see me to get help and ask questions. And finally, if the need arises, I will be happy to schedule an appointment to meet with a student who needs help. (See office hours above and posted on Blackboard.)
Course Policies
1. Attendance Policy
All students are expected to be present and on time at all scheduled class and laboratory meetings. Instructors are not required to admit a student who arrives late to the classroom. A student who adds a class or registers after the first day of classes is counted absent from all class meetings missed.
If a student is absent more than 15 percent of scheduled instructional time, attendance may be defined as unsatisfactory. This calculation includes absences occurring during the add/drop period. See also the Withdrawal Policy in this syllabus for more information. Per the college’s attendance policy, faculty has the right to develop a more stringent policy as well. Students who do not attend or participate in class by the deadline to drop for tuition refund will be deleted from the course.
2. Late Work/Make-up Exam Policy
In general, the due date of an assignment is to be understood as the applicable deadline by which a submitted work is guaranteed to be graded. After that deadline, students submit their work at their own peril. Work may be submitted late subject to a 10% per day penalty. (Assignments where the answers are given in class and/or Blackboard are exempt from this policy and will not be accepted late.)
No makeup exams will be given. If an exam is missed, the final exam score will be used to replace that score. (A second missed exam will receive a zero.)
3. Statement on Classroom Behavior
TCC is committed to maintaining a social and physical environment conducive to carrying out its education mission. Therefore, all members of the TCC community are expected to demonstrate standards for civility:
· Be moderate in speaking. Loud, obscene, argumentative, or threatening speech is disruptive to teaching and learning and is offensive to others. It has no place in an academic setting. (This standard applies to any class-related communications that occur over the semester and is not limited to oral communications.)
· Resolve any disagreements in a positive, non-combative manner. Request the assistance of college authorities if needed.
· Show respect for the comfort of others in an educational setting by observing acceptable standards for personal cleanliness and dress. (not applicable online)
4. Electronic Devices Policy
Cell phones, pagers, and other communication devices are prohibited from use in classrooms, laboratories, and libraries, unless authorized by the appropriate faculty or staff. Although soundless communication devices such as cell phones and pagers are permissible in classrooms, college offices, and/or meeting rooms, they must not be answered during class.
5. Inclement Weather/Emergent Hazardous Conditions
Tidewater Community College uses TCC Alerts to immediately contact and inform faculty, staff and students of a major crisis or emergency. TCC Alerts delivers important emergency alerts, notifications, and updates via:
· Email account (work, home, other)
· Cell phone
· Pager
· Smartphone/PDA (BlackBerry, Treo & other handhelds)
When an incident or emergency occurs, authorized senders will be instantly notified via TCC Alerts. TCC Alerts is a personal connection to real-time updates, instructions on where to go, what to do, or what not to do, who to contact, and other important information. New users may also register by sending a text message to 411912 keyword: TIDEWATER. To cancel the service, text TIDEWATER STOP to 411911.
In the event that of delay or cancellation you should check Blackboard for any course specific information. If the college has a delayed opening that overlaps with class time, class will not be held.
6. Disposition of Classes for Emergency Shutdown of the College:
In the event of an emergency shutdown of the college, the president and the executive staff may elect to conclude the term in session if eighty-five percent or more of that term has been completed. If the term in session is concluded, faculty shall compute final grades of students based on coursework completed at that point.
Grade Policy
ProgramsNote: Average score of all programs must be at least 70% to pass the class. / 25% / Grading Scale:
90 – 100 / A
Exercises/Assignments / 20% / 80 – 89 / B
Hourly exams / 35% / 70 – 79 / C
Final exam / 20% / 65 – 69 / D
< 65 / F
The Final exam will be a comprehensive. At the discretion of the instructor, if a student has demonstrated reasonable effort throughout the semester, and the final exam demonstrates significant mastery of the material, the weight of the final exam may be increased on a case by case basis in favor of that student’s grade. Note however, that students must average at least 70% on the programming assignments to pass the course.