Ask For help

Class wiki

Github

LMS

Class syllabus

All notes for this course

IB Year 1 Standard Level Computer Science

Thursday 15 September 2022 - Block 1
← previous note | most current note | next note →
 

Daily Note

Hello, 

Let's review objective 5. 

== NanoTech Company == 

I'm still working on the database setup for our nanotechnology company. 

But you should know enough to develop a simple text-based application where we can enter a new employee into our system.

  1. Please start by getting this code and spend some time understanding it.
  2. create a menu choice for creating a new employee
  3. design and construct a system to collect the following input:
    1. first name
    2. last name
    3. second last name
    4. Each input should have basic validation / sanitization 
  4. We are going to stop for a moment and reflect on an obvious problem; when we end our program, our data will be erased!
    1. We will learn about working with files
    2. We will create a system for saving new employees to a file
  5. We will then conitnue wokring to build a system which includes almost every question we have mapped for our new employee (see classroom whiteboard)
     

We will work objective 6 with whatever time is left. 

More comfortable with software engineering, please work the two following problem sets: 

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

 

 

 

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.



Tags

grade_11

 

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()

 

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.