Courses‎ > ‎Software Development‎ > ‎Dyrland-Weaver‎ > ‎Projects-Term_1‎ > ‎

Project 02: The final one

posted Dec 20, 2017, 10:57 AM by JonAlf Dyrland-Weaver   [ updated Jan 21, 2018, 3:49 PM ]
Projects are due by 10am Wednesday, 1/24
Here's a checklist of things to make sure you have taken care of:
  • Updated design document
    • Should reflect the actual design of the project as delivered.
  • Devlog
  • Video Demo
    • Show off your project, demo all features.
    • This is not a code presentation.
    • Upload the video to youtube, make sure that it is at least visible to anyone that has the link.
    • Team name - class period
    • Team members
    • Project name
    • Link to video
    • Broad description of project
    • Python library requirements
    • Location for API key file (if needed)
    • Instructions for how to use your site
  • API keys (if needed)
    • Project managers will receive an email requesting API key files
    • Reply with your keys, and where to place them
    • All your keys should be in a single file
  • Make sure all required files are in your github repository and that the master branch is correct.
      • Make a fresh clone of your repo, far away from any development copies you have
      • Follow the instructions you've provided, and make sure it works
      • For best results, do this on one of the Stuy lab machines.
More information will follow, but here are general guidelines about the project so you may begin thinking about it
  • The project must demonstrate knowledge of the concepts covered in class. To that end:
    • You must use python/Flask
    • You must use foundation or bootstrap as a framework
    • You must provide custom CSS
    • You must have your own javascript code that does something meaningful for your project
    • You must use at least one of the following:
      • databases
      • APIs
Design Documents will be due by 8am Friday 12/22
  • Create a new repo and link to it in the vigilant-waddle repository.
  • Create a PDF named DESIGN.pdf in your repository (See previous projects for Design Document guidelines).
  • Create and begin filling in a plaintext file named devlog.txt in your repository (see previous projects for devlog guidelines).
  • Edit in your repository to give -- to start -- a concise overview of your project.
  • Submodule linking notes:
    • Make sure your submodule link appears as follows:
    • NameOfTeam_lastF-lastF-lastF-lastF
    • (e.g., Savages_bethJ-hassanA-miltonF-thompsonG)
    • Note that your repo itself can be named anything you like -- perhaps something indicative of purpose?