As noted in the course syllabus, a programming project is a required part of the course. I anticipate that most of the projects The project will be done using Snap!, and this document is written with that assumption. However, after seeing NetLogo, you and your partner might choose to use the Logo language. If that interests you, please see the instructor for guidance as to what the expectations will be. Regardless of which language is used you should think about what you want to do before you start thinking about how you can meet the programming specifications. If you pick a good project we can almost certainly figure out a way to have it meet the specifications for the project.
The anticipated due date for the project is a week before finals. We will share the programs via the program sharing web page so all of us can see each other's work. Please do not publish the link to that page which I will share with you. You will submit your work and I will transfer it to the server and put a link to it on the web page I create.
As with the all the programming learning activities this work will be done in pairs (with perhaps one triad).
Regardless of the programming environment, the project is to address all the basics / fundamentals of programming, i.e.,
The program should start with a click of the green flag. It should use the Places Everyone! concept. You should be able to stop at any time and click the green flag and have the program start appropriately. Finally, when done, no script should continue running.
The projects should also have reasonable complexity. Complexity can be based on amount of code but also on as many of the following as is applicable to the kind of project. Note that adding sprites with code the same as another sprite (or otherwise just duplicating code) does not increase complexity.
I'd like you to download your project and one partner send it to me as an attachment to a submission message. That message should:
.xmlfile that you downloaded to your computer attached to the message
Please rename the file using your initials, e.g.,
Please do not use the submission message (or any message with the subject "PEEE Project") to ask questions. I will likely not see them until I start grading the submissions.
In addition to the project code, each team is to submit a project report. The report is mostly descriptive and should include or address the following:
Report weekly values at least. You may report more specifically if you wish. I suggest keeping a log so you can be accurate and perhaps more specific.
Indicate the quality of the project — mediocre, okay, good, excellent. Then provide a rationale for that assessment. The assessment and rational should address the quality of the program, not the quantity of the "effort".
The report should be as long as necessary but not longer. I imagine less than a page of information is too little and more than two or three pages may be too much. I suggest you prepare it in some application so you can save it, and proof-read and revise it.
I prefer the project prose be included in in the body of an e-mail message rather than an attachment. When done drafting, proofing, and revising it, just copy and paste it into the submission message discussed below..
When you have drafted, proofread, and saved your report one team member should prepare and send a submission message to me. That message should:
You can add anything else to your report that you'd like, perhaps the effort, learning, etc. that occurred. Note: this is not a requirement for the report but it might enhance the score.
Please don't use this message (or any message with the subject "PEEE Report") to ask questions. I will likely not see them until I start grading the submissions.
Keep in mind that I will be grading what you submit, not the time or effort you expended, and (unfortunately) not the learning (at least not directly). Hopefully, what you produce will reasonably reflect effort and learning.
The project overall counts 30% of the class score with the project program counting 20% and the project report 10%.
The grading discussion in the course syllabus is a good place to start thinking about grading. Submissions that minimally meet the specifications will likely receive some sort of B. Not fully meeting the specs or having errors in the program can reduce the score/grade. The grade/score can be enhanced by:
The report will be graded similarly to reflection reports. See the course syllabus—the discussion of grading there is applicable to this part of the assignment.