Difference between revisions of "IB Computer Science 2"

From WLCS
(→‎Monday (2/25/19))
Line 1: Line 1:
 
== Monday (2/25/19) ==
 
== Monday (2/25/19) ==
 
'''Agenda:'''
 
'''Agenda:'''
−
* Work on your Internal Assessment today
 
 
* Criterion E: Evaluation - Due '''Friday (3/1/19)''' to Canvas
 
* Criterion E: Evaluation - Due '''Friday (3/1/19)''' to Canvas
 
** [http://xmltwo.ibo.org/publications/DP/Group4/d_4_comsc_tsm_1201_2/IA9en/Documentation/Crit_D_Evaluation.pdf Criterion E Example]
 
** [http://xmltwo.ibo.org/publications/DP/Group4/d_4_comsc_tsm_1201_2/IA9en/Documentation/Crit_D_Evaluation.pdf Criterion E Example]
Line 13: Line 12:
 
** You should basically ask in your feedback, suggestions for extending or enhancing the project.  Explain why each new development would be good.
 
** 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
 
** You should have at least 2 minor improvements and 2 major improvements
 +
* Work on your Internal Assessment today
  
 
== Thursday (2/21/19) ==
 
== Thursday (2/21/19) ==

Revision as of 23:30, 24 February 2019

Monday (2/25/19)

Agenda:

  • Criterion E: Evaluation - Due Friday (3/1/19) to Canvas
  • This criterion should be completed as two parts (headings)
  • Evaluation of the product (you should be able to do some of this by Friday)
    • 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
    • You should create a mini log or survey of the feedback results and eventually place it in the Appendix
  • Recommendations for the future development of the product (you should be able to do this by Friday)
    • 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
  • Work on your Internal Assessment today

Thursday (2/21/19)

Agenda:

Tuesday (2/19/19)

Agenda:

  • Criterion D: Functionality and extensibility of product
    • Functionality - Video of product functioning
      • Video (2–7 minutes in length) demonstrating the product
    • Extensibility of product - Assessed through design overview and, where appropriate, code listing.
      • Code should be clean, well-organized, well-designed, commented, good variables names, etc.
  • For Criterion D: turn in an outlined script of your video to Canvas
    • List the specific actions or functionalities of your program that you will test
    • Under each action / functionality, write out any narration that you will say while you demonstrate your program
    • Due Friday (2/22/19) in Canvas
  • [Resource management slides]
  • [Systems in organizations slides]
  • Work on Internal Assessment!

Thursday (2/14/19)

Agenda:

Tuesday (2/12/19)

Agenda:

Wednesday - Friday (2/6/19 - 2/8/19)

Agenda:

Monday (2/4/19)

Agenda:

Thursday (1/31/19)

Agenda:

  • Entertainment & Software Association Hackathon
    • Saturday, February 2nd, 2019 from 8AM-8PM
    • Registration due tomorrow
  • Boolean Logic quiz
    • In order to receive the access code, draw a truth table with 3 boolean variables (a, b, c) and all the F/T input permutations
  • Logic Gates
  • Logic Gates Quiz on Monday (2/4/19)
    • Be able to draw all the gates
    • Be able to draw a circuit based on a boolean expression
    • Be able to write a boolean expression based on a circuit
  • IA Work Session (most of your code should be completed by the end of January)

Tuesday (1/29/19)

Agenda:

Thursday (1/24/19)

Agenda:

  • Boolean Logic
  • IA Work Session (most of your code should be completed by the end of January)

Tuesday (1/22/19)

Agenda:

Homework:

  • Work on your IA! (most of your code should be completed by the end of January)

Thursday (1/17/19)

Agenda:

Homework:

  • Work on your IA!

Tuesday (1/15/19)

  • Snow Day

Friday (1/11/19)

Agenda:

  • Binary
    • Binary Quiz on Tuesday (1/15/19)
  • Internal Assessment Work Session(s)

Wednesday (1/9/19)

Agenda:

  • Data Structures Quiz in Canvas
  • Internal Assessment Work Session(s)

Monday (1/7/19)

Agenda:

  • Submit Criterion B documents to Canvas:
    • Record of Tasks
    • Flowcharts
    • Test Plan
  • Data Structures Quiz on Wednesday (1/9/19)
  • Internal Assessment Work Session(s)
    • CODE CODE CODE
    • Bring any materials you need to program your IA to class

Monday - Friday (12/31/18 - 1/4/19)

  • Winter Break

Archives

Retrieved from "https://www.paulbui.net/wiki/index.php?title=IB_Computer_Science_2&oldid=15173"