Department of Computer Sciences
University of Texas at Austin

CS 303E - Elements of Computers and Programming (Summer 2009)
Section: 90380, MTW (Discussion Th) 11:30 AM - 1:00 PM, RLM 5.104
Section: 90385, MTW (Discussion F) 11:30 AM - 1:00 PM, RLM 5.104

Instructor: Dr. Shyamal Mitra
Office: PAI 5.52
Office Hours: MTW 1:00 PM - 2:00 PM or by appointment

Teaching Assistant: Erkin Bahceci
Office Hours: ThF 2:00 PM - 3:00 PM
Location: Elements Lab PAI 5.38

Proctor: Raleigh Schickel
Office Hours: WF 3:00 PM - 4:00 PM
Location: Elements Lab PAI 5.38

Required Text: Introduction to Java Programming, Brief by Y. Daniel Liang, Seventh Edition. Publisher: Prentice Hall. ISBN: 0136042589

Scope of the Course

Computing is an integral part of all natural sciences and engineering disciplines. All other disciplines require some familiarity with computers. This course is designed to teach the fundamentals of computing and programming to students who wish to minor in Computer Science. In this course we will cover basic computer architecture and software components. We will learn to program in a high level language (Java). We will learn problem solving techniques for numerical and scientific problems. We will study the object-oriented features of Java, develop our own algorithms, and translate them to computer code. No prior programming experience is required but familiarity with personal computers will help significantly.

We will be following the text quite closely. Supplemental notes will be available on the web. Unlike the traditional lecture format, our classes will be a venue for solving problems, writing programs, and exchanging ideas. Your attendance to the classes is mandatory. If you are not there for any lecture you need to send me an e-mail explaining why.


You may choose to use your own computer to work on these assignments. If you work on your home computer, you will have to download and install the Java Software Development Kit from Sun Microsystems. You will also want an IDE like BlueJ, JBuilder, or JCreator.

The only way to learn programming is to program. Doing the programming assignments is crucial to performing well in class. I strongly recommend that you write programs over and above what is assigned to you. Assignments will be given almost every week. Each assignment will have a clearly stated due date and time. Assignments start out being easy but get harder over the semester. If you are having considerable difficulty with Assignments 2 and/or 3, please see me immediately.

The assignments will require a substantial time commitment over several days (an average of 8 hours per week should be expected). Be sure to budget sufficient time to complete assignments before the deadline.

Turn in your assignments on time. This permits grading to start promptly after the submission deadline so that assignments maybe returned promptly. If you do not finish an assignment by the deadline you have a maximum of two days to turn your assignment in. However, there is a penalty of 10 points (out of a 100 points) per day. Your assignment is one day late until the midnight of the day after it is due, two days late from then until midnight of the second day. If you still have not finished your assignment, see me and discuss your particular situation. You may be given an extension.

Specific grading criteria vary on each assignment. However, in general, programs that do not compile correctly on the CS Lab configuration will receive no more than 80% of the possible points. Other point deductions are given for such things as: incorrect results, missing features, bad solution logic, etc. No matter what configuration of software that you have on your home computer, the assignment that is turned in must run successfully on the CS Lab configuration in order to be graded. Here is the general grading criteria for programming assignments.

All assignments must be submitted using the web based turnin program. But whether you can use the turnin program or not, you must make a backup copy of the java source code (i.e. the .java file) on your removable secondary storage device (e.g. flash drive). This will be necessary in cases where your program gets lost, is corrupted, or if there is some dispute over what was turned in when.

If you cannot get the turnin program to work for you in the CS Lab, then have a TA or proctor in the lab email the assignment for you to your TA, with a copy to you or another TA or proctor for proof of mailing. For assigned programs, the source code (.java file) must be turned in; no credit will be given for turning in a compiled, executable, or other file. The source code must be a text file that can be compiled and run; word processing files will not be accepted. If you are using BlueJ (or another another IDE) always submit the .java file.

If you want us to help you debug your program, upload your program to UT Webspace or bring your program (on a portable storage device like USB Flash Drive) to us during office hours and we will go through the program with you. Do NOT just e-mail the program to us for debugging.

Graded Assignments: Assignments submitted via the turnin program are placed in your directory on the turnin server. Graded assignments will be returned by placing a copy of the graded assignment in the same directory. The copy will contain comments and your grade and will have a file name similar to the name of the file turned in. These files can be viewed with any text editor such as Notepad. Once you have submitted an assignment for a grade, do not delete the submitted file or the returned file from the server. These files are part of your record for the course and must be saved by you in case of a lost file or grade dispute.

Assignment Identification: All assignments must be submitted with the proper header, containing your name (as registered), your unique section number, and the assignment number at the top of the assignment. The format for the header will be specified in the assignment. That specification will over-ride any other header specification (e.g. the header description in the documentation for the turnin program).

In addition, because assignments are submitted as files by the turnin program, they must have the correct file name, which will be specified in the assignment handout. You must also ensure that you turn in the assignment to the correct unique section folder - that is, the section you are currently registered in. Lost assignments are typically caused by turning in an incorrect file name and/or turning a file into the wrong section folder. Assignments, which omit the header or are incorrect in any one or more of these requirements, will have the grade reduced by 5% of the maximum grade.


There will be three tests and no final examination. The three tests will last an hour and a half and will be given during either of the discussion section. Make-up tests will be given ONLY for an official UT conflict or an emergency. You must submit a written make-up request with proof to the instructor. For each test you may bring a non-programmable calculator. The test schedule is as follows:


Your performance in this class will be evaluated using your scores for class participation, quizzes, programming assignments, and three tests. The weights of each of these components are listed below:

If you have more than 3 abscences during the semester you will forfeit all the points alloted to class participation, i.e. 5% of your final grade.

There are no extra credit projects to improve your grade. Questions concerning test grades should be given to me in writing along with your test within the next class day that the test is handed back. Questions regarding the programming assignments should be first discussed with the proctor. If you still have a problem give me a written statement within one week of the class that the assignment was returned. No questions about grading will be considered after these deadlines.

Study Groups

Please organize yourselves into study groups of ~5 students who will meet once a week to discuss the course. Typically, you will review the lectures, do the reading, and attempt the homework independently before your weekly meeting with your study group. Studying for tests together is permitted and encouraged. If you are unsure about how to work together with your friend in a legal, helpful manner, do come and talk with us. Remember, it is always ok to "work together" with your professor or TA!

Academic Misconduct Policy

While you are free to discuss the course material with your classmates and are encouraged to form study groups for the exams, collaboration on homework or programming assignments is not permitted unless you have notified us that you will be doing pair programming with a partner.

Helping a friend understand the intent of a homework or programming assignment specification is permitted. Students who are not pair programmers and who work together too closely (e.g. design their solution together) should be aware that this is a form of cheating called COLLUSION and is subject to academic penalties. Penalties for academic misconduct include a failing grade in this course.

The homework, programs, and exams must be the work of students turning them in. University policy (see Dean of Students' policies on academic integrity) will be followed strictly.

Acts that exceed the bounds defined by the approved collaboration practices will be considered cheating. Such acts include:

We urge everyone in the class to take appropriate measures for protecting one's work. You should protect your files, homework solution sheets, etc. as deemed reasonable.

Your Responsibilities in This Class

Course Time Table

General Policies

If you are absent from class or examination for the observance of a religious holy day you may turn in your assignment or take the examination on an alternate date provided you have given me written notice fourteen days prior to the class absence. For religious holy days that fall within the first two weeks of class notice must be given on the first class day.

Students with disabilities who need special accommodations should contact the Services for Students with Disabilities (SSD) Office (471-6259 or 471-4641 TTY).