Small (4 page) LAMP website - 26/04/2018 10:13 EDT

Hello! We have a need for a simple website for use in a graduate class about project management. This application would be part of the deliverables for our project. But don't worry, it's not a programming or development class, you're not doing our homework for us. Outsourcing the development is part of our project. This project is to be a simple online timesheet web application called BaruchTime. We're envisioning this built on a LAMP stack, and contain four pages. Upon completion, we plan on hosting this on our own AWS environment, so we'd like the website and code along with the database schema and whatever instructions are necessary to configure for a new environment. The four pages would be: 1. a log in page Username (in email address format) and password to be stored as hashed within the database. For this purpose, I'd like to have one user for each of the three user classes (more below) pre-created, I can create further users in the database manually. 2. a time entry page. This screen is for users (the first class of user) and is to populate, by default, the dates for the current week Sun-Sat (or Mon-Sun, it doesn't really matter). It should have a date picker to pick alternate days (past and future) which will populate the 7 week days appropriately. If hours have been previously entered for that user for that time period, they'd populate here, otherwise, they'd be blank. For each day, there should be an entry for time in, time out, 2nd time in, 2nd time out, and comments. If possible, there should also be a total number of hours entered (both for each day and a total for the week). If this user's week has already been approved (more on that below), the data here is read only. If it has not yet been approved, they may enter their time and comments for each day and submit. They may submit more than once, as long as it has not yet been approved. Submission allows the user's approver to approve or deny the timesheet. 3. an approver page A read only view for approvers (the second class of user) for the timesheets for the users for which an approver is responsible. An approver should be able to view all of their user's timesheets, only those that need approval, a specific user's timesheets, or only a specific user's timesheets that require approval. For timesheets that have not yet been approved, the approver should be able to either approve or reject the timesheet. 4. an admin page A read only for admins (third class of user). An admin may query any timesheet for any user, but has no write permissions an no ability to approve or reject. Upon login, one should have access to the appropriate page for their user class. The three classes of users, as mentioned above, are: 1. users Those who enter their time and submit for approval. Access only to the time entry page. 2. approvers Those who are responsible for approving their delegated user's timesheets. An approver may have more than one user for who they are responsible (though a user only has one approver). Access only to the approver page. 3. admins Those who may see (but not modify) any timesheet for any user. Access only to the admin page. This "proof of concept" site is needed for a project management demonstration, and the specific look and feel are less important than the overall functionality. We have an example wireframe of the time entry page, but the website does not need to look like this if the developer has other ideas. thank you!