Project Milestone 3

This project milestone spec will be improved as part of our weekly usergroup meetings in the course. For now, it is a basic framework so that we can begin asking questions.

Overview

In this milestone, we will be focusing on 4 key features:

  1. Support for all hospitals*
  2. A back-end database
  3. User Authentication
  4. Maintain existing features

Support for all hospitals

You must now give the user the option to select any hospital in the data files that we have.

Of special note here is that some hospitals may not be eligible for a VBP score. You will indicate that if it happens.

It is up to you to design an intuitive hospital select box for picking a hospital.

The report will initially default to your hospital from Milestone 2 until a new one is selected. Use a change handler on the drop down to trigger the selection, no separate button.

* Teams of only 3 people will only have to support their hospital from M2 and Poudre Valley Hospital (Provider 060010). Since you were required to pick an eligible hospital and 060010 is also eligible, teams of 3 will not have to check for eligibility.

A back-end database

Your program will now use a SQL database to store all data (no more flat files).

You need not carry forward data from M2 to the database. It is OK to start fresh.

User Authentication

Users can now log in. There will only (for now) be the notion of a logged in user or not, no roles or permissions.

You must include a user named ct310 with a password of "cookesareyummy"

Maintain existing features

The ability to model a report and save a scenario shall be maintained. As well as the ability to comment on a report. Anyone can model. Only a logged in user can save or load a scenario or comment on a scenario.

Project Deliverable

Your site must make full use of the Fuel PHP Framework, using Fuel MVC for all pages.

Your site must make use a backend database for all data storage

Your deliverable is a tar file named groupX.tar where X is your group's number. Your tar will contain all of your models, views, controllers, and other associated files. It must also include a folder named "sql" that has all of the CREATE and INSERT queries to fully set up your database state. You need not include any Fuel framework files, they shouldn't be changed other than minor configuration updates.

Your site must be available on the local_html server at ~eid/ct310/m3/ (this will automatically load index.php which will automatically call your default controller/action)

Each team member must host the working site on their local_html directory accessable by the URL ~eid/ct310/m3

The Data

The data files are the same as before, but you must now load the entire file into your DB in order to generate a report for any hospital.

Peer Effort Review

After the assignment is submitted, there will be a report in canvas where you will divide 100 points of effort between your 4 or 5 group members. If everyone contributed evenly, you will give them 100/n points (20 or 25 depending on group size). You will also have an opportunity to comment on each group member's participation. The instructor will take those points into account when assigning group effort scores for each project milestone.

Grading Criteria

  • Submission submitted correctly, files correct, named correctly (10%)
    • Browser Compatibility: Site will work in the latest version of modern browsers, such as Chrome, Firefox, Edge, Opera, IE, Safari
  • Ability to run a report on any hospital (20%)
    • Hospital Select is intuitive
    • Handles hospital not eligible or only 3 domains eligible
  • Data stored in a backend database (20%)
  • User authentication and access restrictions (20%)
  • Existing features maintained (10%)
  • Peer Effort Review (20%)