Outline for Today Course Overview Goals Administrative details - PowerPoint PPT Presentation

Outline for Today • Course Overview • Goals • Administrative details CSE 143 • Workload and grading Computer Programming II • Resources Welcome! This information is largely included in today’s handouts, Course Overview and Administrivia and is on the web No need to transcribe, but do take notes about additional items! 10/9/2003 (c) University of Washington 00-1 10/9/2003 (c) University of Washington 00-2 People Can’t Get In? • Instructor: Hal Perkins • Still a few slots left! Tell your friends to sign up perkins@cs.washington.edu • Historically, openings appear during the first week, but Sieg 208, office hours TBA no guarantees • TA’s: Jiun-Hung Chen, Alan Liu, Bhushan Mandhani, Charlie Reis, Laura Steinkamp, Adrienne Wang, Daniel Wyatt, and Zuo Yan • No waiting list/entry codes cse143-ta@cs.washington.edu (goes to all TAs and the instructor) • Non-matriculated students, grad students, registration • IPL Consultants: once we get their hours worked out, we'll post a schedule. problems – please see Pim Lustig (Sieg 114) • Course administrator: Pim Lustig cse143-admin@cs.washington.edu • Everyone on the course staff: cse143-staff@cs.washington.edu reaches entire staff • You! 10/9/2003 (c) University of Washington 00-3 10/9/2003 (c) University of Washington 00-4 CSE143 Au03 00-1

Java! Are You Ready? A modern approach to programming including • Course is a direct continuation of CSE 142 Java • Objects everywhere; classes, interfaces, polymorphism • Must have a firm grasp of Java basics • Exceptions • including classes, objects, statements, expressions, methods, parameters, • Streams and networking support arrays, etc. • Garbage collection concepts and terminology as well as being able to use in programs • No systematic review • Specifications, design by contract support • Look at old CSE 142 web pages – you should be able to handle those • Rich set of standard libraries assignments and exams • Documentation tools and standards, on-line library documentation • What if you took the C version of CSE 142? Or took 142 • We’ll use Sun’s Java SDK 1.4.2 (windows, *nix) and 1.4.1 (OS X) elsewhere? • 1.3 will not do. • Let’s talk about that now • J++ (Microsoft) will not do • Not sure? • Please update your software! Sit in on both for a few days • Details: Computing at Home page on course web Try the first 143 assignment We'll help you switch to 142 if that's your decision 10/9/2003 (c) University of Washington 00-5 10/9/2003 (c) University of Washington 00-6 Content Overview (1) Content Overview (2) Programming language and libraries Data structures and algorithms • Classes, class relationships (inheritance) interfaces, types • Lists, stacks, queues, trees, dictionaries • Graphical user interfaces & event-driven programming (Swing, • Implementation techniques: arrays, linked data structures event handling, model-view-controller design) • Comparing implementations: basic complexity theory • Exceptions • Divide and conquer algorithms: sorting and searching • Stream I/O and files • And Much Much More! • Recursion 10/9/2003 (c) University of Washington 00-7 10/9/2003 (c) University of Washington 00-8 CSE143 Au03 00-2

Course Objectives Is it or Isn't it? • This is a programming course • This is a programming course • The key goal is learning to program well , not just getting stuff to run • This is not a programming course Good design, good organization, good style Good algorithms, meaningful efficiency • This is not a programming course • Lots of Java features won't be covered See Java reference books for full descriptions of the Java language "Do I contradict myself? We cover the essential parts of Java that support good programming Very well then, I contradict myself. • Many important computer science topics (I am large, I contain multitudes)" Some related to programming, but broader than Java Data structures, algorithms, complexity analysis, software engineering… -- Walt Whitman, Song of Myself from Leaves of Grass • Fact: writing programs that work perfectly isn’t enough to get a perfect grade (!) 10/9/2003 (c) University of Washington 00-9 10/9/2003 (c) University of Washington 00-10 My Goals for You My Expectations for You • 5 things you should be able to do after CSE143 • Responsibility • Be able to design and implement abstractions (classes) using • Keep up, know what’s happening modern programming language features and techniques • Meet deadlines, budget your time, make backups • Be able to test and systematically locate and remove errors in • Take responsibility for your own code and debugging programs • Respect • Be able to learn and use new libraries using standard • For others in the class (people sitting around you in lecture, documentation (no training wheels) members of your quiz section, partners on programming • Be able to evaluate tradeoffs between different projects, …) implementations of an abstraction and pick suitable ones • For the course staff • Be able to communicate technical concepts literately • For yourself 10/9/2003 (c) University of Washington 00-11 10/9/2003 (c) University of Washington 00-12 CSE143 Au03 00-3

Course Organization My Goals For Myself • Be an advocate for your learning (credit to Prof. Mary Pat Wenderoth for this • 3 lectures per week (MWF) notion) • Quiz section twice per week (T & Th) • Help all of you learn • Keep the course on track • Exercises, review, discussions, etc. • Make the homework projects interesting • Frequent quizzes • Make lecture and section events you look forward to! • To keep you up with the reading and assignment instructions • Keep in touch with what’s happening • To test mastery of current material • Office hours – please drop by if just to chat – see the new building! • To provide TAs and me with feedback (you’re not being sent to the Principle’s office!) • Section reps – meet regularly with a collection of volunteers from each section to get more direct feedback • “Muddiest” concept of the day, informal evaluations, etc. 10/9/2003 (c) University of Washington 00-13 10/9/2003 (c) University of Washington 00-14 Assignments Academic (Mis)conduct • Typically (but not always!) due Wed. night 9pm • Goal: balance the following (electronic) and/or in sections or lecture Thursday or • Learning: each student must do the work to learn effectively Friday morning (written) • Cooperation: people learn best when they can cooperate with • Primarily fairly substantial programming projects with others written reports • Fairness and honesty: Nobody should ever represent the work • Maybe some shorter problems and programming drills of someone else as their own or try to claim credit for it • Assignments will more complex than in CSE142 Assignment directions, too! • No late assignments accepted But be sure to talk with your TA about problems truly beyond your control like illness or family emergency so we know what happened. 10/9/2003 (c) University of Washington 00-15 10/9/2003 (c) University of Washington 00-16 CSE143 Au03 00-4

Academic (Mis)conduct Exams & Quizzes • Policy • Exams • You must do assignments by yourself or with your assigned • 2 midterm exams in class; probable dates: Monday Oct. 27 and partner (unless explicitly stated otherwise in an assignment) Monday Nov. 17 • You may discuss general approaches and ideas with others, • Final exam: Tuesday, Dec. 16, 2:30 pm (time set by the but university, location tba) • You may not ever give code to or receive code from others • The exams will not be given on any other days. Don’t • We check this and act when trouble is discovered make plans which would take you away! • Use your common sense and ask first if unclear • Format: mixture of short answer, short essay, multiple • Rule of thumb: any activity you engage in for the purpose of choice, programming earning credit while avoiding learning, or to help others do so, is likely to be an act of academic misconduct (from CSE dept. policy – see link on the web) 10/9/2003 (c) University of Washington 00-17 10/9/2003 (c) University of Washington 00-18 Grading Grading • Grade distribution (subject to change) • Assignment and quiz grading will be very coarse • 30% homework assignments and projects • No partial points • 15% + 15% midterm exams • Typical scale: 4, 3, 2, 1, 0 for assignments and written reports • 25% final exam • Occasionally may use 0..1 or 0..2, etc. • 10% quizzes • Mastery || Good Job! || On the Right Track || Honest Effort, but... || Really, • 5% participation and service Now! • Class is curved • Separate scores for Operation/Practice • Median of final course grades is around 3.0 i.e., Yes! Style, clarity, readability matters Maybe a bit higher when there are a lot of drops • Written reports count as much as the actual code (being able to communicate what you do is a crucial skill) • Why? • Quiz question grading: usually right or wrong 10/9/2003 (c) University of Washington 00-19 10/9/2003 (c) University of Washington 00-20 CSE143 Au03 00-5