CS 1713 and CS 1711 Syllabus Fall 2000

Recitation Instructor:
       Name: Rajesh Boppana
       Office: 3.02.10 SB
       Phone: 210-458-5737
       Email: brajesh@cs.utsa.edu
       Web Page: http:www.cs.utsa.edu/~brajesh
       Office Hours: MW 11:15-12:30pm T 3-5pm

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

Lecture Time and Place:
        CS 1713 Section 1: MWF 9:00 - 9:50 am 3.03.04BB
        CS 1713 Section 2: MWF 1:00 - 1:50 pm 3.03.04BB
        CS 1713 Section 3: TR 7:00 - 8:15 pm 3.03.04BB

Recitation Time (All recitations will be in 1.02.04 SB):
        CS 1711 Section 1 (for Lecture Section 1): M 10:00-10:50 am
        CS 1711 Section 2 (for Lecture Section 1): W 10:00-10:50 am
        CS 1711 Section 3 (for Lecture Section 1): F 10:00-10:50 am
        CS 1711 Section 4 (for Lecture Section 2): M 2:00-2:50 pm
        CS 1711 Section 5 (for Lecture Section 2): W 2:00-2:50 pm
        CS 1711 Section 6 (for Lecture Section 3): T 6:00-6:50 pm
        CS 1711 Section 7 (for Lecture Section 3): R 6:00-6:50 pm

Textbook and Required Materials:
        Java Software Solutions: Foundations of Program Design by John Lewis and William Loftus
                    http://jss.villanova.edu
        Ten high density double sided 3.5" formatted floppy disks
        A ring-binder with dividers for organizing lecture notes, recitations, assignments and other handouts
        Pack of 4" x 6" unlined index cards

Prerequisite:
        MAT 1093 and previous programming experience
        Note: if you have not programmed using selection (if) and loops you should sign up for CS 1063 BEFORE taking CS 1713.

Course Objectives:

• Students should be able to use object-oriented design to develop and implement computer-based solutions to problems.
• Students should be able to apply the steps necessary for software development with classes including using and extending existing classes as well as developing new classes to solve problems.
• Students should use and master the essential features of Java including control (sequential, selection, repetition, recursion and exceptions), parameter passing, arrays, vectors and strings.
• Students should learn to implement elementary search and sorting algorithms
• Students should be introduced to elements of GUI design and event-driven models of execution.
• Students should be able to create applets that can be inserted into Web pages.
• Students should gain experience both in individual program development and in group design and collaboration.

• 30% Two in-class exams
  
• 30% Final exam
  
  • Lecture Section 1: Tuesday, December 12, 2000 from 7:30 am to 10:15 am
  • Lecture Section 2: Wednesday, December 13, 2000 from 1:30 pm to 4:15 pm
  • Lecture Section 3: Thursday, December 14, 2000 from 8:00 pm to 10:45 pm
• 20% Laboratories (CS 1711 recitation)
• 20% Individual programming projects
  

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 course 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. There are no make-up recitations. However the last recitation exercise will be optional and will be used to replace a missed or low grade in one of the others. Attendance in the recitation is required in order to receive credit for the recitation. It is your responsibility to check in with the TA at each recitation session. If you have to miss a particular recitation, you may attend another session if that session can accommodate you. However in addition to checking in with the TA, you must send an email to your lecture instructor explaining the reason for attending the other section. An outline of what will be expected of you in a recitation will be posted on the class web page usually the week prior to the recitation. You are expected to read the exercise before coming to recitation and to do the section Before the Recitation. The recitations will be held in the Computer Science Teaching Laboratory (1.02.04SB). Your recitation instructor will work through the first part of the recitation exercise with you during the recitation period and will answer questions. The better prepared you are, the more you will accomplish during the class session You must hand in the specified deliverables for the recitation to your LECTURE INSTRUCTOR during class on the due date to receive credit for the exercise. Late assignments and recitation exercises will not be accepted unless you have made advanced arrangements with your instructor.

Class Index Cards:

For many recitation exercises, individual projects and in-lecture designs, you will be required to hand-in an index card for each Java class. One side the card specifies the public interface for the class; the other side gives implementation and usage notes. A sample of the specific format will be provided in class. You are expected to bring your index cards to the lectures and to the exams.

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.

Lecture Attendance and Make-up Exam Policy:

Attendance in the lecture 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 your instructor before the exam, or as soon after the exam as possible.

Drop Date:

Friday, October 27, 2000 is the last day to drop this course.

Programming Environment:

We will be using the Microsoft J++ development system along with Java version JDK 1.2.2. This software is available on the machines in all of the student computing facilities. However, the primary computing facility for the course is the CS Teaching Laboratory in room 1.02.04 SB. This room is open for a number of scheduled hours outside of class time and staffed with tutors who can assist you with account and programming problems (except for your 4 individual assignments of course). The schedule for this room can be found at http://vip.cs.utsa.edu/cslab/schedule. Schedule changes and notices are posted here, so be sure to check this schedule on a regular basis. You will have an individual account on the CS Sun Network which gives you access to both NT and Unix machines in the Division of Computer Science. Through this account you will have disk disk space for storing your files as well as email and a personal web page. You can access your files from home through this account. However, you should also back up your programs on a floppy. This account is for coursework only. You are expected to take care in maintaining the security of this account. Do not give your password to anyone. Your instructors will be regularly contacting you by email with information about the class. You MUST read your email several times a week. The class email alias is for instructor use ONLY. If you have a suitable PC at home, we encourage you to install the CURRENT version of Visual J++ on your machine so that you can develop code at home. The Microsoft J++ is part of the Microsoft Visual Studio Suite and can be purchased at low cost in the game room at the University Center.

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 collaborate on the recitation exercises, but direct copying is not allowed. You may NOT collaborate on any of the five individual programming assignments. 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. Because patterns of cheating do not always become apparent until after several assignments have been completed, you will be asked at the end of the course to hand in all of your source in electronic archival form. Instructions for doing this will be given at the end of the course. Each project should be kept in a separate directory as specified in the project description and should not be deleted.