We have seen a couple different uses of Scratch (story telling, drawing block letters, drawing with polygons) and a variety of Scratch blocks and features. Familiar topics are broadcasts (especially for "Places Everyone" & "Action"), movement for drawing, repetition, and creating our own blocks or new instructions. Less familiar topics are variables. This learning activity will provide additional experience with variables, perhaps with less of a math orientation. As usual it should allow for creativity and problem solving, and be interesting for kids. The task is to do something that involves user input and variables. You might choose some sort of story telling but are encouraged to think a bit outside the box.
During class we saw/will see the an example that makes use of user input, variables, and the if block. Also included were the use of randomly generated values and cloning. The task here is to come up with your own program that makes use of user input (the ask block, variables, and the if ... or if ... else ... block. More uses is better.
This assignment builds on the expectations in the previous task and adds some new ones. Note that some of the specifications below are required. (Whether you meet the expectations is up to you, but it will be considered when determining the extra credit for shared programs.) The expectations are:
You may work in pairs on this assignment if you wish. Those who do work in pairs are expected to have more impressive products. Everyone is encouraged to try to impress themselves and the instructor. If you feel your project is worth sharing I will include it in a class sharing document. Scratch will allow you to share it with the world if you wish (but that is not how we'll share it—download and send me a copy of the program). Sharing it with the class can earn a bit of extra credit. Sharing earns a (very) little bit of credit. Sharing something that meets all the "required" expectations will earn a bit more extra credit and sharing something particularly fun, interesting, amazing, ... earns a bit more extra credit
As noted in the TARR (task-specific activity and program report) document the graded component of this assignment will be the report you submit. Please keep in mind that the activity report should indicate what you did/included in your program, i.e., which expectations you met and did not meet. The TARR document also includes a number of cues you can use to kickstart your reflection. The submission message should have the subject PEEE_Scratch-V.
If you have questions about the assignment send me an e-mail or drop by my office. If you have a question while working on the assignment do the same. Keep in mind that when you encounter something you can't figure out you can/should think, explore, seek answers on google, etc. but, do not spend more than 15-30 minutes trying to overcome a particular error or problem.
I encourage you to suggest additions to our code templates page. You might suggest a revision to clarify (or finish) something that is there already or an entirely new topic. Please indicate how/why you think the would be helpful. Communicate as clearly and fully as you can what is needed/desired. (This can earn you extra credit.)