IB Computer Science 1

From WLCS
Jump to: navigation, search

Friday - Wednesday (6/9/17 - 6/14/17)

Agenda:

Monday - Thursday (6/5/17 - 6/8/17)

Agenda:

  • IB Summer Assignment will be working on IA: Criterion B
  • Final exam exemption slips due by June 12th (or asap)
  • Rock-Paper-Scissors Flowchart Assignment
    • Flowcharts - Media:Flowcharts.ppt
    • Create a flowchart for the Rock-Paper-Scissors game using draw.io
    • Submit a pdf of your flowchart via Google Classroom (due Wednesday (6/7/17))
  • Complete and demo Breakout
  • Work on Internal Assessment

Thursday - Friday (6/1/17 - 6/2/17)

Agenda:

  • Complete and demo Breakout
  • Work on Internal Assessment

Tuesday - Wednesday (5/30/17 - 5/31/17)

Agenda:

  • Complete and demo Breakout
  • Work on Internal Assessment

Monday (5/29/17)

  • Memorial Day

Friday (5/26/17)

Agenda:

  • Java 20Q Assessment
  • Complete Breakout
  • Turn in Internal Assessment: Criterion A: Planning
    • E-mail Mr. Bui if you need an extension

Friday - Thursday (5/19/17 - 5/25/17)

Agenda:

  • Assignments thus far:
    • Emoji
    • Ping w/ Objects (Classes)
    • Preliminary Breakout (only needs bottom brick collision)
  • Current assignment:
    • Breakout w/ collisions on left, right, and tops of bricks
    • Multiple lives
    • Game over when there are no more lives
    • Win screen when there are no more bricks
  • Internal Assessment: Criterion A: Planning
    • Internal Assessment
    • Media:IBCS_InternalAssessmentChecklist.doc
    • IA Criteria Rubrics
    • IA Examples
    • Criterion A Overview - due Friday (5/26/17) via Google Classroom
      • Explicitly state your client
      • Explicitly state your advisor
      • Define and describe the problem or unanswered question (175-250 words)
      • Explicitly reference to documentation or evidence that a client was consulted (e.g. interview notes, transcription, or e-mail thread)
      • Justify your proposed product (175-250 words)
      • List (bulleted sentences/phrases) your success criteria (functionality requirements)
  • Workplace Readiness Skills Assessment - Date TBD

Monday - Thursday (5/15/17 - 5/18/17)

Agenda:

  • Complete the NVCC Dual Enrollment Evaluation
  • Complete End-of-Course Survey
    • Summary results will be shown when all students have finished
  • Complete and demonstrate the preliminary Breakout game with the Brick[] array
    • Displays bricks, paddle, and ball
    • Ball collides with both paddles and bottom of bricks
    • Bricks disappear upon collision
  • Once you have completed and demonstrated the preliminary Breakout game, continue implementing the following features:
    • Collisions with left, right, and tops of bricks
    • Multiple lives
    • Game over when there are no more lives
    • Win screen when there are no more bricks

Thursday - Friday (5/11/17 - 5/12/17)

Agenda:

  • Complete the NVCC Dual Enrollment Evaluation
  • Complete and demonstrate the preliminary Breakout game with the Brick[] array
    • Displays bricks, paddle, and ball
    • Ball collides with both paddles and bricks
    • Bricks disappear upon collision

Monday - Wednesday (5/8/17 - 5/10/17)

Agenda:

  • Complete the preliminary Breakout game with the Brick[] array

Thursday - Friday (5/4/17 - 5/5/17)

Agenda:

  • Interim grades are posting. Assignments thus far:
    • Emoji
    • Ping w/ Classes/Objects
    • Breakout/BrickBreaker Warmup
    • Preliminary Breakout w/ Brick[] (array)
  • Work on Breakout w/ Brick[] array

Tuesday - Wednesday (5/2/17 - 5/3/17)

Agenda:

  • What you should have as of now:
    • A BrickClassTest that defines a Brick class and declares and sets up a Brick[] (array)
    • The draw() should loop through the Brick[] and display each brick
  • Today, you should:
    1. Create a new sketch named BrickBreaker or Breakout
    2. Copy over the Brick class and its setup and display code
    3. Copy over your Ball and Paddle from Ping
    4. Go through the code and clean it up, making any necessary changes
    5. Add a new function named checkBrickBottomCollision(Brick br, Ball ba)
      • It should check if a Ball ba collides with a Brick br's bottom edge, return true and false accordingly
  • Demonstrate your preliminary BrickBreaker/Breakout game for credit

Archives