Instructor: Dr. Steven Robbins
Office: 4.01.23 SB
Phone: 458-5544
Address: srobbins@cs.utsa.edu
Course Homepage: /classes/cs4773s2005/
Office Hours: MWF 11:00 - 12:00
Class Times: MWF 10:00-10:50 am in room SB 3.01.04 (the Linux Lab)
Texts:
Additional Materials
A Mead 5 Star Composition Book,
100 sheets/college ruled 9.75" by 7.5" .
Prerequisites: Java Programming
Course Objectives:
For each laboratory assignment, you will also send an email to the cs4773 account with a summary of the interactions you had concerning that assignment.
At the end of the semester you will turn in a self-evaluation. This evaluation should be one to two pages single spaced (use a word processor). You should explain your strengths and weaknesses in the course, what aspects of your work need improvement, and what you contributed to overall class success.
Course Content:
Unless otherwise stated, all assignments are due at the beginning of class on the due date. There will be a 10 percent penalty for assignments turned in after that time. Do not miss class to finish an assignment. Turn in what you have for partial credit. 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 of your programs.
Work you turn in should be your own, but you may get help from or give help to any member of the class, as long as it is documented. Important: If you use computers long enough you will delete a file by mistake. When working on assignments, make copies of your course code often and store the copies in a safe place. At a minimum, you should store them on your account in a different directory. It is a good idea to use a separate directory for each assignment and a separate subdirectory for each part of the assignment. Copy everything from one part of the assignment into a new directory before starting on the next part. After you have worked several hours on a program and have it almost working, make a backup copy before doing any major modifications.