Required Text: Introduction to Java Programming, Brief Version by Y. Daniel Liang, Ninth Edition. Publisher: Prentice Hall. ISBN: 0-13-292373-4
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. You will be expected to come to class having read the material. The emphasis of the lectures will on critical thinking and problem solving. In class we will analyze problems, design solutions or algorithms, implement the algorithms in code using Java, and test our programs. For this end, your attendance to the classes (lectures as well as discussion) is mandatory. If you are not there for any lecture you need to send me an e-mail explaining why.
This course may be used to fulfill the natural science and technology (Part II) component of the university core curriculum and addresses the following four core objectives established by the Texas Higher Education Coordinating Board: communication skills, critical thinking skills, teamwork, and empirical and quantitative skills.
On several of the assignments you will be asked to work with a partner. Make sure that you read the paper on Pair Programming . This paper spells out the responsibilites and expectations in pair programming and how to distribute the work load equitably.
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 run correctly on the Linux machines in 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 Linux machines in the CS Lab configuration in order to be graded. Here is the general grading critera for programming assignments.
All assignments must be submitted using the web based turnin program. We will not accept assignments e-mailed to us. Before you use the turnin program you must create a CS account. It takes at least 24 hours for your account to get activated. You will have to remember your CS username and password. It maybe different from your UT EID and password. Do not share your account information with anyone. You can reset your password if you forget it.
Always make a backup copy of the Java source code (i.e. the .java file) on a removable secondary storage device (e.g. a 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.
For assigned programs, the source code (.java file) must be turned in. The source code must be a text file that can be run through a Java interpreter. Word processing files (those created with Microsoft Word, for example, and ending with .doc extension ) will not be accepted.
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.
Grade Dispute: You have one week from the date the assignment grade is posted to dispute your grade. The proctors will be grading the assignments. Send the proctor for your section an e-mail and copy the TA in charge of the assignment and see if you can resolve your differences. If you cannot resolve your differences, you may send me an e-mail explaining the situation. We will not entertain any grade disputes after one week.
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.
We will be working on the exercises posted on Coding Bat. Please create an account on Coding Bat . Use your first name and middle name as the first name and your last name with any suffix for the last name on the registration form. Once your account is created, share your account with UTCS312@yahoo.com. Do not send e-mail to this account.
We will be having quizzes regularly throughout the semester. The quizzes will be held on Fridays. There are no make-up quizzes. You may miss one of the quizzes during the semester.
There will be three tests and no final examination. The three tests will be on Wednesdays evenings from 6 pm to 8 pm. Please check the schedule and go to the assigned room.
|Test 1||Wed, 20 Feb||6:00 PM - 8:00 PM||CLA 0.126|
|Makeup 1||Thurs, 21 Feb||6:00 PM - 8:00 PM||CLA 0.102|
|Test 2||Wed, 03 Apr||6:00 PM - 8:00 PM||CLA 0.126|
|Makeup 2||Thurs, 04 Apr||6:00 PM - 8:00 PM||CLA 0.102|
|Test 3||Wed, 01 May||6:00 PM - 8:00 PM||CLA 0.126|
|Makeup 3||Thurs, 02 May||6:00 PM - 8:00 PM||CLA 0.102|
Make-up tests will be given only for the following reasons. In all cases you must provide some form of documentation.
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. We will not entertain any disputes after that time.
If you have more than 6 absences during the semester you will forfeit all the points alloted to class participation, i.e. 5% of your final grade.
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:
Students with disabilities who need special accommodations should contact the Services for Students with Disabilities (SSD) Office (471-6259 or 471-4641 TTY).