Courses‎ > ‎Intro to CS - Half Year‎ > ‎Dyrland-Weaver‎ > ‎projects‎ > ‎

Project 1: The Final One

posted Jan 2, 2019, 10:13 AM by JonAlf Dyrland-Weaver   [ updated Jan 16, 2019, 12:22 PM ]
General Final Project Guidelines:
  • You must create a final project of your own making
    • You may borrow code from earlier work/other netlogo models, but you must document when using code from sources other than your brains.
    • You may, and it is in fact encouraged to, work with 1 other person in your class.
  • You project will most likely fit into one of the following categories.
    • Simulation/Model
      • Make sure your simulation is based in reality. For example, if modeling something in physics, make sure to use actual formulae, don't just make up rules/data.
    • Game
      • When picking a game, make sure it would translate well into netlogo.
      • Remember that controls will either be button or mouse based.
      • Platformer-style games may seem to fit nicely, but they are in fact difficult to put together.
    • Animation
      • Animations are often the easiest to program from a  technical standpoint (not a lot of complex code structures), but will require a lot of tedious code for drawing scenes.
      • Animation should also involve creating custom shapes.
  • You will be required to submit 4 versions of your project over time. Regardless of what kind of project you make. 
  •  You are expected to do work in class AND at home.
  • Your grade will depend on several factors beyond the actual project:
    • a Your prototype/documentation/submissions
    • Consistent work throughout the allotted time. (The procrastination penalty)
  • You should try to get the minimum requirements done early, and play with how your project looks as a last 
  • It is ok if someone goes above and beyond, as long as the other partner contributes a substantial amount. It is NOT ok if one partner does most of the work, and the other does very little.
  • You will have to fill in the information tab, specifically:
    • PUT YOUR NAME(s) AND CLASS PERIOD AT THE TOP!
    • What is it
      • Give a general description of your program
    • How it works
      • Discuss how you put together the program, interesting coding parts, your design plan etc.
    • How to use it
      • Instructions on what I should do 
    • Credits and references
      • If you got outside help, provide credit here.
    • You may fill in other parts, but they are not required.
Final Project Dates:
  • Jan 4th, Start of class
    • Prototypes required in class while you work. This should be an elaborate explanation of your goals, and picture of how you want things to work. Details to follow.
  • Jan 8, 8am
    • HW server Project slot 0 due.
  • Jan 14, 8am
    • HW server Project slot 1 due. 
  • Jan 18. 8am
    • HW server Project slot 2 due.
    • This is the final project 
Prototype:
  • Page(s) 0-1:
    • Top: Name(s) of all involved, class period, team name, project name
    • Section 0
      • High level description of your project.
      • What is it? Why do you want to make it? How will it work?
    • Section 1
      • Template sketch(es)
      • What will the world look like?
      • What will the interface elements look like?
        • Types, size, positioning
      • You may need to provide multiple sketches to show the full design. Thats ok.
  • Page 2
    • Sources of information
      • Will you be using data or formulae, if so, where is that coming from?
      • Will you need to look at code from other NetLogo models? 
        • You might want to look through the "Code Examples" section of the models library for things we have not covered in class that you might need.
    • Task breakdown
      • Who will be doing what
    • Development stages
      • timeline of features to be added, prioritized by importance and feasibility.
      • It is ok to fall behind schedule. 
      • It is OK to modify this.
  • Deadline: Friday after you get back from break, it can be updated afterward, but I want to see that you have it. 
  • NO CODE: Until you hand in the prototype there should be absolutely NO CODE! This is a design process. 
  • You can experiment with different NetLogo features and try making mini-models as a 'working prototype' but nothing you do before the official start counts. 
  • Grade: This will be 20% of your final project grade. It should look like you put serious effort into it. 
  • If it looks like you did this assignment on the train coming to school or rushed it the night before, I will grade you accordingly. 
  • Diagrams can be printed images, or hand drawn. Both of you should PROOFREAD the entire document.
  • Hand drawn does not mean you can draw like a 5-year-old.
    • Take time to draw what you want to show. You don't have to draw everything (just the world, or include the buttons as you choose.)
    • Use a ruler for straight edges! This makes it look much better. (No ruler = you didn't care)
    • Please use reasonable paper! (Drawing on wrinkled looseleaf = you didn't care)
  • The purpose of the document is to:
    • Come together with your partner and make a clear picture of what you BOTH want to do. 
    • Explicitly describe the behavior of your project so I can tell you if there are potential problems. 
    • Make clear expectations public so you have guidelines to follow and don't cut features for no reason.
    • Have the document in class when you are working so I can reference it when I see your group.
  • Keep it out in class:
    • Print one for me, and one for each of you. 
    • You must have it out at all times.
  • Evolving document:
    • You may ADD to it, but do NOT remove old pages. 
    • You may mark sections as outdated, and that they are replaced later.
    • The goal is to see the evolution of your project over its creation. 
Comments