Difference between revisions of "IB Computer Science 2"

From WLCS
Line 3: Line 3:
 
* Criterion C draft due '''Thursday (2/13/20)'''
 
* Criterion C draft due '''Thursday (2/13/20)'''
 
* [https://drive.google.com/open?id=1L3Q5lyOuhCFtWtzIvz0F5mIExsqrIodkhXN8e9n4vc4 Control Systems]
 
* [https://drive.google.com/open?id=1L3Q5lyOuhCFtWtzIvz0F5mIExsqrIodkhXN8e9n4vc4 Control Systems]
* Criterion D
+
* Criterion D end of this week / beginning of next
* Case Study
+
* Criterion E end of February
 +
* Assemble IA first week of March
 +
* Turn in final IA March 9ish
 +
* Read [[Media:IBCS_CaseStudy2020.pdf]] by '''Monday (2/17/20)'''
  
 
== Monday - Friday (2/3/20 - 2/7/20) ==
 
== Monday - Friday (2/3/20 - 2/7/20) ==

Revision as of 11:24, 11 February 2020

Tuesday (2/11/20 )

Agenda:

  • Criterion C draft due Thursday (2/13/20)
  • Control Systems
  • Criterion D end of this week / beginning of next
  • Criterion E end of February
  • Assemble IA first week of March
  • Turn in final IA March 9ish
  • Read Media:IBCS_CaseStudy2020.pdf by Monday (2/17/20)

Monday - Friday (2/3/20 - 2/7/20)

Agenda:

  • Criterion C review - ~1000 words
    • Screenshots of code
    • Extended writing (short paragraphs) that...
      • describes how your code implements the advanced programming technique
      • justifies the use of the technique (why did you use that advanced programming technique?) -- advantages of doing so and disadvantages of not doing so (or doing something different)
    • Citations / Bibliography to any external resources that you used (required!)
    • ~200 words per advanced programming technique
    • Draft due in Canvas by Thursday (2/13/20)
  • Systems in organizations
  • System design basics
  • Usability Assignment
    1. Find a software application example of "good" usability (you may not use an example stated in class)
    2. State the software application and the specific feature
    3. Identify the usability rule that it implements
    4. Display a screenshot of the application's implementation of the rule
    5. Briefly describe how that feature implements that particular usability rule
    6. Repeat the above with an example of "bad" usability
    7. Submit to Canvas

Wednesday (1/29/20)

Agenda:

  • Criterion C Outline Meetings
  • Continue working on your IA code!

Homework:

  • Work on your IA code!

Monday (1/27/20)

Agenda:

  • Read thoroughly the Criterion C description AND rubric found in Media:IBCS_InternalAssessmentGuidelines.pdf
  • Review Criterion C examples in IA Examples
  • Criterion C - Major techniques list
    1. Create a list of at least 6 techniques used in developing the product
    2. "The techniques may include algorithmic thinking, data structures, software tools and user interface. This list need not be exhaustive but should illustrate how the major components of the product were developed." (IB)
    3. Example techniques some people may have:
      • graphical user interface
      • specific search algorithms
      • specific sorting algorithms
      • 3rd-party libraries
      • object-oriented programming
      • file reading and writing
      • recursion
      • version and source control (e.g. git)
      • networking
      • client-server communication
      • ...any many more!
    4. Within each technique, write a sub-bullet point description of how you have employed that technique in your IA
    5. Submit to Canvas
  • Continue working on your IA code!

Homework:

  • Work on your IA code!

Thursday - Thursday (1/16/20 - 1/23/20)

Agenda:

  • IA Progress Checks
  • Work on your IA code!

Homework:

  • Work on your IA code!

Tuesday (1/14/20)

Agenda:

Homework:

  • Work on your IA code!
  • Work on your IA code!
  • Work on your IA code!

Friday (1/10/20)

Agenda:

  • Code Progress Check #2
  • Work on IA code

Wednesday (1/8/20)

Agenda:

Homework:

  • Work on your IA code!
  • Work on your IA code!
  • Work on your IA code!

Monday (1/6/20)

Agenda:

  • CSTA/ACM Cutler-Bell Scholarship
  • Internal assessment timeline updates
    • Complete code by the end of January
    • Write Criterion C by mid-February
    • Record Criterion D around mid-February
    • Demonstrate and obtain feedback from client or adviser near end of February
    • Write Criterion E end of February
    • Assemble and turn in IA early/mid-March
  • Complete Network fundamentals
  • Data transmission

Homework:

  • Work on your IA code!
  • Work on your IA code!
  • Work on your IA code!

IBCS2 - 1920 - December

IBCS2 - 1920 - November

IBCS2 - 1920 - October

IBCS2 - 1920 - September

IBCS2 - Archives