HOME | Overview | Syllabus | Instructor | Lectures | Laboratories | Readings | Assignments | Resources | Other Links

CS 1713 and CS 1711 Syllabus Fall 1999

Course Instructor:
       Name: Kay A. Robbins
       Office: 3.02.01C
       Phone: 458-5543
       Email: krobbins@cs.utsa.edu
       Web Page: http://vip.cs.utsa.edu/krobbins
       Office Hours: M W noon to 12:50 pm, F 10 am to 10:50 am and by appointment

Recitation Instructor:
       Name: Saivijay Gali (Vijay)
       Office: 3.02.04A
       Phone: 458-5699
       Email: sgali@cs.utsa.edu
       Web Page: http://www.cs.utsa.edu/~sgali
       Office Hours: M 11 am to noon and by appointment

Course Web Page:         http://vip.cs.utsa.edu/classes/cs1713f99/robbins

Lecture Time and Place:
        CS 1713 Section 1: MWF 9:00 - 9:50 am 3.04.06BB
        CS 1713 Section 2: MWF 1:00 - 1:50 pm 3.04.06BB
Recitation Time (Place will be announced):
        CS 1711 Section 1 (for Lecture Section 1): W 10:00-10:50 am
        CS 1711 Section 2 (for Lecture Section 2): W 2:00-2:50 am
        CS 1711 Section 4 (for Lecture Section 1): M 10:00-10:50 am
        CS 1711 Section 6 (for Lecture Section 2): M 2:00-2:50 am

Textbook and Required Materials:
        Problem Solving with Java by Elliot Koffman and Ursula Wolz
                    (http://www.awl.com/cseng/titles/0-201-35743-7/)
        Ten high density double sided 3.5" formatted floppy disks

Prerequisite:
        MAT 1093 and either CS 1063 or other some exposure to programming

Course Objectives:

Grading Policy:

Recitation (CS 1711):
The lecture (CS 1713) and the recitation (CS 1711) are considered to be two parts of the same course. The lecture and the recitation carry different numbers as an administrative convenience. You must be enrolled in a recitation section of the course that is associated with the lecture section that you are enrolled in. You will receive the same grade for both the lecture and the recitation. The recitations provide reinforcement, teach you specific skills related to topics introduced in the lectures, and help prepare you to do the individual programming projects.

You will receive grades for approximately 12 recitation exercises (laboratories). The lowest two grades will be dropped. There are no make-up laboratories. Attendance in the recitation is required in order to receive credit for the laboratory. An outline of what will be expected of you in a recitation will be posted on the class web page before the class so that you can prepare for it. When you come into the recitation, you will need to sign in and put on a name tag. You are expected to stay for the entire class even if you finish early. In case you finish early, please assist other students or work on your programming projects.

We have tried to schedule as many of the recitation class periods as we could into computer classrooms so that each student can work at a machine during the class. Unfortunately, because of the scheduling logistics, a given recitation section won't always be meeting in the same classroom. The schedule for each week will be announced in class and posted on the web site.

Individual Programming Projects:
There will be four major programming projects this semester. While you may ask for assistance in debugging, these projects are to be entirely your own work.

Group Design Project:
There will be one group design project with several intermediate milestones. You will be assigned to work in a group with (3 or 4) classmates from your recitation section. The group design project will require some written analysis. We will be discussing different group designs during the lectures.

Lecture Attendance and Make-up Exam Policy:
Attendance in the lecture is not mandatory, but is strongly recommended. You will be asked to check your name off as you enter the room prior to the beginning of the lecture. While not weighted directly in your final grade, attendance can influence borderline grades.

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, or as soon after the exam as possible. Leave a message at the above number or send me email.

Drop Date:
Friday, October 29, 1999 is the last day to drop this course.

Programming Environment:
We will be using Sun Microsystems Java WorkShop Version 3.03 along with Java version JDK 1.2.2. We have requested that the same version be installed in the Student Computing Facilities and in the computer classrooms in the Business Building. These programs are free under a community license program. If you have a suitable PC at home, we encourage you to install these programs on your machine. The programs are somewhat large to download. You may sign out a CD containing the software, provided you agree to register with Sun on the web and you return the CD at the beginning of the next class period. For instructions on downloading and using Java WorkShop see http://vip.cs.utsa.edu/classes/JavaInfo.

Email and Web Pages:
Java allows programs to be executed from web pages. As part of the course you will develop your own web page and some of your assignments will tested by your instructor via your web page.

You will be given an account on the Division of Computer Science Sun Network to use for your web page and for email. The first recitation laboratory is an orientation on constructing a web page and on using email. I will be regularly contacting you by email with information about the class. You must read your email several times a week. I will also notify you by email when new lecture outlines, laboratories, and project information are posted on the web.

Scholastic Dishonesty:
The integrity of a university degree depends on the integrity of the work done for that degree by each student. The University expects a student to maintain a high standard of individual honor in his/her scholastic work.

In this course, you may (should) work with classmates on activities designated as collaborative. You may NOT collaborate on activites specifically designated as individual. In particular, copying other people's code with minor modifications on individual projects is regarded as a serious case of cheating. You must write your own code. You may ask debugging and syntax questions of other students.


Revision Date: August 31, 1999 at 7:50 pm