Spring 1999 Syllabus
CIS 1033 - Fundamentals of Programming
Section 3824 M W 9-10:50 am
Section 3825 T H 11-12:50 pm
Lecture: RVS 9116 Lab: RVS 9143
Bob Comer, Associate Professor, CIS/CSC
phone: 512-223-6256 email: comer@austin.cc.tx.us web: www.austin.cc.tx.us/comer/
Office hours and location are posted on my web page


Course Description

This course is an introduction to computer concepts, logic, and computer programming. Includes designing, coding, debugging, testing, and documenting programs using a high-level programming language.

Prerequisites

B - Reading and Math

Course Objectives

  1. Discuss and demonstrate an appreciation of the field of Computer Science from a historical point of view.
  2. Discuss the evolution of computer hardware and software technology.
  3. Discuss how data is represented in the computer.
  4. Design, code, debug, test, and document programs using a professional programming style.
  5. Write elementary programs using a high-level programming language.
  6. Discuss the differences between traditional structured programming and object-oriented programming.

Instructional Materials

Required Textbook: The Art of Programming: Computer Science with C++ by Steven C. Lawlor, 1998, PWS Publishing.

Materials: Two 3 1/2" high density floppy diskettes (IBM format) and two manilla
envelopes 8 1/2" by 11" or larger.


Course Requirements

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 16, 1999.

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 and 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: Except for assignments that are explicitly designated as group assignments, 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 three semester exams, approximately 8 programming assignments, and other in-class and homework assignments.

    A = 90-100 %
Exams (3 @ 20% each) 60 % B = 80-89.9 %
Programming assignments (equal weight) 30 % C = 70-79.9 %
Other assignments (equal weight) 10 % D = 60-69.9 %
  100 % F = Below 60 %

Students must score 60 % or more to pass the course.


Exams

The material covered in each chapter of the textbook builds on material covered in previous chapters. For this reason, exams 2 and 3 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 given in class. Make-up exams will be given for excused absences only. If you must miss an exam, please contact me as soon as possible, preferrably before the exam.

Exams will be reviewed in class. Graded exams are kept on file by the instructor. The student may review her/his exam during lab time or during the instructor's office hours by request. The examination must be returned to the instructor before leaving the lab or office.


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 Programs: Turn in (1) a printed copy of your program source code and (2) a copy of the source code file on a 3.5" PC-type disk. You may turn in programs in class or in my mail slot in room 9141. Alternatively, you may turn in programs by e-mail to comer@austin.cc.tx.us. E-mail instructions: Copy the source code and paste it into the message - DO NOT USE THE ATTACHMENT FEATURE. Please include the program number in the Subject field of the e-mail.

Deadlines: Programming assignment must be turned in by 5:00 pm on the due date. See my policy for late assignments below. In addition, only the last program will be accepted the week of final exams. All other programs must be turned in before the week of final exams.

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

All programs must follow the guidelines in the Program Documentation and Style handout. Program documentation involves the use of proper variable names, indention, comments, etc. 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 ask if you have questions about the assignment expectations or grading process.


In-class and Homework Assignments

In-class assignments will be due at the end of the lab period on the day that they are given. Homework assignments are due at 5:00 pm on the due date. See my policy for late assignments below. In addition, only the last in-class assignment and the last homework assignment will be accepted the week of final exams. All other in-class and homework assignments must be turned in before the week of final exams.


Late Policy for Assignments

All assignments will have a clearly marked due date, except for in-class assignments which are due the day they are assigned. Assignments turned in after the listed time on the due date will be assessed a 10% penalty. An additional 10% penalty will accrue each week thereafter. Exception: Programming assignments have a one week grace period. The initial 10% penalty will be assessed one week after the due date. An additional 10% penalty will accrue each week thereafter.

Assignment Type Time Due Grace Period
Homework 5:00 pm None
In-class end of lab time None
Programming 5:00 pm One week

For example, an in-class assignment must be turned in at the end of the lab period on the day assigned to earn full credit. During the first week after that, the maximum credit is 90%; during the second week, the maximum credit is 80%; etc. Important: all assignments are subject to the absolute deadlines posted above.

Please note: Absence from class is not an excuse for late assignments.