Skip to content

Latest commit

 

History

History
71 lines (59 loc) · 4.38 KB

final-project.md

File metadata and controls

71 lines (59 loc) · 4.38 KB

STARS Exploring CS Spring 2017

Final Project

Code Due Sunday, 05/28, at 9pm

Presentation, Friday, 06/02, at 4:30pm

Goals

  • Demonstrate success and learning in Processing
  • Demonstrate knowledge of variables, methods, parameters, conditional statements, loops, and arrays
  • Demonstrate the ability to learn and explore new concepts and topics not explored in class
  • Demonstrate successful communication and the ability to work with others
  • Practice informal usability studies
  • Practice presenting to others

Prework

  • Generate a list or sketches (or both!) of your project ideas, think big, we will help you scope down your project if needed
  • General topics you might explore: Games, Puzzles, Choose-Your-Own-Adventure Stories, Digital Prototype, Data Visualizations, Text Generators, Educational experience, Twitter bot, Generative art ...
  • Post your top 2 – 3 ideas+sketches to the Slack channel to share with others

Specification

  • You must maintain a Trello board throughout the project that tracks what you are planning to do, what you are working on, and what you are done with (along with anything else your group would like to track)
  • Your project must be unique and based on your own ideas, consulting web resources is highly recommended, but make sure your project is not the same as something else you found
  • Your project must demonstrate your ability to use variables, methods, parameters, conditional statements, loops, and arrays in your code
  • You must conduct at least 5 informal usability sessions, to get user feedback and make changes (this is required content for your presentation)
  • You must work together with your partner for all aspects of the project, and you both must fully understand every aspect of the code
  • Your group must show movement forward in your project each week (you will demo your project each week)

Optionals

  • Create and submit a video showcasing your project (this can be anywhere from 2 - 6 minutes, depending on the project). The video should demonstrate a run-through of the program, with a voice talking through what is happening
    • You can record a video, or use screen recording software (I recommend screencast-o-matic)
    • Note: You will be evaluated on your ability to tell the story of a user using your project, not on the execution of your video

Code Submission

  • Your code should have a top comment block with your name, last edited date, and a brief description of the entire program
  • Each line in setup and draw should have a comment
  • Each method that you created should have a top comment briefly explaining what that function does (note that setup and draw do not need top comments)
  • Any complicated parts of your code should have line comments

Grading Rubric

Code

Criteria Points
Group demonstrated progress each week 1 pt
Group used Trello to track progress and tasks 2 pts
Showcased a complete project, that runs without errors 2 pts
Showcased a well-executed, creative project 3 pts
Used variables as appropriate 1 pt
Used methods and parameters as appropriate 2 pts
Used conditional statements as appropriate 2 pts
Used loops and arrays as appropriate 3 pts
Code is fully commented as described in the Code Submission section 3 pts
Code uses correct style throughout as discussed in class 3 pts
Extra Credit: Group created a video, showcasing the project 3 pts

Presentation

Criteria Points
Group's presentation was 5 minutes in length 1 pt
Group was prepared, and professional during the presentation 1 pt
Group clearly presented an overview of their project 1 pt
Group clearly described their project process in detail 2 pts
Group presented data collected from their usability studies and how it informed their project 2 pts
Group demoed a live version of their program 2 pts
Group talked about the details of their code with appropriate detail 2 pts
Group talked about extensions they would like to have added if more time allowed 1 pt
Group presented what they learned from the experience, and if/how they will be moving forward with the project 1 pt
Group fielded questions about their project and code with ease 1 pt