Difference between revisions of "IB Computer Science 2"

From WLCS
Line 1: Line 1:
 +
== Monday (2/22/16) ==
 +
'''Agenda:'''
 +
* Criterion E: Evaluation - Due '''Tuesday (3/1/16)'''
 +
** [http://xmltwo.ibo.org/publications/DP/Group4/d_4_comsc_tsm_1201_1/IA3en/MarkedCrit_E_Evaluation03_en.pdf Criterion E Example]
 +
* This criterion should be completed as two parts (headings)
 +
*'''Evaluation of the product''' (you should be able to do some of this by Monday)
 +
** The evaluation of the product should refer directly to the success criteria in Criterion A, feedback from the client/adviser, as well as any other appropriate feedback obtained.
 +
** You should basically demo your product to multiple people and have them comment on each success criteria
 +
* '''Recommendations for the future development of the product''' (you should be able to do this by Monday)
 +
** The student will use the feedback and the evaluation of the specific performance criteria to recommend possible future developments to the product. These recommendations should explain the benefits of these developments.
 +
** You should basically ask in your feedback, suggestions for extending or enhancing the project.  Explain why each new development would be good.
 +
** You should have at least 2 minor improvements and 2 major improvements
 +
* Networks
 +
** [[Media:DataTransmission.pptx]]
 +
** [[Media:WirelessNetworking.pptx]]
 +
* Work on Internal Assessment
 +
 
== Thursday - Thursday (2/11/16 - 2/18/16) ==
 
== Thursday - Thursday (2/11/16 - 2/18/16) ==
 
'''Agenda:'''
 
'''Agenda:'''

Revision as of 12:11, 22 February 2016

Monday (2/22/16)

Agenda:

  • Criterion E: Evaluation - Due Tuesday (3/1/16)
  • This criterion should be completed as two parts (headings)
  • Evaluation of the product (you should be able to do some of this by Monday)
    • The evaluation of the product should refer directly to the success criteria in Criterion A, feedback from the client/adviser, as well as any other appropriate feedback obtained.
    • You should basically demo your product to multiple people and have them comment on each success criteria
  • Recommendations for the future development of the product (you should be able to do this by Monday)
    • The student will use the feedback and the evaluation of the specific performance criteria to recommend possible future developments to the product. These recommendations should explain the benefits of these developments.
    • You should basically ask in your feedback, suggestions for extending or enhancing the project. Explain why each new development would be good.
    • You should have at least 2 minor improvements and 2 major improvements
  • Networks
  • Work on Internal Assessment

Thursday - Thursday (2/11/16 - 2/18/16)

Agenda:

Tuesday (2/9/16)

Warmup:

  1. Given the following scenario: The light bulb(L) is ON if switch A (A) is OFF and switch B (B) is ON and either switch B (B) is OFF or switch (C) is ON
  2. Write the Boolean expression to represent with the light bulb (L) is ON/OFF
  3. Draw the truth table for the Boolean expression
  4. Draw the logic gate diagram/circuit for the expression

Agenda:

Friday (2/5/16)

Agenda:

  • Logic gate quiz
  • Circuit Simulator
  • Media:BooleanLogic.ppt
  • Media:LogicGates.ppt
  • Boolean expression word problems
  • Criterion D - Functionality and extensibility of product
    • This criterion should be completed as two parts and does not require any additional written documentation.
    • Functionality of the product
      • The student must use the video to demonstrate the product functioning (2-7 minutes in length). This evidence will be supported, where possible, by the product on the CD-ROM/DVD or USB.
      • i.e. demo the your program's functionality
    • Extensibility of product
      • The student should design the product so that it can be maintained by another party and/or be further developed. Therefore the design of the product should include appropriate folder and data structures, intuitive file and/or class naming conventions and, where appropriate, comments in the code.
      • i.e. your program should be well-organized (good filenames, clean code, good variable names, comments)
  • Assignment - Scripting your demo
    1. Outline the functionalities that you listed in your criteria for success in Criterion A
    2. Expand your outline with scripted lines and actions that explain and demo the different parts of your project
    3. You should be able to demonstrate each requirement/criteria you listed in Criterion A
    4. Time yourself and how long it takes to read the script at a moderate pace (You should aim for ~5 minutes)
    5. Turn in your scripted outline via Google Classroom by Tuesday (2/9/16)

Wednesday (2/3/16)

Agenda:

  • StudentVUE has been updated
    • You have today demo missing assignments
    • If you are turning in a missing assignment, you MUST show it to Mr. Bui in person and e-mail him requesting an update
  • IB candidate session numbers
  • Operating Systems quiz
  • Internal Assessment
    • return Criterion C
    • 3rd quarter grade will be based on the final IA as a whole
  • Criterion D - Functionality and extensibility of product
    • This criterion should be completed as two parts and does not require any additional written documentation.
    • Functionality of the product
      • The student must use the video to demonstrate the product functioning (2-7 minutes in length). This evidence will be supported, where possible, by the product on the CD-ROM/DVD or USB.
      • i.e. demo the your program's functionality
    • Extensibility of product
      • The student should design the product so that it can be maintained by another party and/or be further developed. Therefore the design of the product should include appropriate folder and data structures, intuitive file and/or class naming conventions and, where appropriate, comments in the code.
      • i.e. your program should be well-organized (good filenames, clean code, good variable names, comments)
  • Assignment - Scripting your demo
    1. Outline the functionalities that you listed in your criteria for success in Criterion A
    2. Expand your outline with scripted lines and actions that explain and demo the different parts of your project
    3. You should be able to demonstrate each requirement/criteria you listed in Criterion A
    4. Time yourself and how long it takes to read the script at a moderate pace (You should aim for ~5 minutes)
    5. Turn in your scripted outline via Google Classroom by Tuesday (2/9/16)
  • Introduction to Boolean Algebra & Logic Gates
  • Logic Gate Quiz - Friday (2/5/16)
    • Be able to draw all the logic gates AND their truth tables

Thursday - Friday (1/21/16 - 1/29/16)

  • Snowzilla!

Tuesday (1/19/16)

Agenda:

Thursday (1/14/16)

Agenda:

Tuesday (1/12/16)

Agenda:

Friday (1/8/16)

  • Group 4 Project Day

Monday - Wednesday (1/4/16 - 1/6/16)

Monday - Thursday (12/21/15 - 12/31/15)

  • Winter Break

Thursday (12/17/15)

Agenda:

Tuesday (12/15/15)

Agenda:

Wednesday - Friday (12/9/15 - 12/11/15)

Agenda:

  • Binary Tree Quiz
  • Missing Demos
    • Dynamic Queue
    • Linked List
  • Media:Recursion_Java.ppt
  • Binary Tree Code walk-through
  • Internal Assessment

Thursday - Monday (12/3/15 - 12/7/15)

Agenda:

  • LinkedList demos!
  • Introduction to Binary Trees
  • Binary Tree Quiz on Wednesday (12/9/15)

Tuesday (12/1/15)

Agenda:

  • Dual enrollment application and testing
  • Complete LinkedList assignment posted on Google Classroom

Friday - Tuesday (11/20/15 - 11/24/15)

Agenda:

  • Demo DynamicQueue
  • Introduction to Linked Lists (walk-through)
    • Data Structure Visualizations
    • What does a Linked List look like?
    • Linked List attributes
      • first
      • last
      • size
    • Linked List methods
      • adding data (beginning, middle, end)
      • deleting data (beginning, middle, end)
      • getting data
      • modifying data
      • searching for data
      • clearing all data
    • Complete LinkedList assignment posted on Google Classroom

Wednesday (11/18/15)

Agenda:

  • Finish DynamicStack walk-through
  • Testing DynamicStack
  • Dynamically-sized Queues - complete by the end of today
    1. On paper, draw the before-and-after pictures