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

Project 2: The Final Frontier

posted May 8, 2017, 8:38 AM by JonAlf Dyrland-Weaver   [ updated May 11, 2017, 6:19 AM ]

github repo:

More information will follow, but here are general guidelines about the project so you may begin thinking about it
  • Project must be done in groups of 4*
    • Due to math (or the illegality of splitting students into fractions of students), 6th period will have 1 group of 5.
  • The project must demonstrate knowledge of the concepts covered in class. To that end:
    • You must use python/Flask
    • You must use a front-end framework (probably bootstrap or foundation)
    • You must provide custom CSS
    • You must have your own javascript code that does something meaningful for your project
      • It should be a relatively meaningful amount of js. 
      • Include at least one example of:
        • making ajax calls
        • using canvas or svg
        • using data visualization (most likely d3)
    • You must use at least one of the following:
      • databases
      • APIs
        • If you are using an API, research it to make sure it is stable.
  • More Guidelines will follow as we move on
Design Documents will be due by 8am Friday 5/12
  • Create a new repo and link to it in the vigilant-telegraph repository.
  • Create a PDF named DESIGN.pdf in your repository (See Project 1 for Design Document guidelines).
    • Include a component map, site map and database schema (if applicable), as well as any necessary supporting documentation.
    • Divide the tasks among your group members. Include a Project Manager.
    • Include a tentative timeline
    • Include a style guide
  • Create an begin filling in a plaintext file named devlog.txt in your repository.
    • The purpose of the devlog is so that any group member can see what the current state of the project is.
    • The devlog should be a plain text file that can be easily edited.
    • PM will make sure devlog is being maintained, but will not make all entries.
    • When any team member stops working and pushes changes to github, they should update the devlog explaining what changes have been made. Include any errors/bugs discovered (or created).
    • Separate devlog entries with newlines, put the latest entries on the bottom
    • Each line should begin with the following format: firstL -- TIMESTAMP\n
      • eg: jonalfD -- 2016-12-04 14:32
  • Edit in your repository to give -- to start -- a concise overview of your project.