Syllabus
Course Description
This course is an introduction to the C++ programming language and its subset, the C programming language. Program structure, blocks, storage types, console and file I/O, functions, arrays, strings, pointers, call-by-reference, call-by-value, and dynamic memory allocation will be discussed. The concept of classes will be introduced. The differences between C++ and C will also be discussed.
Prerequisites
CIS 1033 - Pascal Programming or Departmental approval.
Course Objectives
1. Discuss the differences between C++ and C.
2. Design, code, debug, test, and document a program using a professional programming style.
3. Write elementary to intermediate level programs using C++.
Instructional Materials
Textbook: Programming and Problem Solving with C++; Dale, Headington, Weems; Jones and Bartlett Publishers.
Web Site: Web pages for this course are located at: www.austin.cc.tx.us/comer/cis2003/
You will need access to the Web to periodically check for updates to course information. A log of these changes will be posted on the course home page. It is your responsibility to check for any new information or changes to the course.
Software: You must have access to a computer with a C++ compiler.
Recommended: An electronic mail account for communication with the instructor and classmates.
Course Requirements
Class progress: This is a self-paced course and students are expected to keep up with the schedule of the class. In this course, each new concept builds on previous concepts so that regular progress through the material is crucial to success on tests and assignments.
Withdrawal: A student who does not participate and does not officially drop the course will be given an F for the course. THE INSTRUCTOR WILL NOT AUTOMATICALLY WITHDRAW STUDENTS FROM THIS COURSE! The last date for withdrawal for this course is July 10, 1998.
Incomplete: A grade of Incomplete will not be given a student unless there is sufficient justification. An Incomplete is rarely to the advantage of the student since most Incomplete grades are not completed successfully. The instructor encourages students to avoid situations requiring Incomplete Grades if at all possible. A student who is not current in the course will not be considered for an Incomplete grade.
Participation: Even though there are no required classes, students are expected to participate by asking questions using e-mail to the instructor or classmates using the class Listserve. Students are encouraged to ask questions either privately to the instructor or to the entire class. There are no "dumb" questions! The instructor knows that the material is difficult to grasp at times and will be glad to give additional examples or one to one assistance when asked.
Grade Policy
The course grade will be based on two semester exams, a final exam, and 6 programming assignments.
|
|
|
A = 90-100 % |
|
6 programs @ 6 % each |
36 % |
B = 80-89.9 % |
|
2 semester exams @ 21 % each |
42 % |
C = 70-79.9 % |
|
Final Exam |
22 % |
D = 60-69.9 % |
|
|
100 % |
F = Below 60 % |
Students must score 60 % or more and complete 4 programs to pass the course.
Programming Assignments
Success in this course depends on the ability to successfully complete the assigned homework. Students are expected to do the assignments, which are designed to provide experience and practice with the concepts and techniques covered in the course.
Submitting Assignments: All assignments will be turned in by e-mail (copy the source code and paste it into the message - DO NOT USE THE ATTACHMENT FEATURE) sent to my teaching assistant Rob Wheeler (wheels@austin.cc.tx.us) or on a 3.5" PC-type disk in my mail slot in room 9141 at the Riverside Campus.
Deadlines: Programming assignment due dates will be posted on the Course Schedule. See my policy for late programs below. In addition, Programs 1 - 5 will not be accepted after July 18, 1998. Program 6 will not be accepted after July 24, 1998. For emergency situations only, see section above on Incomplete grades.
Assignment Grading: Assignments will be graded on the following basis:
Program documentation involves the proper variable names, indention, comments, etc. These conventions are described in the textbook. I will post a summary of these guidelines on my web page. It is very important to make the programs as readable as possible and the instructor will strictly enforce the documentation guidelines for this course.
Please contact me if you have questions about the assignment expectations or grading process.
Exams
Each of the exams covers several chapters in the textbook. Each chapter/exam builds on the previous chapter therefore the second and third tests will focus on material not covered in the previous exam. If a mistake is made on the second or third exam, which relates to material previously covered, points will be deducted.
The exams will cover the following chapters:
All exams will be administered at an ACC Testing Center. Testing facilities are located at all major campuses and are open throughout the week. Check the current schedule for the testing facility you wish to use. Please allow at least one and a half hours for the exam.
You may bring up to 3 pages (8.5 x 11" maximum) of notes for each exam and the notes will be attached to the test and sent to the instructor (so make a copy). Exams will be graded and students will be notified by email of the items that were missed and the grade received. A student wishing to view and discuss the test with the instructor may do so by scheduling an appointment with the instructor.
Exams are not returned to the student.
Deadlines: I will post due dates for exams on the Course Schedule. See my policy for late exams below. In addition, Exams one and two will not be accepted after July 18, 1998. Exam 3 will be available at all ACC Testing Centers through July 22, 1998. For emergency situations only, exam 3 may be taken at the Riverside Testing Center through July 24, 1998. Otherwise, see section above on Incomplete grades.
Late Policy for Exams and Programming Assignments
There is a one week grace period for programs and a two week grace period for exams. During the grace period exams or programs will still be accepted for full credit. After the grace period, a 10% penalty will be deducted for each additional week the exam or program is late For example, a program due on 5/30 can still be turned in up to a week later (6/06) for full credit. If turned in more than 1 week late, the maximun credit is 90%; more than 2 weeks late counts a maximum of 80%; etc. . Important: all exams and programming assignments are subject to the absolute deadlines posted above.