IB Year 1 Standard Level Computer Science
Thursday 1 September 2022 - Block 1
← previous note | most current note | next note →Daily Note
- Welcome!
- We will take attendance
- We will discuss our first formative quiz, covering objectives 1, 2 and 3.
- We will plan a date for our quiz
== NanoBot Company ==
- We will look at the data we gathered.
- Systems need a way to store data.
- what happens if we turn off the computer?
- what happens if we have multiple users who need to access the same data?
- Looks like we need to dip our toes into databases!
- we will also be exposed to ACID!!!!
- we will also be exposed to ACID!!!!
- We will learn about relational and non-relational databases
- We will learn about about database data types
- We will learn about erd diagrams (and here: ERD diagrams)
- We will construct ERD diagrams
- hint: click on shape library
- hint: click on the checkbox "Entity relationship"
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.
Statement of Inquiry
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:
- IF today == testing_day_for_me:
remember to go get tested!
- IF today == Friday:
current_event_activity()
Our learning
This is a beta feature. Please let me know if you have any feedback.
Please click here to reflect on our learning for today's class.