IB Computer Science II

From WLCS
Revision as of 09:53, 28 April 2010 by Admin (talk | contribs)

Friday (4/30/10)

  • Saturday (5/1/10) review session @ 1PM
  • Sunday (5/2/10) review session @ 9PM, Central Library! (free pizza & snacks)
  • Review Syllabus
    • Topic 3 - Computing system fundamentals
    • Topic 4 - Computer mathematics and logic

Wednesday (4/28/10)

  • Media:FurtherSystemFundamentals.ppt quiz
  • Self-grade Mock Paper 2
  • Review Syllabus
    • Topic 1 - Systems life cycle and software development
    • Topic 2 - Program construction in Java
  • Saturday (5/1/10) review session @ 1PM
  • Sunday (5/2/10) review session @ 9PM, Central Library! (free pizza & snacks)

Monday (4/26/10)

Thursday (4/22/10)

Tuesday (4/20/10)

Friday (4/16/10)

  • Mock IB Paper 1 exam
    • Please use a pencil
    • Write on your own paper, and do not write on the exam
    • Put your name at the top
    • Staple your papers together BUT NOT to the actual exam
    • Create two piles:
      1. Paper 1 exams
      2. Your answers
  • Quiz on Media:UtilitySoftware.ppt and Media:IntroCompArch.ppt on Tuesday (4/20/10)

Wednesday (4/14/10)

Warmup:

Agenda:

Thursday - Monday (4/8/10 - 4/12/10)

Warmup:

  • List all the different memories/storage devices from fastest to slowest
  • If programs don't fit in main memory, what happens next? (HINT: virtual memory)

Agenda:

Tuesday (4/6/10)

Warmup:

  • Please complete the following college acceptance survey

Agenda:

  • Boolean logic and DLD quiz
  • Bonus Computer Architecture quiz
  • Review Introduction to Computer Architecture
  • Return & Review Dossiers
    • Please allow Mr. Bui to KEEP your dossiers as examples
    • If you would like to have your dossier back, then talk to Mr. Bui

Thursday (3/25/10)

Tuesday (3/23/10)

Warmup:

  • Please complete the following survey

Agenda:

  • Turn in completed dossiers
    • Fill out IB coversheets (front and back)
    • Fill out Mr. Bui's checklist (front and back)
    • Binderclips for all

Monday - Friday (3/15/10 - 3/19/10)

  • Dossier - Conclusion due today
  • Dossier - User Manual (User Documentation) due Friday (3/19/10)
  • COMPLETED Dossier due next Tuesday (3/23/10)

Tuesday - Thursday (3/9/10 - 3/11/10)

Warmup:

  • An automated robot is used to cut shapes from steel sheets. If the robot's cutting blade becomes both hot and blunt the robot must stop so that the blade can cool and be resharpened. Sensors S1 (hot state) and S2 (blunt state) are attached to the blade to detect these states. Water from a container is used to keep the blade cool during cutting. If the water level falls below a certain point a sensor S3 detects this state and the robot stops irrespective of the other states. A logic circuit is required to control the robot so that it stops cutting when the appropriate states occur.
  • Create the Boolean table that represents the above logic

Agenda:

Friday (3/5/10)

Wednesday (3/3/10)

Warmup:

  • Gate diagrams

Agenda:

Monday (3/1/10)

Warmup:

  • Draw the gate diagram for Z = A+B*C
  • Draw the gate diagram for Z = AB + B'C
  • Draw the gate diagram for Z = (A+B)'C

Agenda:

Thursday (2/25/10)

Agenda:

  • Boolean expressions quiz
  • Turn in Usability and Handling Errors sections
  • Extra Credit: Sign up and help out with Gotta Gadget
    • March 9 from 4:30-6:30 at Central Library
  • Work on dossier - File I/O
  • Dossier - Success of Program due Monday (3/1/10)

Tuesday (2/23/10)

Warmup:

  • Add the two binary numbers together 00001111 and 00010101
  • Write out the 8-bit sign magnitude binary representation of -5?
  • Write out the 8-bit sign magnitude binary representation of -25?

Agenda:

  • Review Boolean expressions
  • On non-scratch paper, complete the Boolean expression exercises
  • Go over #1-5
  • Go over #6-10
  • Go over #11-15
  • Quiz on Boolean expressions Thursday (2/25/10)
  • Dossier - Usability & Handling Errors due Thursday (2/25/10)

Friday (2/19/10)

Warmup:

  • Cram for Quiz

Agenda:

Wednesday (2/17/10)

Warmup:

  • Convert the following 8-bit 2s complement numbers to decimal
    • 01101101
    • 11110101
  • Add the above numbers in binary

Agenda:

Tuesday (2/2/10)

Warmup:

Agenda:

Friday (1/29/10)

  • Take out all Dossier materials
  • We will go through each section of the checklist
  • Turn in all materials with checklist to Mr. Bui
  • Using MSWord to create professional-looking documents

Wednesday (1/27/10)

Warmup:

  • Why are digital signals "better" than analog signals?
  • How many bits are in a byte?
  • How many bytes are in a KB, MB, GB, TB?

Agenda:

  • NSF Field Trip! - Thursday (2/4/10)
  • Errors!
  • Dossier - Modular Organization due Friday (1/29/10)
  • BRING ALL YOUR DOSSIER MATERIALS ON FRIDAY
  • File Input/Output - reading and writing to files
  • Add writing to file to your LinkedList class
    1. Add a method named saveToFile(String filename)
    2. Open the filename for writing using RandomAccessFile
    3. writeUTF() the number of nodes or size of your LinkedList
    4. Create a loop that traverses the LinkedList and writeUTF() all of the nodes' data
  • If you want to add writing to file to a BinaryTree, then you must create recursive saveToFile() and saveToFileSubtree() methods that look like print() and printSubtree()

Monday (1/25/10)

Warmup:

  • Write down a list of ALL your classes
  • Draw a class hierarchy diagram that shows "has-a" relationships

Warmup:

  • Dossier - Modular Organization due Friday (1/29/10)
  • BRING ALL YOUR DOSSIER MATERIALS ON FRIDAY
  • File Input/Output - reading and writing to files
  • Add writing to file to your LinkedList class
    1. Add a method named saveToFile(String filename)
    2. Open the filename for writing using RandomAccessFile
    3. writeUTF() the number of nodes or size of your LinkedList
    4. Create a loop that traverses the LinkedList and writeUTF() all of the nodes' data
  • If you want to add writing to file to a BinaryTree, then you must create recursive saveToFile() and saveToFileSubtree() methods that look like print() and printSubtree()

Friday - Thursday (1/15/10 - 1/21/10)

  • Work on completing Dossier code

Wednesday (1/13/10)

Warmup:

  • List and describe the three types of test data
  • Look online and find out how many symbols are represented in ASCII
    • How many bits does the computer use for ASCII?

Agenda:

Monday (1/11/010)

  • 2nd Quarter Exam

Thursday (1/7/10)

Warmup:

  • What base is hexadecimal?
  • List the symbols used in hexadecimal
  • Convert 45 to binary and hexadecimal
  • Convert binary 101011101001 to hexadecimal

Agenda:

  • 2nd Quarter Exam will be next Monday (1/11/10) <- Binary 30!
    • Basic Java programming
    • Stacks
    • Queues
    • Linked Lists
    • Binary Trees
    • Software Development
    • Big-O algorithm evaluation
    • Binary
    • Hexadecimal
    • Binary Addition
    • Sign-Magnitude Negative Binary Numbers (?)
  • Turn in late Dossier: Algorithms section & peer review
  • Dossier update meetings
  • Media:BinaryAddition.ppt
  • Media:NegBinarySignMag.ppt
  • Work on Dossier! Code should be nearing completion at the end of next week

Tuesday (1/5/10)

Warmup:

  • Convert the following binary numbers to decimal:
    • 0001
    • 0011011
    • 010101
  • Convert the following decimal numbers to binary:
    • 3
    • 63
    • 14
  • List all the Big O complexities (Hint: O(1) is constant time)

Agenda:

  • Three-word winter break update
  • 2nd Quarter Exam will be next Monday (1/11/10) <- Binary 30!
  • Turn in Dossier: Algorithms section & peer review
  • Dossier update meetings
  • Introduction to Hexadecimal
  • Work on dossier!

Thursday (12/17/09)

Warmup:

Agenda:

Tuesday (12/15/09)

Agenda:

  • LLAddressBook? BTAddressBook?
  • Makeup Software Development Quiz
  • Algorithm Evaluation - Big O! - Media:AlgorithmEvaluation.ppt
  • Introduction to Binary - Media:Binary.ppt
  • Introduction to Binary #2 - Media:Binary2.ppt
  • Binary Games
  • Binary Quiz on Thursday (12/17/09)
  • Dossier Progress Check on Thursday (12/17/09)
    • You will demo / present completion of the following components in your dossier:
      • Basic container class (e.g. Contact)
      • Node class (e.g. ContactLLNode or ContactBTNode)
      • Partial completion of your major data structure (e.g. ContactLL or ContactBT)

Friday (12/11/09)

Warmup:

  • Finish cramming for software development quiz

Agenda:

  • Software Development Quiz! Yay!

Wednesday (12/9/09)

Warmup:

  • List the stages of the software development life cycle
  • List 3 different methods of data collection for the Analysis stage

Agenda:

  • Proper coding style
    • Program header at the very top
      • the program name
      • author, date, school
      • computer used, IDE used, purpose
    • Proper indentation
    • Proper line-wrapping (how to deal with LONG lines of code)
  • Demo missing work
  • Recursion Review
  • Software systems life cycle & software development
  • Work on the programming for your dossier

Homework:

  • Software development quiz on Friday (12/11/09)

Monday (12/7/09)

Warmup:

  • Illustrate the binary tree that is created when you insert the following values:
    • 24, 75, 4, 12, 98, 33, 0
  • Illustrate the binary tree that is created when you insert the following values:
    • Newman, Braden, Hines, Rawoot, Whelan, Luoma-Overstreet, Anderson, Apseloff

Agenda:

Homework:

  • Software development quiz on Friday (12/11/09)

Tuesday - Thursday (12/1/09 - 12/3/09)

Warmup:

  • Prepare to demo your BTAddressBook

Agenda:

  • BTAddressBook demos
  • Recursion Review
  • Dossier Review - Data Structures section
  • Dossier Programming - use this time in class to begin programming the classes you will use in your dossier
    • Create your basic container classes (e.g. Person, Schedule, Book, Order, Ticket, etc.). They should contain the following:
      • private attributes
      • default constructor
      • specific constructor
      • setters
      • getters
    • Create any classes that may contain these other classes (e.g. Library, AddressBook, etc.)
    • Using your prototype solution as a guide, you should begin creating the main menu system for your dossier.

Homework:

  • Dossier - Data Structures rough draft - due (Thursday 12/3/09)

Tuesday (11/24/09)

Agenda:

Homework:

  • Demo BinaryTreeAddressBook - due (Tuesday 12/1/09)
  • Dossier - Data Structures rough draft - due (Thursday 12/3/09)

Friday (11/20/09)

Agenda:

  • Demo your LinkedList AddressBook. It should be able to do the following:
    • add a Contact
    • print list of Contacts
    • find a Contact
    • sort list of Contacts
  • Re-Introduction to Binary Tree
  • Create 3 new classes called ContactBTNode, ContactBinaryTree, and ContactBTTestMain
  • Convert the 3 given binary tree classes to use Contacts instead of ints

Wednesday (11/18/09)

Warmup:

  • What is the algorithm for a linear search?
  • What is the algorithm for a selection sort?
  • What is the algorithm for a bubble sort?

Agenda:

  • int find(String fn, String ln) in the ContactLinkedList
    • Add the find() option to your AddressBookMain and AddressBook
    • find() in the AddressBook should use the ContactLinkedList's find() and then ContactLinkedList's getContact()
  • void selectionSort() in the ContactLinkedList
  • You should move the bubbleSort() into the ContactLinkedList and complete the method yourself
  • Removing a Contact
    • Add a remove option to your AddressBookMain
    • Create a remove(String fn, String ln) method in your AddressBook
    • In the method, use the ContactLinkedList's find() method to get the index of the Contact
    • Check if the index is valid (not the error code), and if so, then use the ContactLinkedList's remove() method using that index
  • Demo a completely working AddressBook

Monday (11/16/09)

Warmup:

  • Open your Contact class and review the code

Agenda:

  • Contact class review as a class
  • Create a new class from your Node class and called ContactNode
    • Do this as a class...quickly
  • Create a new class called ContactLinkedList
    • Do this as a class...quickly
  • Convert your LinkedList to use ContactNode and call it ContactLinkedList
    • Go through one or two examples as a class
  • Be sure to test your ContactLinkedList
  • AddressBook class review as a class
  • Convert your AddressBook to use ContactLinkedList instead of an array
    • Comment out the parts for find(), selectionSort(), and bubbleSort(). We will convert these later
    • Be sure to test your AddressBook with LOTS of contacts

Homework:

  • Complete the AddressBook conversion over to ContactLinkedList by Wednesday (11/18/09)
  • Be ready to demo your AddressBookMain

Thursday (11/12/09)

Agenda:

  • Abstract data types review
  • Introduction to Binary Tree
  • Demo your LinkedList
  • Contact class review
  • Create a new class from your Node class and called ContactNode
  • Create a new class called ContactLinkedList
  • Convert your LinkedList to use ContactNode and call it ContactLinkedList
  • Be sure to test your ContactLinkedList
  • AddressBook class review
  • Convert your AddressBook to use ContactLinkedList instead of array
    • Comment out the methods for find(), selectionSort(), and bubbleSort(). We will convert these later
    • Be sure to test your AddressBook with LOTS of contacts

Monday (11/9/09)

Agenda:

  • Turn in homework
  • Demo DynamicQueue
  • Introduction to Linked Lists
    • Media:LinkedList.java
    • Attributes: head, tail, size
    • Constructors: default
    • Methods:
      • isEmpty() - returns true if the LinkedList is empty, and false otherwise
      • void add(int num) - adds a new Node with num at the end of the LinkedList
      • void add(int num, int index) - adds a new Node with num at the index specified
        • There are FIVE different scenarios when you add a Node
        • DRAW the before-and-after pictures for all FIVE secenarios
      • int remove(int index) - removes the index-th Node and returns its data
        • There are SIX different scenarios when you remove a Node
      • print() - traverses the LinkedList and prints out each Node's data
    • Create a main method to test out all the methods and scenarios of LinedList

Homework:

  • Complete the LinkedList class and all its methods by the beginning of class on Thursday (11/12/09)
  • Mr. Bui will give you his LinkedListMain on Thursday to test

Thursday (11/5/09)

Warmup:

  • Draw the before-and-after pictures for adding a Node to an empty Queue (be sure to use head and tail!)
  • Draw the before and after pictures for adding a Node to a non-empty Queue
  • Draw the before-and-after pictures for removing a Node from an empty Queue
  • Draw the before and after pictures for removing a Node from a non-empty Queue

Agenda:

  • Return 1st Quarter Exams
  • Dynamically-sized Queues
    • Create a new class called DynamicQueue
    • Test out your DynamicQueue using the original QueueMain file
  • Introduction to Linked Lists
    • Media:LinkedList.java
    • Attributes: head, tail, size
    • Constructors: default
    • Methods:
      • isEmpty() - returns true if the LinkedList is empty, and false otherwise
      • void add(int num) - adds a new Node with num at the end of the LinkedList
      • void add(int num, int index) - adds a new Node with num at the index specified
        • There are FIVE different scenarios when you add a Node
        • DRAW the before-and-after pictures for all FIVE secenarios
      • int remove(int index) - removes the index-th Node and returns its data
        • There are SIX different scenarios when you remove a Node
      • print() - traverses the LinkedList and prints out each Node's data

Homework:

  • Complete DynamicQueue!
  • Draw the before-and-after diagrams (all SIX scenarios) for the LinkedList's remove() method

Monday (11/2/09)

Warmup:

  • Assume that you have allocated memory for a new int array of 10000 elements. An int is 32-bits in size, and there are 8-bits in 1 byte. How many bytes of memory are you taking up?
  • If there are 1024 bytes in a kilobyte, how many kilobytes are you taking up?

Agenda:

  • Dynamically-sized Stacks
    • Create a new class called DynamicStack
    • What attribute must we keep track of when we talk about stacks?
    • Create a Node reference for the most important stack attribute
    • Implement push(int num) using Nodes.
      • push() should not return anything
      • push() creates a new Node with the num, and set the new Node's next reference to the top
      • Don't forget to update the top to be the new node!
    • Implement pop(), which should POP and return the value on top of the stack and update the top
    • Implement top(), which should just return the value on top of the stack
    • Implement isEmpty() which returns true if the stack is empty
    • Implement print() which should print your entire stack
    • TEST YOUR STACK USING MR. BUI'S STACK MAIN OR YOUR OWN MAIN METHOD

Thursday (10/29/09)

  • 1st Quarter Exam

Tuesday (10/27/09)

Warmup:

  • Pass in your Prototype Solution to Mr. Bui
  • Given the following code, draw the memory diagram:
Node fun = new Node(42);
Node general = new Node (11);
Node a, b, c;

a = general;
b = a;
fun.next = b;
c = fun;

Agenda:

  • Pass back Stacks quiz
  • Prototype Solution peer review
  • 1st Quarter Exam Review
    • Java programming
    • class construction
    • methods
      • components of the method header
    • Stacks
      • how they work
      • operations: push(), pop(), top(), isEmpty()
      • why we use them
      • example uses
    • Queues
      • how they work
      • operations: add(), remove(), head(), tail(), isEmpty()
      • why we use them
      • example uses
    • Nodes and reference variables
      • Memory diagram and tracing code

Friday (10/23/09)

Agenda:

Homework:

  • Dossier - Prototype Solution rough draft due Tuesday (10/27/09)

Wednesday (10/21/09)

Warmup:

  • Give 2 specific examples of when a queue should be used
  • Identify the following parts in each of the method declarations: access type, return type, method name, parameters
    • public int getSize()
    • private String whatNot(String whatFor)
    • public void print(int size, String stuff)

Agenda:

Homework:

  • Dossier - Prototype Solution rough draft due Tuesday (10/27/09)

Monday (10/19/09)

Warmup:

  • What does LIFO stand for?
  • What does LIFO describe?
  • When would you want a LIFO?

Agenda:

Homework:

  • Dossier - Criteria for Success rough draft due Wednesday (10/21/09)
  • Turn in late assignments! Examples: AddressBook sorting, Problem Analysis, etc.

Thursday (10/15/09)

Warmup:

  • Demo any missing work
  • Finish adding bubble sort and selection sort to your AddressBook
    • Hint1: You cannot simply compare Contacts, but you can compare their last names
    • Hint2: You cannot sort the ENTIRE Contact array, you can only sort the ones that you have added
    • Hint3: You should test our the sorting methods by adding a (s)ort option to your AddressBookMain

Agenda:

Homework:

  • Stacks quiz on Monday (10/19/09)
  • Dossier - Criteria for Success rough draft due Wednesday (10/21/09)
  • Turn in late assignments! Examples: AddressBook sorting, Problem Analysis, etc.

Tuesday (10/13/09)

Warmup:

  • Please complete this password request form
  • What are the advantages and disadvantages of the binary search algorithm?

Agenda:

  • Dossier peer review - Analysis of the Problem
  • Demo any missing work
  • Sorting & Searching Review
    • Selection Sort
    • Bubble Sort
    • Linear Search
    • Binary Search
  • Examples of using the String.compareTo() method
  • Fix Media:StringBinarySearch.java such that it uses binary search to find a String. Hint: You will be using the compareTo()
  • Demo StringBinarySearch to Mr. Bui by the end of today.
  • You should then add selectionSort() to your AddressBook class. It sorts your AddressBook Contact array by last name using the selection sort algorithm. You may assume that everybody will have a different last name.
  • You should then add bubbleSort() to your AddressBook class. It sorts your AddressBook Contact array by last name using the bubble sort algorithm. You may assume that everybody will have a different last name.
  • Demo the two sorting methods to Mr. Bui before Thursday.
  • Read through Media:CriterionA2_criteriaforSuccess.doc
  • Begin working on your Criteria for Success. It will be due next Wednesday (10/21/09).

Thursday (10/8/09)

Warmup:

  • Given the array of integers: 3, 6, 2, 7, 9, 5, 2, 3
  • Illustrate the bubble sort algorithm to sort the numbers

Agenda:

  • Introduction to Linear Search
  • Download Media:LinearSearch.java
  • Fill in the commented parts of LinearSearch.java and demo a working linear search to Mr. Bui
  • Linear Search performance evaluation
  1. What is the best case scenario? i.e. What is the minimum # of comparisons?
  2. What is the worst case scenario? i.e. What is the maximum # of comparisons?
  3. What is the average # of comparisons?
  4. Can we do better than a linear search?
  • Introduction to Binary Search
  1. Assume sorted list
  2. Go to the middle point
  3. If the middle element matches the key, then the search is over
  4. If the key is less than middle element, go to the left (down), else go to the right (up)
  5. Repeat steps 2-4 until the key is found or when the left and right bounds pass each other
  1. What is the best case scenario? i.e. What is the minimum # of comparisons?
  2. What is the worst case scenario? i.e. What is the maximum # of comparisons?
  3. What is the average # of comparisons?
  • Binary Search Advantages & Disadvantages

Homework:

  • 1st rough draft of Analysis of the Problem due Tuesday (10/13/08)
  • Any missing assignments (e.g. AddressBook, SelectionSort, BubbleSort)

Tuesday (10/6/09)

Warmup:

  • Upload AddressBook.java and AddressBookMain.java to SchoolWebLockers
  • Demo SelectionSort.java to Mr. Bui
  • Turn in your Dossier idea sentence

Agenda:

  • Introduction to Bubble Sort
  1. Initialize the front to be the top or beginning of the array
  2. Now go to the bottom/end of the array
  3. Compare the two adjacent elements to see if they are in proper sequential order
    1. Swap the elements if they are out of order (bigger number to the left of smaller number)
  4. Move to the next pair of adjacent elements/numbers
  5. Repeat steps 3 and 4 until the smallest number has "floated" to the top/front
  6. After you traverse the entire array
    1. Move the front so that the sorted numbers are ignored
    2. Go back to the end of the array
    3. Repeat steps 2 through 6 for the unsorted part of the array
  • Bubble Sort Animation
  • Download Media:BubbleSort.java
    • Fill in the commented parts of the BubbleSort.java file. Where there is a comment, you need to write code.
    • Demo to Mr. Bui at the end of class or at the beginning of class tomorrow
  • Introduction to Program Dossier

Friday (10/2/09)

Warmup:

  • Swapping elements warmup

Agenda:

Homework:

Archives