DOC PREVIEW
UW CSE 142 - Syllabus

This preview shows page 1 out of 2 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 2 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 2 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

University of Washington Computer Science & Engineering 142: Introduction to Programming I Course Syllabus, Autumn 2011 Instructors Administrator name: Hélène Martin Marty Stepp Pim Lustig email: [email protected] [email protected] [email protected] office: CSE 338 CSE 214 CSE 126 office phone: (206) 616-5772 (206) 685-2181 (206) 616-3225 Please see the course website for our office hours. Pim handles many course details, e.g. registration and switching sections. Course Overview This course provides an introduction to programming using the Java programming language. We will explore common computational problem-solving techniques useful to computer scientists but also to anyone with large data sets, repetitive processes or other needs for computation. No prior programming experience is assumed, although students should know the basics of using a computer (e.g., using a web browser and word processing program) and should be comfortable with math through Algebra 1. Students with significant prior programming experience should consider skipping CSE 142 and taking CSE 143 (we allow this without any special permission). Lecture Time MWF 9:30 AM - 10:20 AM, Guggenheim 220 (Lecture A) MWF 11:30 AM - 12:20 PM, Guggenheim 220 (Lecture B) Discussion Sections You will be expected to participate in a Thursday discussion section, held at various times (see course web site for details). The TA who runs your section will grade your homework assignments. In section we will answer questions, go over common errors in homework solutions, and discuss sample problems in more detail than we can in lecture. Each student will be assigned a section participation score that is weighted the same as one homework assignment. You will receive up to 3 points for each section you participate in, up to a maximum of 20 points. Two of those points will be awarded for successful completion of short take-home problems from the textbook that will be due at the start of each week's section. Course Web Site • http://www.cs.washington.edu/142/ All resources from class will be posted here. Check the web site daily for important announcements. Textbook • Reges/Stepp, Building Java Programs: A Back to Basics Approach (2nd Edition). ISBN 0136091814. Required. can be purchased from UW Bookstore, online (e.g. Amazon.com), or as a download for lower cost UW instructors wrote the book specifically for this course to supplement lectures and clarify concepts. We will expect you to refer to the book when you miss lecture, don’t quite understand an idea or need extra practice problems. Exams in this course will be open-book and the book will be the ONLY reference you may use. Textbook exercises will be due in your discussion sections each week. Computer Access and Software The department operates an Introductory Programming Lab (IPL) in room 334 of Mary Gates Hall. TAs and consultants will be available at the lab to help students with problems. The recommended software is the Java Development Kit (JDK) version 6 and the jGRASP editor. The course web site contains links to download this software free of charge if you want to work at home.Grading 50% weekly homework assignments (including section participation) 20% midterm (Friday, November 4, 2011 in lecture) 30% final exam (Wednesday, December 14, 2011) lecture A: 10:30-12:20 Kane 130 (confirmed 10/18) lecture B: 12:30-2:20 in Kane 130 (confirmed 10/18) This maps to the 4.0 scale roughly as follows. You will get at least the grade below for the percentage shown. 90%: at least 3.5 85%: at least 3.0 80%: at least 2.5 75%: at least 2.0 70%: at least 1.5 60%: at least 0.7 Exams You may use the textbook as reference during exams but nothing else. You may highlight your book and add reasonable margin notes (i.e. not entire paragraphs or programs). No electronic devices may be used, including calculators. Make-up exams will not be given except in case of a serious emergency. If you must miss an exam, even if you are sick or injured, you must contact an instructor before the exam (or arrange for someone to do so). You must show evidence that you are physically unable to take the exam, such as a clear and specific doctor's note mentioning the date, exam, and reason. No make-ups will be granted for personal reasons such as travel, personal hardship, leisure, or to ease exam week schedules. No student will be permitted to take an exam early for any reason. Homework Homework consists of weekly programming assignments done individually and submitted electronically from the course web site. Programs will be graded on "external correctness" (behavior) and "internal correctness" (style and design). Disputes about homework grading must be made to your TA within 2 weeks of receiving the grade. Lateness Each student receives 5 "late days" for use on homework assignments. A late day allows you to submit a program up to 24 hours late without penalty. For example, you could use 2 late days and submit a program due Tuesday 9pm on Thursday by 9pm with no penalty. Once a student has used up all the late days, each successive day that an assignment is late will result in a loss of 1 point on that assignment. Regardless of how many late days you have, you may not submit a program more than 4 days after it is due or after the last day of class. Students will not be given extensions unless they have extenuating circumstances as decided by the instructor. Academic Integrity and Collaboration Programming assignments must be completed individually; all code you submit must be your own work. You may discuss general ideas of how to approach an assignment, but never specific details about the code to write. Any help you receive from or provide to classmates should be limited and should never involve details of how to code a solution. You must abide by the following rules: • You may not work as a partner with another student on an assignment. • You may not show another student your solution to an assignment, nor look at his/her solution, for any reason. • You may not have another person "walk you through" an assignment, describe in detail how to solve it, or sit with you as you write it. You also may not provide such help to another student. This includes current or former students, tutors, friends, TAs, paid consultants, people on the


View Full Document

UW CSE 142 - Syllabus

Download Syllabus
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Syllabus and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Syllabus 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?