Information Sheet for CS 2213 Advanced Programming

Fall 2000

Instructor: Dr. Steven Robbins
Office: 3.02.01A SB
Phone: 458-5544
Address: srobbins@cs.utsa.edu
Course Homepage: /classes/cs2213f2000/
Office Hours: TTH 12:30 - 1:15 p.m. and by appointment
Class Times: TTH 11:00 a.m. - 12:30 p.m. in room 2.01.30 HSS

Text:

  • The C Programming Language by Brian W. Kernighan and Dennis M. Ritchie, second edition

    Prerequisites: CS 1721 and CS 1723

  • It is expected that you can program in Java and that you are familiar with basic data structures such as arrays, stacks, queues, linked lists, and trees.

    Course Objectives:

  • To become a 3-star C programmer
  • To become familiar with using the Unix operating system
  • To understand how program data is stored and to manipulate it safely
  • To solidify your understanding of basic data structures and to become familiar with new ones.

    Course Content:

  • We will cover almost all of the material in the textbook.
  • We will be using our SUN workstation laboratory in room 3.02.04SB.
  • All assignments must be done using the equipment in this lab. If you have a Unix system at home, you can do the assignments at home first and then transfer them to our system.

    Grading:

  • 10% Lab Assignments
  • 30% Midterm Exams (at least 2)
  • 30% Programming Assignments
  • 30% Final Exam (Tuesday, December 12, 10:30 a.m. - 1:15 p.m.)
  • You must successfully complete at least 70% of the lab assignments to pass the course.

    Notification of final grades:
    If you wish to receive your final grades by email, send me an email message some time after the last class and before the final. The message should have the subject line
    CS 2213 Grade Request
    and the message should have a valid return address. After I have graded the final exam and determined the letter grades for the course I will reply to your email message.

    Course Policy:
    Friday, October 27, is the last day to drop this course. No make-up exams will be given except for university sanctioned excused absences. If you must miss an exam (for a good reason), it is your responsibility to contact me before the exam. Leave a message at the above number or send me email.

    Unless otherwise stated, all programming assignments are due at the beginning of class on the due date. There will be a 10 percent penalty for programming assignments turned in after that time. Do not miss class to finish an assignment. Turn in what you have for partial credit. Programming assignments which are more than 12 hours late will not be accepted unless prior arrangements have been made.

    You must keep copies of the source code for all assignments for this course at least until you receive the your final grade for the course. At any time during the semester you may be asked to demonstrate any one of your programs.

    Note that there are two types of assignments in this course. The lab assignments are typically short and require you to learn or demonstrate specific knowledge. The programming assignments are more demanding and are a major part of the course grade. They ask you to demonstrate that you have mastered a particular aspect of the course material.

    You may get as much help on the lab assignments as you need, but the more you do on your own, the more you will learn. The purpose of these assignments is to keep you active in the course and to give you skills you will need to understand the course material.

    You are to do the programming assignments without collaboration. You can ask me questions about any aspect of an assignment. General discussion with others on the system or on an approach to a problem is constructive and is okay. However, since your grade is based on your assignments, they must be your own work. Students who hand in programs or written assignments which are identical or nearly identical are cheating. This type of scholastic dishonesty usually results in immediate failure in the course and can lead to additional disciplinary action.