Difference between revisions of "IB Computer Science 2"
From WLCS
Line 1: | Line 1: | ||
+ | == Thursday (2/2/17) == | ||
+ | '''Agenda:''' | ||
+ | * Logic Gates w/ Truth Tables Quiz | ||
+ | * Criterion D - Functionality and extensibility of product | ||
+ | ** This criterion should be completed as two parts and '''does not require any additional written documentation'''. | ||
+ | ** '''Functionality of the product''' | ||
+ | *** The student must use the video to demonstrate the product functioning (2-7 minutes in length). This evidence will be supported, where possible, by the product on the CD-ROM/DVD or USB. | ||
+ | *** i.e. demo the your program's functionality | ||
+ | ** '''Extensibility of product''' | ||
+ | *** The student should design the product so that it can be maintained by another party and/or be further developed. Therefore the design of the product should include appropriate folder and data structures, intuitive file and/or class naming conventions and, where appropriate, comments in the code. | ||
+ | *** i.e. your program should be well-organized (good filenames, clean code, good variable names, comments) | ||
+ | * Assignment - Scripting your demo | ||
+ | *# Outline the functionalities that you listed in your criteria for success in Criterion A | ||
+ | *# Expand your outline with scripted lines and actions that explain and demo the different parts of your project | ||
+ | *# You should be able to demonstrate each requirement/criteria you listed in Criterion A | ||
+ | *# Time yourself and how long it takes to read the script at a moderate pace (You should aim for ~5 minutes) | ||
+ | *# Turn in your scripted outline via Google Classroom by '''Thursday (2/9/16)''' | ||
+ | |||
== Friday - Tuesday (1/27/17 - 1/31/17) == | == Friday - Tuesday (1/27/17 - 1/31/17) == | ||
'''Agenda:''' | '''Agenda:''' |
Revision as of 14:34, 2 February 2017
Contents
Thursday (2/2/17)
Agenda:
- Logic Gates w/ Truth Tables Quiz
- Criterion D - Functionality and extensibility of product
- This criterion should be completed as two parts and does not require any additional written documentation.
- Functionality of the product
- The student must use the video to demonstrate the product functioning (2-7 minutes in length). This evidence will be supported, where possible, by the product on the CD-ROM/DVD or USB.
- i.e. demo the your program's functionality
- Extensibility of product
- The student should design the product so that it can be maintained by another party and/or be further developed. Therefore the design of the product should include appropriate folder and data structures, intuitive file and/or class naming conventions and, where appropriate, comments in the code.
- i.e. your program should be well-organized (good filenames, clean code, good variable names, comments)
- Assignment - Scripting your demo
- Outline the functionalities that you listed in your criteria for success in Criterion A
- Expand your outline with scripted lines and actions that explain and demo the different parts of your project
- You should be able to demonstrate each requirement/criteria you listed in Criterion A
- Time yourself and how long it takes to read the script at a moderate pace (You should aim for ~5 minutes)
- Turn in your scripted outline via Google Classroom by Thursday (2/9/16)
Friday - Tuesday (1/27/17 - 1/31/17)
Agenda:
- Turn in a hard-copy of Criterion C
- Boolean Logic & Logic Gates
- Logic Gates w/ Truth Tables Quiz on Thursday (2/2/17)
- Be able to draw all the logic gates AND their truth tables
- Non-IB Interesting stuff:
- Media:NandGateUsage.gif
- MOSFETs (Metal Oxide Semiconductor Field Effect Transistor)
- N-type vs P-type
- CMOS (Complementary Metal Oxide Semiconductor)
Monday - Wednesday (1/23/17 - 1/25/17)
Agenda:
- ACM Capital Region Celebration of Women in Computing
- February 24-25th @ Georgetown University
- Work on Internal Assessment
- Criterion C Draft due Friday (1/27/17)
- Review in detail, Criterion C rubric
- Review Criterion C requirements found in Media:IBCS_InternalAssessmentGuidelines.pdf
- Review IA examples
Wednesday (1/18/17)
Agenda:
- Computer Architecture & Operating Systems Quiz
- Work on Internal Assessment!
- Criterion C Draft due Friday (1/27/17)
- Review in detail, Criterion C rubric
- Review Criterion C requirements found in Media:IBCS_InternalAssessmentGuidelines.pdf
- Review IA examples
Friday (1/13/17)
Agenda:
- Introduction to Operating Systems
- Computer Architecture & Operating Systems Quiz on Wednesday (1/18/17)
- Work on Internal Assessment!
- Criterion C Draft due Friday (1/27/17)
- Review in detail, Criterion C rubric
- Review Criterion C requirements found in Media:IBCS_InternalAssessmentGuidelines.pdf
- Review IA examples
Wednesday (1/11/17)
Agenda:
- Hardware Quiz
- Criterion C Draft due Friday (1/27/17)
- Review in detail, Criterion C rubric
- Review Criterion C requirements found in Media:IBCS_InternalAssessmentGuidelines.pdf
- Review IA examples
- Finish Introduction to Computer Architecture
- Introduction to Operating Systems
Monday (1/9/17)
Agenda:
- Media:Hardware.pptx
- Hardware Quiz on Wednesday (1/11/17)
- Be able to identify the hardware part
- Acronyms should be completely written out
- High-level vs. Low-level
- Introduction to Computer Architecture
Thursday (1/5/17)
Warmup:
- Turn in your Criterion C lists
Agenda:
- Binary & Hexadecimal quiz
- Data Representation
- Software vs. Hardware
- Computer Science, Computer Engineering, Electrical Engineering
- Media:Hardware.pptx
Tuesday (1/3/17)
Agenda:
- Internal Assessment meetings this Thursday (1/5/17)
- Have a 5-6 bulleted list of your "programming techniques" that you will write about in your Criterion C
- Introduction to Number Systems
- Binary & Hexadecimal quiz on Thursday (1/5/17)
- Data Representation
Homework:
- Study for Binary & Hexadecimal quiz
- Criterion C bulleted list