What’s this course all about?

Slides:



Advertisements
Similar presentations
CSc 2310 Principles of Programming (Java)
Advertisements

Lecture 1: Overview CMSC 201 Computer Science 1 (Prof. Chang version)
CS3L: Introduction to Symbolic Programming Summer 2008Colleen Lewis Lecture 1: Introduction & Administration.
COMP 14 Introduction to Programming Mr. Joshua Stough January 12, 2005 Monday/Wednesday 11:00-12:15 Peabody Hall 218.
COMP171 Data Structures and Algorithm Huamin Qu Lecture 1 (Sept. 1, 2005)
Class 1: What this course is about. Assignments Reading: Chapter 1, pp 1-33 Do in Class 1: –Exercises on pages 13, 14, 22, 28 To hand in in Class 2: –Exercises.
OBJECT ORIENTED PROGRAMMING I LECTURE 1 GEORGE KOUTSOGIANNAKIS
COMP171 Data Structures and Algorithm Qiang Yang Lecture 1 ( Fall 2006)
COMP 110 Introduction to Programming Jingdan Zhang June 20, 2007 MTWRF 9:45-11:15 am Sitterson Hall 014.
CS 152 & CS 154 Bill Crum, Lecturer Bill White, Instructional Coordinator Earth Chandrraungphen, Lab TA.
COMP 110 Introduction to Programming Mr. Joshua Stough August 22, 2007 Monday/Wednesday/Friday 3:00-4:15 Gardner Hall 307.
Modern Optics Lab Modern Optics Lab Introductory Meeting.
COMP 14 – 02: Introduction to Programming Andrew Leaver-Fay August 31, 2005 Monday/Wednesday 3-4:15 pm Peabody 217 Friday 3-3:50pm Peabody 217.
Please open your laptops and pull up Quiz Only the provided online calculator may be used on this quiz. You may use your yellow formula sheet for.
Summer 2009 Math 1431 and Math 1432 begin. What to do… Watch the orientation video from the spring online classes. Please note that the spring classes.
COP4020/CGS5426 Programming languages Syllabus. Instructor Xin Yuan Office: 168 LOV Office hours: T, H 10:00am – 11:30am Class website:
CS 450: COMPUTER GRAPHICS COURSE AND SYLLABUS OVERVIEW SPRING 2015 DR. MICHAEL J. REALE.
Welcome to Biology 101! Please pick up a syllabus (if you don’t have one yet) and a clicker at the front desk. You will need to rent a clicker from the.
Welcome to Biology 102! Please pick up a syllabus (if you don’t have one yet) and a clicker at the front desk. You will need to rent a clicker from the.
CS211: Course Overview George Mason University. Today’s topics Go over the syllabus Go over resources – Marmoset – Piazza – Textbook Highlight important.
Spring 2008 Mark Fontenot CSE 1341 Principles of Computer Science I Note Set 1 1.
Medical Law and Bioethics
Welcome to CS 115! Introduction to Programming. Class URL Please write this down!
Spring 2008 Mark Fontenot CSE Honors Principles of Computer Science I Note Set 1 1.
Please open Daily Quiz 34. A scientific calculator may be used on this quiz. You can keep your yellow formula sheets out when you take the quiz. Remember.
Course Introduction CS 2302 SPRING Course Introduction In this part we'll discuss course mechanics. Most of this will apply to all sections of the.
COMP 111 Programming Languages 1 First Day. Course COMP111 Dr. Abdul-Hameed Assawadi Office: Room AS15 – No. 2 Tel: Ext. ??
Welcome to CS 3260 Dennis A. Fairclough. Overview Course Canvas Web Site Course Materials Lab Assignments Homework Grading Exams Withdrawing from Class.
COMP Introduction to Programming Yi Hong May 13, 2015.
CSc 2310 Principles of Programming (Java) Dr. Xiaolin Hu.
CSC 212 – Data Structures Prof. Matthew Hertz WTC 207D /
CSE 331 Software Design & Implementation Hal Perkins Autumn 2012 Lecture 0 – Course Introduction 1CSE 331 Au12 One handout up front!
Welcome to CS 115! Introduction to Programming. Class URL
ECEN 301Discussion #1 – Syllabus1 All Sections MWF 1:00 – 1:50 PM 256 CB Lecture: MW Recitation: F Labs: M or Th Instructor: Prof. David Long Office: CB.
CSCE 1040 Computer Science 2 First Day. Course Dr. Ryan Garlick Office: Research Park F201 B –Inside the Computer Science department.
CS355 Advanced Computer Architecture Fatima Khan Prince Sultan University, College for Women.
CSCI 51 Introduction to Computer Science Dr. Joshua Stough January 20, 2009.
Welcome to CS 115! Introduction to Programming. Class URL Write this down!
Matter and Interactions 1 Fall 2006 Matter & Interactions I Physics Professor & Lecturer: Dr. Reinhard Schumacher Teaching Assistants: Ms. Elisa.
Agenda for the week of 1/28: You should be finished your midterm exam! It had three sections: Multiple Choice, Short Answer was completed in session #1.
CS 210 DATA STRUCTURES AND ALGORITHIMS Fall 2006.
1 CS1100 Fall Instructor: David Gries CS100M: Matlab No prior programming experience One semester of calculus Math & engineering type problems CS100J:
INTRODUCTION TO PROGRAMMING ISMAIL ABUMUHFOUZ | CS 146.
Lecture 1: Overview CMSC 201 Computer Science 1. Course Info This is the first course in the CMSC intro sequence, followed by 202 CS majors must pass.
CSCE 1030 Computer Science 1 First Day. Course Dr. Ryan Garlick Office: Research Park F201 B –Inside the Computer Science department.
1 CS 101 Today’s class will begin about 5 minutes late We will discuss the lab scheduling problems once class starts.
More Inheritance 7/2/2009. Important Dates Project 1 - Check-off – Thursday 7/02/2009 ready BEFORE lab Review Session – Sunday 7/05/2009 – 306 Soda 1-4pm.
1 COP 2510 Programming Concepts Spring credit hours Instructor:Dr. Rollins Turner ENB 343F Office Hours: MW 11:00 AM – 12:00.
REMINDER: If you haven’t yet passed the Gateway Quiz, make sure you take it this week! (You can find more practice quizzes online in the Gateway Info menu.
Welcome to AB113 Accounting for Non-Majors
CSE 1340 Introduction to Computing Concepts Class 1 ~ Intro.
Course Information CSE 2031 Fall Instructor U. T. Nguyen /new-yen/ Office: CSEB Office hours:  Tuesday,
CS122 Engineering Computation Lab Lab 2 Bruce Char Department of Computer Science Drexel University Winter 2012.
CS 161 Introduction to Computer Science I Winter, 2014: 112 Spring, 2014: 131 Summer, 2014: 132.
IST 210: ORGANIZATION OF DATA Introduction IST210 1.
Course Information CSE 2031 Fall Instructor U.T. Nguyen Office: CSE Home page:
ICS 151 Digital Logic Design Spring 2004 Administrative Issues.
PROBLEM SOLVING AND PROGRAMMING ISMAIL ABUMUHFOUZ | CS 170.
REMINDER: If you haven’t yet passed the Gateway Quiz, make sure you take it this week! (You can find more practice quizzes online in the Gateway Info menu.
Spring 2008 Mark Fontenot CSE 1341 – Honors Principles of Computer Science I Note Set 1 1.
CIS 505: Programming- Language Paradigms Torben Amtoft Xinming (Simon) Ou Aug 23, 2010.
Computer Science I ISMAIL ABUMUHFOUZ | CS 180. CS 180 Description BRIEF SUMMARY: This course covers a study of the algorithmic approach and the object.
Grade Scale Quiz 3 Results: Average class score after partial credit: XX.X% Commonly missed questions: # ____________________ We will be going over some.
Introduction to Programming
Welcome to CS 1010! Algorithmic Problem Solving.
Welcome to CS 1010! Algorithmic Problem Solving.
Welcome to CS 1301! Principles of Programming I.
Overview Basic Information Lecture Labs Lab Reports Homework Exams
ECE 103 Engineering Programming Chapter 1 Introduction
CS Problem Solving and Object Oriented Programming Spring 2019
Presentation transcript:

What’s this course all about?

Project 1

Project 2

Project 3

Staff

Lab Assistants (more to come!)

Lectures Tuesday/Thursday 5:10-6:00 10 Evans

Labs Online curriculum: ucwise.org During lab – Take the quiz online (capped at 70%) – Do online lab activities – Work with a partner – Participate in discussion section – Get help from other students, lab assistants & TAs

What’s the difference between CS61B and CS61BL? Lecture Discussion Lab Lecture Lab Discussion 1 week In CS61B 1 week In CS61BL

Why are we doing lab based? Community Learn by doing Interviewing practice Extra pair of eyes (or ears) Frequent feedback/support Lecture Notes: – Lecture Videos: –

How is summer session different? Lecture Lab Lecture Lab 1 week in summer CS61BL Lecture Lab Discussion 1 week In CS61BL Discussion

Do I have to come to lab? Yes - to get credit for the quiz!

Books Head First Java, second edition, by Kathy Sierra and Bert Bates (O’Reilly, 2005); Pragmatic Unit Testing in Java with JUnit, by Andrew Hunt and David Thomas (The Pragmatic Bookshelf, 2004); Data Structures and Abstractions with Java, second edition, by Frank M. Carrano (Prentice Hall, 2007).

Reading Assignments

Exams Midterm 1: Tuesday July 7 th, – 5-6pm in 10 Evans Midterm 2: Tuesday July 28 th, – 5-6pm in 10 Evans Final: Thursday August 13 th, – 5-8pm in 10 Evans

Review Sessions Review 1: Sunday July 5 th, – 1-4pm in 306 Soda Review 2: Saturday July 25 th, – 1-4pm in 306 Soda Review 3: Sunday August 9 th, – 1-4pm in 306 Soda

Projects Project 1 (individual): – due Monday July 13 th, 10pm Project 2 (with 0 or 1 partner): – due Wednesday July 22 nd, 10pm Project 3(with 1 or 2 partners): – due Tuesday August 11 th, 10pm

inst.eecs.berkeley.edu/~cs61b/su09/

Homework Assigned:Due: Monday during labWednesday before your lab Tuesday during labThursday before your lab Wednesday during labMonday before your lab Thursday during labTuesday before your lab

Grading Assignment category# pointspercent All projects3618% All other homework scaled to:2412% All quizzes scaled to:2010% Midterm 12412% Midterm 23618% Final6030%

Grades: There is no curve! PointsGrade A A A B B B C C C D D D- <80 F

Cheating On every homework assignment and project we will be running cheating detection software to compare your solution with the solution of your classmates and with all previous submissions. If you’re falling behind at all – please talk to Colleen or your TA!

Cheating versus Collaboration Obvious rules: You can’t get a solution from the internet by any method. Don’t copy a current or previous student’s solution. Cheating

Cheating versus Collaboration No code rule: You should never have any part of a current or previous student’s homework or project solution in your possession, either electronically or in hardcopy form. – Lab collaboration clarification: In lab you will write a lot of programs that you will never turn in for homework or a project. For a program that is not turned in, we encourage you to write code with a partner on one computer and then share that collaboratively written code. Always check the day’s homework assignment to make sure you don’t need to turn that code in. If you do need to turn it in, you can talk, but you can not share code.

Cheating versus Collaboration Reusing code: You may reuse code that you have written. The first time you are writing the code if it is for a homework or project you MUST write it yourself. If not, you may work together with a partner. If you would like to reuse some code that you and your partner wrote in a regular lab that was not part of a homework or project, you may reuse that code. Please make a note whenever this is the case.

Cheating versus Collaboration Looking at code rule: You can help a classmate with bugs in their homework or projects and in doing so you can look at their code. Don’t copy their code that you see – all work must be your own and all work must be their own. – Don’t show your own: If you’re helping a classmate find a bug, it is NOT okay to show them your code – whether it is working or not. You should focus only the buggy code in question.

Cheating versus Collaboration Debugging clarification: You can help someone if they have a logical error in their code. You should: Never touch their keyboard or mouse. Ask them lots of questions! Examples: – If they have a run time error: » What is happening on the line indicated by the run-time error? What are you trying to do? » How could that error happen on that line? What would need to be true? How could those conditions be met?

Cheating versus Collaboration Debugging clarification: You can help someone if they have a logical error in their code. You should: Never touch their keyboard or mouse. Ask them lots of questions! Examples: – If the program doesn’t do the right thing: » What test case(s) demonstrates the error? » Can you come up with a simpler test that demonstrates the error? » Can you trace through by-hand a simple example that demonstrates the error? » Have you run the debugger on the simple test to see when the error is introduced? » Have you tested the sub-procedures to make sure that they work?

Cheating versus Collaboration Compiling clarification: If their code doesn’t compile you can help! You should: Never touch their keyboard or mouse. Try to help them figure it out for themselves. You should just be helping. Talk about each syntax error to make sure that it makes sense why the compiler was complaining. Cheating

Cheating versus Collaboration When in doubt – ask rule: If you are not sure whether a particular interaction is appropriate, talk to Colleen Lewis or your lab TA before you submit the solution. Cheating

Cheating versus Collaboration Give credit rule: If you receive a significant idea from someone else, clearly acknowledge that student in your solution. Not only is this a good scholarly conduct, it also protects you from accusation of theft of your colleagues’ ideas. Cheating

Waitlist To be enrolled for the course you need to enroll for a section that is not full. – This means the 8-11am or 6-9pm labs – Do this ASAP! If a spot opens up in a the 11-2 or 2-5 sections you can switch into that section. Please don’t over-crowd the 11-2 or 2-5 sections!

CS Rocks! Welcome to CS61BL!