Monthly
Schedule
(AP
Computer Science A, Period F)
Th
11/1/012 |
HW due: Read Lesson 25;
write the “Student Averages” project on p. 25-5. |
|
F 11/2/012 |
HW due: Read Lesson 26 and
Appendix F; write the project on p. 26-2 with the additional modification
that the program should take an existing text file that resembles the sample
output given on p. 26-2, and then append new output with a line that says
“REVISED STATISTICS:” followed by fresh computations. |
|
M 11/5/012 |
HW due: Please finish
registering for the competition (including parent confirmation). Also, read
the training materials that are available here. |
|
T 11/6/012 |
HW due: Finish reading the
competition training materials. If you have not already downloaded all of the
required software, finish doing that as well. |
|
W 11/7/012 |
(The day after Election
Day.) No additional HW is due today, so that you have the option of watching
the election returns if you wish. |
|
Th
11/8/012 |
HW due: Read Lesson 27;
write #15 and both projects at the end of the lesson (“BaseClass”
and “Gymnastics”). |
|
F 11/9/012 |
No school (teacher
workday). |
|
M 11/12/012 |
HW due: Write a new pairs
project proposal (one submission per pair), with timeline and milestones.
Vince is the singleton this time. We will negotiate the specific requirements
and the timeline during class today. |
|
T 11/13/012 |
HW due: Flesh out your
system requirements, as discussed in class yesterday. Continue reviewing the
competition preparation materials. Do not begin coding yet. We will negotiate
the due date of the project so that it does not detract from the competition. |
|
W 11/14/012 |
HW due: If you have not
already done so, read the competition
rules. Check out additional activities on your team captain’s Facebook page. |
|
Th
11/15/012 |
HW due: If you have not
already read all of the items posted on your team captain’s Facebook page, please do so now. I don’t think there is anything
new there, but you never know. |
|
F 11/16/012 |
Competition day! Please
report to MH-102 by 8 a.m. sharp
so that we can make up the schedule for the day. Competition will begin in earnest
at about 9 a.m., assuming we get our decryption key and team hash mailed to us. Cross fingers! |
|
M 11/19/012 |
HW due: Detailed design
documentation for your pairs project. Target length
is approximately 2 pages, but that is only a rough guideline. Some projects
will require tables and/or graphics that could swell the length considerably,
and other projects may fit in a page or slightly more than a page. This is
not a requirements document, but rather a detailed description of how you intend
to implement your project. A list of any libraries or third-party code you
intend to use must be included. A block diagram is recommended but is not
required. |
|
T 11/20/012 |
HW due: Design
documentation will be collected at the start of class. Be on time! This means
you, (cough cough) J. |
|
W 11/21/012 |
Thanksgiving break begins. |
|
M 11/26/012 |
HW due: Sleep and recharge your
internal batteries. Working on your project is permitted, since the design
documents for all groups have been approved, but rest and relaxation are
fine, too. |
|
T 11/27/012 |
HW due: Work on your
project. |
|
W 11/28/012 |
HW due: Progress
review/code review. Be prepared to demo your project in its current partial
state. Order of groups will be determined at random. |
|
Th
11/29/012 |
HW due: Work on your
project. |
|
F 11/30/012 |
HW due: Work on your project. |
|
Return to Mr. Hansen’s home page
Return to Mathematics Department home page
Return to St. Albans home page
Last updated: 12 Feb 2013