Instructor: Rob Atlas
Email: ratlas@cs.wisc.edu
Lecture 6: 11:00 AM - 11:50 AM MWF, 1289 Computer Science
Office: 1301 Computer Science
Office Hours: M 12-1 PM, T 1-2 PM, Th 5-6 PM
Course Homepage:
http://pages.cs.wisc.edu/~cs302/
Lectures 6 Homepage:
http://pages.cs.wisc.edu/~cs302-6/
| Description | This course introduces you to fundamental computer programming concepts as you learn to program in the Java language. Algorithm development, structured programming, code organization (methods), data organization (arrays), basic object-oriented programming, exception handling, and file access are covered. |
| Learning Objectives | Students successfully completing this course will be able to analyze problems and formulate algorithms; create robust, user-friendly, well-structured and well-documented Java programs; read basic Java programs to determine their purpose; and have a basic understanding of how computers work. |
| Registration | The only way to add CS 302 or to change sections is through the UW's online enrollment system. |
| Auditing | Auditing is not allowed for CS 302, but you may sit in the course with the instructor's permission. |
| Pass/Fail | Pass/Fail is allowed by some departments. See your academic advisor. Your department might require a grade of C or better to receive credit and a grade of Satisfactory. |
| Textbook | Java for Everyone |
| Required | by Cay Horstmann, © 2010 Wiley; available for purchase in printed form (textbook or binder versions), electronic form (e-Book), and also on reserve at Kurt Wendt and Helen C. Libraries. See http://pages.cs.wisc.edu/~cs302/?r=text for more information. |
| Computer Labs | There are two instructional Windows XP computer labs
for you to practice programming and do your programming assignments.
These labs are on the first floor of the CS building in rooms 1366 and 1368. They are open from 7 AM to 1 AM each day. They are used for the lab sections when scheduled and otherwise are open labs for 302 students. During the some of the open lab times, consultants are scheduled to assist students. |
| Course Work | |
| Labs (10%) | Labs give you valuable experience using a computer while you
work with a partner to solve problems.
LAB SECTIONS START ON TUESDAY, 9/13. CS 302 students register for one 75-minute lab, which meets once per week in the computer labs mentioned above. You must attend the lab for which you enrolled. You'll be assigned different lab partners and computers during the semester. Lab TAs guide labs and are there to help you succeed on the lab problems. Labs grades are based on prompt attendance, preparation, cooperation with your partner, and progress completing the lab. |
| Programs (30%) | Programming assignments are comprehensive
projects that require substantial time and effort.
Programming assignments give you an opportunity to use the skills you've learned in lecture, the labs, and the textbook readings. There will be four programming assignments. The experience you gain doing programming assignments helps prepare you for exams, future CS courses, and a career in CS. Programming assignment grades are based on correctness, technique, and documentation. Late work is NOT accepted for a grade. Extensions are given for circumstances, such as illness, when you notify your instructor at least three days before the due date. You are responsible for: protecting your work from access by other students; performing frequent backups of your work; and verifying that you have correctly handed in your work (we'll be showing you how). |
| Exams (60%) | Exams are a primary tool we use to evaluate your
performance in this course.
There will be three exams at the dates listed below. The first exam will be multiple choice questions, the second exam will be entirely written, and the final exam will be multiple choice and might have a few written questions.
|
| Pair Programming | Pair programming with another classmate on each programming
assignment is allowed.
You may have a different partner for each programming assignment, but you may NOT have more than one partner on a single programming assignment. Read the online Pair Programming Guidelines before viewing or allowing another student to view, or have electronic access to, any portion of your program. Meet with your instructor or Lab TA if you have any questions regarding the guidelines or procedures for pair programming. Giving access to your code or using as your work any portion of code written by anyone other than your partner, is NOT allowed and is academic misconduct. |
| Academic Conduct | We expect that all students will conduct themselves with
honesty and integrity. Academic misconduct is not acceptable.
You are responsible for doing your own work as well as securing your work so that it is not available in any form to students other than your partner. Failure to do so can result in an academic misconduct investigation. Any investigation of academic misconduct is reported to the Dean's Office. If you are unsure if something is allowed or not allowed, ask your instructor or Lab TA BEFORE you do it. Additional information about policies specific to CS 302 can be found on the CS 302 course web pages. Information about University Academic Misconduct policies and procedures can be found at: http://www.wisc.edu/students/saja/misconduct/misconduct.html |
| Reminders | Make sure to:
|