TCSS142 Winter 2005

1
TCSS142 Winter 2005

• Welcome!

2
TCSS142 Winter 2005

• Course web page is here http//faculty.washington
  .edu/hanks/Courses/142/w05
• Syllabus, schedule, assignments, slides, etc.
• Slides will be available by noon of each class
  day

3
Assignments and Grading

• Three exams
• two in class
• one at the scheduled final exam
• Seven assignments
• see schedule for due dates
• The general model for course work
• lectures come from UWT
• questions and discussion come from everywhere
• assignments and exams will be the same for
  everybody
• assignments and exams will be graded separately
  at each institution
• lab sessions, lab support, help sessions, etc.
  will be held separately at each institution

4
Instructors

• At UWT
• Steve Hanks Office Pinkerton 307 Office
  hours in lab or by appointment Email
  hanks_at_u.washington.edu
• At Olympic
• Dondi Hanson Email dhanson_at_oc.ctc.edu
• At Pierce
• John Staneff Email jstaneff_at_pierce.ctc.edu

5
Class Time Schedule

• 415 425
• setup and class-specific mechanics, no remote
• 425 520
• first half of class, TV is live!
• 520 530
• break
• 530 620
• second half of class, TV is live!
• 620 630
• wrapup and discussion, class-specific mechanics,
  no remote

6
What Are We Going to Do?

• Computer fluency
• operating systems, programming languages,
  compilation and interpretation, development
  environments and deploying solutions
• Programming fluency
• things youll see in any programming language
• variables and data storage, control and
  algorithms, input and output
• Java proficiency
• how to do all of the above in Java
• Object-oriented programming
• New ways of thinking
• thinking very abstractly (keeping the big picture
  in mind)
• thinking very concretely (understanding and
  attending to the smallest details)

7
Expectations

• Maturity this is a college class, you are
  responsible for your own success, though we will
  do absolutely everything in our power to help you
  to succeed
• Participation
• attend class and labs
• participate in the discussion (take some chances)
• be responsible about completing your coursework
• handing in on time
• being a responsible member of a pair for pair
  programming assignments
• Participation
• if you dont understand something, say so
• if you do understand something, say so
• Participation
• you dont know if you understand something until
  you try to apply it
• Practice
• you dont know if you understand something until
  you try to apply it
• Participation
• you dont know if you understand something until
  you try to explain it to somebody else

8
Cooperation versus Plagiarism

• Exams must be completed individually
• Assignments must be essentially your own work
• Studying for exams together is always OK
• Getting help on a specific problem (e.g. a syntax
  error) from a classmate or anybody in the lab is
  always OK
• Discussing approaches to a programming assignment
  with a classmate is generally OK but
• Copying substantial amounts of somebody elses
  solution to a programming assignment is never OK
• When in doubt use the Gilligans Island rule
• after working with a classmate on the approach to
  a programming assignment, watch (exactly) ½ hour
  of Gilligans island
• then go on to complete the assignment by yourself
• Getting a solution off the web is never OK
• Getting reference material off the web is always
  OK

9
01-04

• Deadlines
• Assignment 1 on the web now, due Thursday 1/6
  (beginning of class)
• Last time
• No such thing
• Today
• Overview of computing systems, terminology
• Programming languages, compilers, interpreters
• First Java program and how everything fits
  together