IB Year 1 Higher Level Computer Science

Monday 13 September 2021 - Block 4, Room C152
← previous note | most current note | next note →
 

Daily Note

  1. We will review our big ideas from our last class. Today is Friday, so we have current events!
     
  2. We will break into two groups
     
    1. more comfortable with Python
    2. less comfortable with Python
       
  3. We will discuss two different interfaces to working with a computer operating system:
    1. GUI - graphical user interface
    2. CLI - command line interface
       
  4. If you are less comfortable with Python
    1. Please bookmark this link
    2. Please bookmark this link
    3. Watch this first, and follow all directions
    4. Watch this second and follow all directions
    5. Please create some windows using this cookbook and design patterns
       
    6. I expect you to physically sit next to our students in the less-comfortable group and walk them through creating a gui. 
       
    7. We will return to objectives and problem sets in our next class
       
  5. We will review our learning

 

 

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.



Reminders & routines:

Please read and follow these reminders:

  1. IF today ==  testing_day_for_me:
         remember to go get tested!
     
  2. IF today == Friday:
         current_event_activity()