Difference between revisions of "IB Computer Science 2"

From WLCS
Line 12: Line 12:
 
* UML Class Diagrams Activity & Assignment:
 
* UML Class Diagrams Activity & Assignment:
 
*# Read [[Media:UML_Diagrams.pptx]]
 
*# Read [[Media:UML_Diagrams.pptx]]
*# Read part of [https://www.ibm.com/developerworks/rational/library/content/RationalEdge/sep04/bell/ UML Basics: The Class Diagram] (see note below)
+
*# Read [https://www.ibm.com/developerworks/rational/library/content/RationalEdge/sep04/bell/ UML Basics: The Class Diagram] (see note below)
 
*#* You only need to read about the class name, class attribute list, and class operators (methods) list
 
*#* You only need to read about the class name, class attribute list, and class operators (methods) list
 
*# You will use [https://www.draw.io/ draw.io] to create UML class diagrams.  The UML tools are on the left side of the draw.io editor
 
*# You will use [https://www.draw.io/ draw.io] to create UML class diagrams.  The UML tools are on the left side of the draw.io editor

Revision as of 06:59, 22 March 2017

Wednesday (3/22/17)

Agenda:

Monday (3/20/17)

Warmup:

  1. Click on your class period's terms presentation below
  2. Go to your term's slide and insert your material
  3. Do *not* change the order of the slides

Agenda:

Thursday (3/16/17)

Agenda:

  • Turn in your Internal Assessment via Google Classroom if you have not already done so!
  • Read the Media:IBCS_CaseStudy2017.pdf
    • You may print a hard-copy if you prefer one
    • Highlight or note any words or terms with which you are unfamiliar
  • Case Study Slide Assignment
    1. Go to Google Classroom to find your assigned case study term
    2. Each person will create a presentation slide to present their assigned term
    3. Be sure to include the following:
      • Definition: What does the term mean or do?
      • Describe: How does it work?
      • Image or graphic to help explain/describe the term
      • Why should we care? (why is it useful?)
    4. Submit your slide via Google Classroom

Tuesday (3/14/17)

  • Winter Storm Stella Snow Day

Internal Assessment Final Deadline: Monday (3/13/17)

  • Note, this is not an L day, but you will be able to electronically submit to Google Classroom
  • The submission will be a zip file (archiving all the IA folders and files)

Wednesday - Friday (3/8/17 - 3/10/17)

Agenda:

  • Teen Tech Help @ Central Library, Thursday (3/9/17), 3:30-5pm
    • Volunteer to help adults solve their tech problems
    • Easy service hours!
    • Mr. Bui will provide pizza
  • Senior Experience Opportunity
    • Reid Goldstein & Carolyn Carlson
    • 15-20 hrs for each per week (30-40 hrs total/wk)
    • MS Excel, proficient typing and moderate-to-advanced computer skills
  • Criterion D Update!
  • Anonymization Guidelines
    • No full names -- use initials only (on coverpage and any criteria)
  • Work on you Internal Assessment
    • See Monday (3/6/17) for final assembly instructions

Monday (3/6/17)

  • 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 Media:IBCS_IA_Forms.zip and templates
    • All written sections are saved as .pdf 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
    • Zip everything and submit electronically
  • IA Assembly Guidelines - DUE MONDAY (3/13/17)
  1. Prepare access to all your electronic copies of your documents and project
  2. Download Media:IBCS_IA_Forms.zip and move the folder to your desktop
  3. Move all your solution (actual code) files to the Product folder
  4. Complete the coversheet
  5. Move your Criterion sections PDFs into the Documentation folder
  6. Delete files in Documentation that are not necessary
  7. Edit links in the coversheet
    1. Copy the file name in the coversheet and paste/rename each of your criterion PDFs
    2. Rename your Criterion D video using the same naming convention -- edit the link in the coversheet
    3. Add links to any appendices -- evidence of initial consultation and feedback should be here
  8. Open your coversheet in a web browser and double-check every field and click on every link.
  9. Be sure to edit/correct the word count
  10. Highlight the coversheet, Documentation, and Product folders -- right-click and create a zip archive or compress (Mac) or send to compressed file (Windows)
  11. Zip file naming convention: LastName_IA.zip
  12. Send the zip file to another computer, click on every link, and test it out
  13. Once everything has been double-checked. Submit the zip file to Google Classroom

Thursday (3/2/17)

Agenda:

  • Criterion E: Evaluation - Due Friday (3/3/17) to Google Classroom
  • Senior Experience Opportunity
    • Reid Goldstein & Carolyn Carlson
    • 15-20 hrs for each per week (30-40 hrs total/wk)
    • MS Excel, proficient typing and moderate-to-advanced computer skills
  • System design basics - Media:SystemDesignBasics.pptx

Friday - Tuesday (2/24/17 - 2/28/17)

Agenda:

  • Criterion E: Evaluation - Due Friday (3/3/17) to Google Classroom
  • 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
  • System Fundamentals

Wednesday (2/22/17)

Agenda:

  • Criterion E: Evaluation - Due Friday (3/3/17) to Google Classroom
  • 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
  • Networks

Monday - Friday (2/13/17 - 2/17/17)

Agenda:

Homework:

  • Complete and cleanup your IA code
  • Don't forget that it should be organized, good variables names, and comments

Thursday (2/9/17)

Agenda:

Homework:

  • Complete and cleanup your IA code
  • Don't forget that it should be organized, good variables names, and comments

Tuesday (2/7/17)

Agenda:

  • Return quizzes and Criterion C
  • Boolean expression word problems
    • Take out paper and complete the problems listed
  • Work on Criterion D Script - due to Google Classroom by Thursday (2/9/16)

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
    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. Turn in your scripted outline via Google Classroom by Thursday (2/9/16)

Archives