IB Computer Science 2
From WLCS
Contents
- 1 Thursday (3/5/20)
- 2 Monday - Friday (2/24/20 - 2/28/20)
- 3 Thursday (2/20/20)
- 4 Tuesday (2/18/20)
- 5 Thursday (2/13/20)
- 6 Tuesday (2/11/20 )
- 7 Monday - Friday (2/3/20 - 2/7/20)
- 8 IBCS2 - 1920 - January
- 9 IBCS2 - 1920 - December
- 10 IBCS2 - 1920 - November
- 11 IBCS2 - 1920 - October
- 12 IBCS2 - 1920 - September
- 13 IBCS2 - Archives
Thursday (3/5/20)
Agenda:
- Full IA will be due 8AM - Friday (3/13/20) on Canvas!
- What to expect in Canvas to submit your IA...
- Individual criterion sections that must have submissions (A through E)
- Project code uploaded as a single zip (required)
- Appendix (optional)
Monday - Friday (2/24/20 - 2/28/20)
Warmup:
- Read Media:IBCS_CaseStudy2020.pdf
- Be prepared to organize terms by categories
- Terms will eventually be drafted
Agenda:
- Criterion E draft due Friday (2/28/20)
- Full IA will be due 8AM - Friday (3/13/20)
- All components will need to be submitted: A, B, C, D, E, and the project code itself
- Case study terms categories
- Case study terms draft
Thursday (2/20/20)
Warmup:
- Watch Common Craft: Blockchain
Agenda:
- Reminder: Setup your evaluation meeting with your client/advisor
- Criterion E draft due Friday (2/28/20)
- Full IA will be due 8AM - Friday (3/13/20)
- All components will need to be submitted: A, B, C, D, E, and the project code itself
- Complete Usability assignment (Canvas) today
- Work on IA
Tuesday (2/18/20)
Agenda:
- IA Work Day
- Criterion E: Evaluation
- Begin trying to schedule an evaluation meeting w/ your client and/or advisor
Thursday (2/13/20)
Agenda:
- Criterion C drafts are due to Canvas today
- We will revisit Usability topic and assignment as a class when Mr. Bui is back
- Criterion D script outline is due by the end of the period
- Your eventual video will be 5-7 minutes in length. Less than 5 minutes is allowed, but you should ask yourself why it's so short
- List the specific actions or functionalities of your program that you will test. These should be your success criteria
- For each of your actions, state your narration or the specific action you will perform as you are demonstrating your program
- You should also demonstrate any error-handling that your program can do
- This is your time to show off your IA for complexity points
- Turn your outline into Canvas by the end of class
- Read Media:IBCS_CaseStudy2020.pdf by Monday (2/17/20)
Tuesday (2/11/20 )
Agenda:
- Criterion C draft due Thursday (2/13/20)
- Control Systems
- Criterion D end of this week / beginning of next
- Criterion E end of February
- Assemble IA first week of March
- Turn in final IA March 9ish
- Read Media:IBCS_CaseStudy2020.pdf by Monday (2/17/20)
Monday - Friday (2/3/20 - 2/7/20)
Agenda:
- Criterion C review - ~1000 words
- Screenshots of code
- Extended writing (short paragraphs) that...
- describes how your code implements the advanced programming technique
- justifies the use of the technique (why did you use that advanced programming technique?) -- advantages of doing so and disadvantages of not doing so (or doing something different)
- Citations / Bibliography to any external resources that you used (required!)
- ~200 words per advanced programming technique
- Draft due in Canvas by Thursday (2/13/20)
- Systems in organizations
- System design basics
- Usability Assignment
- Find a software application example of "good" usability (you may not use an example stated in class)
- State the software application and the specific feature
- Identify the usability rule that it implements
- Display a screenshot of the application's implementation of the rule
- Briefly describe how that feature implements that particular usability rule
- Repeat the above with an example of "bad" usability
- Submit to Canvas