IB Computer Science 2

From WLCS
Revision as of 08:36, 21 February 2014 by Admin (talk | contribs)

Friday (2/21/14)

Agenda:

  • Internal Assessment - What's Left?
  • Appendix
    • Evidence of consultation with the client/advisor (transcription of consultation works)
    • Evidence of feedback from the client/advisor (transcription of feedback is ok)
    • Any additional documents or screenshots of the product functioning
  • Super-checklist rubric for all criteria
  • 2000 word max for the extended writing sections
  • Use of the provided IA Forms and templates
  • All written sections are saved as .odt files
  • Correct location and placement of the following:
    • Criteria A-E documentation should be located in the Documentation folder
    • Your video should be located in the Documentation folder as Criterion D
    • Your actual product should be located in the Product folder. The product should work as it sits in the folder.
    • Cover page
  • Filling out the cover page
    • Use relative links
    • Make sure you fill in every field
    • Link to a working copy of your product
  • Burn everything onto a CD

FINAL DEADLINE:

  • Monday, March 3rd, 2014

Wednesday (2/19/14)

Warmup:

  1. For each section, write at least one specific concerns or possible attack strategy
    1. Company website page on DoS attacks
    2. Guanjong High School
    3. Western Heights
    4. BYOD (Bring Your Own Device)
  2. We will use the entire's class list of attacks to test out each team's security plan

Agenda:

  • Network Security Plan Presentations
    1. Each team will present their plan
    2. We will test each plan by going over the class's list of attacks

Friday (2/14/14)

  • Snow Day

Monday - Wednesday (2/10/14 - 2/12/14)

Warmup:

  • Be sure that you have read the Case Study: Network Security - Media:IBCS_CaseStudy2014.pdf
    1. Begin preparing a Google document that has 4 sections:
      1. Company website page on DoS attacks
      2. Guanjong High School
      3. Western Heights
      4. BYOD (Bring Your Own Device)
    2. For each section, write at least one specific concerns or possible attack strategy
    3. We will use the entire's class list of attacks to test out each team's security plan

Agenda:

Thursday (2/6/14)

Agenda:

  • Criterion E: Evaluation - Due Monday (2/10/14)
  • This criterion should be completed as two parts (headings)
  • Evaluation of the product (you should be able to do some of this by Monday)
    • The evaluation of the product should refer directly to the success criteria in Criterion A, feedback from the client/adviser, as well as any other appropriate feedback obtained.
    • You should basically demo your product to multiple people and have them comment on each success criteria
  • Recommendations for the future development of the product (you should be able to do this by Monday)
    • The student will use the feedback and the evaluation of the specific performance criteria to recommend possible future developments to the product. These recommendations should explain the benefits of these developments.
    • You should basically ask in your feedback, suggestions for extending or enhancing the project. Explain why each new development would be good.
    • You should have at least 2 minor improvements and 2 major improvements
  • Case Study: Network Security - Media:IBCS_CaseStudy2014.pdf
    1. Highlight any/all special terms in your reading
    2. As you read, look up any terms that you do not understand or if you need more information
    3. We will break up into groups next week to simulate network security teams. Each team will address one of the scenarios in the Challenges Faced section at the end of Media:IBCS_CaseStudy2014.pdf
    4. Begin preparing a Google document that has 4 sections:
      1. Company website DoS attacks
      2. Guanjong High School
      3. Western Heights
      4. BYOD (Bring Your Own Device)
    5. For each section, list a bulleted description of 3 different concerns/possible attacks
  • Crash Course in Symmetric and Asymmetric Cryptography

Tuesday (2/4/14)

Agenda:

Friday (1/31/14)

Agenda:

  • Turn in Criterion D scripts (print it out)
  • Work on Terms & Definitions assignment
    • Due Tuesday (2/3/14) - Share with Mr. Bui
  • Work on finishing your IA project code!!

Wednesday (1/29/14)

Agenda:

  • Missing scores for NVCC Dual Enrollment
  • Introduction to Web Science
  • Work on Terms & Definitions assignment
    • Due Tuesday (2/3/14) - Share with Mr. Bui
  • Work on Criterion D
    • Script due Friday (1/31/14)

Monday (1/27/14)

Agenda:

  • Missing Networking Tests
  • Screenshot and screencasting software - Jing
  • 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)
  • Today's Assignment - Scripting your demo
    1. Outline the functionalities that you listed in your criteria for success in Criterion A
    2. Expand your outline with scripted lines and actions that explain and demo the different parts of your project
    3. You should be able to demonstrate each requirement/criteria you listed in Criterion A
    4. Time yourself and how long it takes to read the script at a moderate pace (You should aim for ~5 minutes)
    5. Print out and turn in your scripted outline by Friday (1/31/14)
  • Work on IAs...they should be close to completion.

Thursday (1/23/14)

Agenda:

  • Disappointing...missing Criterion Cs
  • Networking Test

Wednesday - Friday (1/15/14 - 1/17/14)

Agenda:

Monday (1/13/14)

Agenda:

  • Work on IA Criterion C
  • Partial Criterion C Drafts due Wednesday (1/15/14)
  • Test on Binary, Hexadecimal, and Data Representation on Wednesday (1/15/14)
  • Introduction to Networks

Tuesday - Thursday (1/7/14 - 1/9/14)

Agenda:

Archives

Retrieved from "https://www.paulbui.net/wiki/index.php?title=IB_Computer_Science_2&oldid=11090"