IB Year 2 Standard Level Computer Science

Tuesday 25 August 2020 - Block 8, Room C152
← previous note | most current note | next note →
 

Daily Note

Our first full week, yahoo!

Our big idea: 

  1. Programming knowledge and understanding

Zoom url: 

IF today IS  testing_day_for_me THEN remember to go get tested!

Our plan for the day: 

  1. Reminder: daily note
     
  2. We will review our homework 
     
  3. We will review: 
    1. Inputs and outputs
    2. Reading error messages in Python
    3. Variables
    4. Functions
       
  4. We will learn: 
    1. How cheat sheets can be very helpful
    2. Data types
    3. Slicing
    4. Selection (with a focus on comparision operators and the "in" keyword)
    5. Operators

Problem sets: 

  1. https://computersciencewiki.org/index.php/In_Flight_Entertainment
  2. https://computersciencewiki.org/index.php/Strings:_making_HTML_tags

If we have time, we will jump into control systems

 

A little less comfortable

Content

Programs must solve the problem they were create to solve. We can worry about how effieciently or elegantly they solve the problem later on; not right now. The content of a program entails input, processing and output. All three of these elements must be clearly observable. A key question you will be asked (and you should ask yourself) is: to what extent does your code implement the features required by the specification?  

Process

Within the process, we are looking at six guiding questions: 

  • To what extent is your code written well (i.e. clearly, efficiently, elegantly, and/or logically)?
  • To what extent is your code eliminating repetition?
  • To what extent is your code using functions appropriately?
  • To what extent is your code readable?
  • To what extent is your code commented?
  • To what extent are your variables well named?

Product

As opposed to content, this section we focus on how well you solved the problem. A key question here is to what extent is your code free of bugs?

 

A little more comfortable

Content

Programs must solve the problem they were create to solve. You should ask yourself "Am I solving this elegantly?". The content of a program entails input, processing and output. All three of these elements must be clearly observable, and we must see evidence of sanitizing input and raising exceptions.  A key question you will be asked (and you should ask yourself) is: to what extent does your code implement the features required by the specification?  

Process

Within the process, we are looking at six guiding questions: 

  • To what extent is your code written well (i.e. clearly, efficiently, elegantly, and/or logically)?
  • To what extent is your code eliminating repetition?
  • To what extent is your code using functions appropriately?
  • To what extent is your code readable?
  • To what extent is your code commented?
  • To what extent are your variables well named?

For those more comfortable programming, we expect succinct, secure and effecient problem solving. 

Product

As opposed to content, this section we focus on how well you solved the problem. A key question here is to what extent is your code free of bugs? The real difference here is the complexity of the problem you have chosen to solve and how well you solved it. 

Our Big idea

The big idea for today is Programming.

The essential questions for this topic are:

How do we plan, write, execute, and test instructions a computer can understand and process?

It takes time to explore and really understand a big idea. If you want to
learn more about programming (which is connected to today's daily note), please click here .

We are learning this because as a designers must understand scientific and technical innovation. Designers use systems, models, methods, and processes to solve problems.



Tags

 

Reminders & routines: