11th grade retreat: Difference between revisions
Mr. MacKenty (talk | contribs) (Created page with "right|frame|This a problem set for you to work through <ref>http://www.flaticon.com/</ref> This is a problem set. Some of these are easy, others are far m...") |
Mr. MacKenty (talk | contribs) |
||
Line 23: | Line 23: | ||
# student 2 wants to be in activity 7 and 8 | # student 2 wants to be in activity 7 and 8 | ||
# and so on... | # and so on... | ||
1:5, | # | ||
2:7,8 | choices={"1":"4,5", | ||
3:1,6 | "2":"7,8" | ||
4:2,4 | "3":"1,6" | ||
"4":"2,4" | |||
</syntaxhighlight> | </syntaxhighlight> | ||
== Unit Tests == | == Unit Tests == |
Revision as of 09:01, 22 August 2018
This is a problem set. Some of these are easy, others are far more difficult. The purpose of these problems sets are:
- to build your skill applying computational thinking to a problem
- to assess your knowledge and skills of different programming practices
What is this problem set trying to do[edit]
This is example problem set. In this example we are learning about lists, conditionals, and processing user input.
The Problem[edit]
The 11th grade has a two-day retreat. This retreat will help them learn about CAS (Creativity, activity, service). There are 8 activities for the 11th grade retreat. Each activity can only have 10 students. Each student can make a primary request and a secondary request.
Your solution must make the best possible match for all students. An example of the INPUT data is provided below:
#
# in the example below:
# student 1 wants to be in activity 4 and 5
# student 2 wants to be in activity 7 and 8
# and so on...
#
choices={"1":"4,5",
"2":"7,8"
"3":"1,6"
"4":"2,4"
Unit Tests[edit]
Hacker edition[edit]
Demonstrate
How you will be assessed[edit]
Your solution will be graded using the following axis:
Scope
- To what extent does your code implement the features required by our specification?
- To what extent is there evidence of effort?
Correctness
- To what extent did your code meet specifications?
- To what extent did your code meet unit tests?
- To what extent is your code free of bugs?
Design
- To what extent is your code written well (i.e. clearly, efficiently, elegantly, and/or logically)?
- To what extent is your code eliminating repetition?
- To what extent is your code using functions appropriately?
Style
- To what extent is your code readable?
- To what extent is your code commented?
- To what extent are your variables well named?
- To what extent do you adhere to style guide?
References[edit]
A possible solution[edit]
Click the expand link to see one possible solution, but NOT before you have tried and failed!
not yet!