Spring 2000 Syllabus
CIS 2003 - Introduction to C++ and C
Open Campus Sections 4579 & 4367
Bob Comer, Associate Professor, CIS/CSC
phone: 512-223-6256 email: comer@austin.cc.tx.us web: www2.austin.cc.tx.us/comer/
Office hours and location are posted on my web page


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 - Fundamentals of 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: C++ How to Program second edition by Deitel and Deitel, Prentice Hall.

Web Site: Web pages for this course are located at: www2.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. You may also use the Computer Studies labs on any of the 5 main ACC campuses.

Recommended: An electronic mail account for communication with the instructor and classmates.


Course Requirements

Orientation: Orientation is required. Students who do not complete the orientation by the end of the first week of class may be dropped from the class.

Class progress: 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! According to the College calendar, the last day to withdraw (initiated by instructor or student) is Friday, April 21, 2000.

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: Students are expected to participate in discussions. Questions and comments of general interest should be sent to the class Listserve so that everyone can benefit from the discussion. Other questions, such as questions about your grades, should be sent directly to the instructor or teaching assistant. Students are encouraged to ask questions. 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.

Academic dishonesty: All assignments and tests submitted for this course must be the product of the student's own independent effort. The instructor expects that students will discuss programming assignments and assist each other with problems; however, copying someone else's work is not allowed. If the instructor determines that work has been copied, disciplinary action will result which could include referral to the College Dean.


Grade Policy

The course grade will be based on two semester exams, a final exam, and 7 programming assignments.

    A = 90-100 %
7 programs @ 5 % each 35 % B = 80-89.9 %
2 semester exams @ 21 % each 42 % C = 70-79.9 %
Final Exam 23 % 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: Turn in a copy of your program source code by email or on a 3.5" PC-type disk in my mail slot in room 9141 at the Riverside Campus. Email instructions: Copy the source code and paste it into the message - DO NOT USE THE ATTACHMENT FEATURE. Send the message to wheels@austin.cc.tx.us. Please include the program number in the Subject field (for example: C++ Program 2).

Deadlines: Programming assignment due dates will be posted on the Course Schedule. See my policy for late programs below. In addition, Programs 1 - 6 will not be accepted after Saturday, May 6, 2000. Program 7 will not be accepted after Friday, May 12, 2000. For emergency situations only, see the section above on Incomplete grades.

Assignment Grading: Assignments will be graded on the following basis:

Program documentation involves the proper use of 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

The material covered in each chapter of the textbook builds on material covered in previous chapters. For this reason, the second and third exams will focus on the chapters listed below, but will include material from previous exams. If a mistake is made related to material covered on a previous exam, points will still be deducted.

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. The notes will be attached to the test and sent to the instructor, so you will want to make a copy before you take the exam. 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 review 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 1 and 2 will not be accepted after Saturday, May 6, 2000. Exam 3 will be available at all ACC Testing Centers through Wednesday, May 10, 2000. Exam 3 may be taken at the Riverside Testing Center through Friday, May 12, 2000. 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 1/29 can still be turned in up to a week later (2/5) for full credit. If turned in more than 1 week late, the maximum credit is 90%; more than 2 weeks late counts a maximum of 80%; etc. Note: purpose of the grace period is to allow you some flexibility in scheduling your coursework. If you consistently complete assignments after the due date, it will be very difficult for you to complete all the coursework by the end of the semester. Important: all exams and programming assignments are subject to the absolute deadlines posted above.