Final Project

The goal of this project is to emulate a real-world agency process to plan, design, and build a working web application according to client specifications and employer defined workflows. It will utilize everything you've learned this year:

• Semantic HTML
• Responsive CSS
• Front-end JavaScript
• Back-end Python
• PostgreSQL Database
• Agile Process
• Security Objectives
• Feature Branch Git Workflow

The Teams

Each team is composed of around four developers. As a group, you'll choose two people to take on the roles of Project Manager and DevOps. Note, these roles are not a hiearchy. All members of the group have equal say in decision making. These roles are just to divide areas of responsibility:

• Project Manager:
  • Responsible for keeping stories up to date in the project management software.
  • Will run daily stand-up and weekly planning meetings.
  • See more details about Project Management.
• DevOps:
  • Responsible for maintaining the repository on GitHub, Heroku, and Travis CI.
  • Will run Pull Request reviews.
  • See more details about the Git Workflow.

To sum it up, if I have a question about your progress I'll ask the PM and if I have a question about your code I'll ask DevOps.

The Product

You are reproducing the college portal. It would take months to build the whole thing, so you're only working on a small subset of features. Most of the user stories have already been written for you, but you will be editing and adding to them as you work.

1. The first thing you need to do as a group is to read through the user stories and get an idea of the scope of the project.
2. Write down a list of the unique Actors and Assets.
3. Create a Threat Model using Google Sheets and add a link to it in the Documentation list on Trello.
4. Then add your Security Objectives to the descriptions of any related user stories.
5. With your knowledge of actors and assets, you can now create a Database Diagram using Draw.io, adding the link to the Documentation on Trello.

Treat your threat model and database diagram as rough drafts to get you started. You will change them over time as you learn more about the product you're building. Documentation is only helpful if it's up to date, so look at it often. You should also add any other resources you create to Trello, like adding drawings or designs for a story.

The Schedule

This is a four week project. Each week will start with a planning day to prep a week's worth of stories and review the previous week's deployment.