Final Project Instructions

Transcription

1 CPT283: PHP Programming I Final Project Instructions CPT283 Final Project Instructions Version Date: April 19, 2018 Project Name: Vehicle Log Project Purpose: Vehicle Log is a maintenance management program for one of more automobiles or trucks. Almost everyone has a vehicle that requires everything from gasoline to costly maintenance repairs. Vehicle Log is designed to track the use and cost of all consumables as well as machine maintenance. It will calculate the cost to operate a vehicle over a period of time. It will help the user watch everything from how many miles per gallon they are getting to how many miles a set of tires lasts. Vehicle Log can work for one vehicle or a whole fleet. Project Database: Your instructor has prepared a database for the Vehicle Log project. CPT283 students DO NOT have to use this database. It was prepared to give CPT283 students a starting place to get to work on their PHP interface. Students are encouraged to create their own mysql database for this project or alter the database provided by the instructor. Section 3 in our textbook starting on page 505 details how to design and create mysql databases. There are many online resources to help with this as well. Google How to create a mysql database using phpmyadmin and you will find many helpful sites. The instructor s version of the database has already been installed in your lab virtual server. Minimum Requirements: Tables for users, vehicles, maintenance_type, maintenance, and fuel Users should be able to lookup, add, and edit vehicles, maintenance_types, maintenance, and fuel; only administrators should be able to delete anything or add, edit, and delete users There should be a vehicle_log/admin subdirectory that is protected by an Apache htaccess password where all admin interface pages will be located; the username should be cpt283 and the password should be webapps The users tables should capture at least the user_id, first_name, last_name, user_password, and The maintenance table should capture the maintenance_id, maintenance_type_id, and vehicle_id, and at a minimum the maintenance_vendor, maintenance_description, and maintenance_cost of each maintenance event The fuel table should capture at a minimum the fuel_id, vehicle_id, fuel_source, fuel_gallons, fuel_cost, fuel_mileage Users should be able to view reports on each vehicle that details the maintenance events, fuel used, average mileage for consumables like fuel, oil, and tires, and the cost of operation on each vehicle over a period of time The solution application must be well documented with comments embedded in the code Extras (for extra credit): Roles assigned to users like admin or user; authentication for users; see How to use authentication in Chapter 21 in our textbook Report options listing the details of each individual table that includes printing and exporting data to a spreadsheet CPT283 Final Project Instructions docx Page 1

2 CPT283: PHP Programming I Final Project Instructions Authentication for administrators with additional features for adding/editing/deleting all tables Make the application responsive for small screens by using Twitter s Bootstrap Use MVC pattern in code development Embed an online HTML editor like TinyMCE CPT283 student added extra feature not specified in the Final Project assignment Application Structure: In an effort to leave CPT283 students as much flexibility as possible, the application structure expectations are limited to the following: The interface must be original PHP code written by the CPT283 student submitting the project; do not use any non-original utilities or other code not created by you in your project unless expressly approved by your instructor (i.e. Bootstrap, TinyMCE, etc.) The database must be in mysql and be named vehicle_log Develop the project on your assigned CPT283 virtual server; create a directory named vehicle_log in the document root of your web server ( /var/www/html/vehicle_log ) which will contain all of your PHP, HTML, and CSS files Disclaimer: Your instructor reserves the right to change these instructions as necessary at any time. CPT283 students will be notified of any changes by way of and announcements on our Blackboard class page. Questions and Suggestions: Your feedback about the final project is encouraged. Address all questions and/or suggestions to your instructor at sandewbs@my.gvltec.edu. Attachments: Final Project Grading Rubric vehicle_log.sql printout CPT283 Final Project Instructions docx Page 2

3 CPT 283: PHP Programming I FINAL PROJECT GRADING RUBRIC (1803) Student: REQUIRED FINAL PROJECT SPECIFICATIONS: 1 Project works according to specifications 2 Instructions followed; all requirements included in the app 3 Code does not generate any errors; logic is efficient Points Earned Points Available Specifications 0% Mostly 80% Somewhat 70% Needs Improvement 60% Does NOT Meet Specs 0% Tables used for users, vehicles, maintenance_type, maintenance, and fuel Non administrative users able to lookup, add, or edit everything but users table; must not be able to delete anything Administrators must log in and be able to delete anything; as well as, lookup, add, or edit all tables in the app Interface and tables allow input of users, vehicles, maintenance, maintenance_type, and fuel 8 Users able to list/view all data using the app 9 User friendly and professional interface Well commented code documentation on each page of the app TOTAL REQUIRED POINTS 0 EXTRA FEATURES FOR BONUS POINTS: 11 Bootstrap used in app design; app must be responsive 8 12 Demonstrate your app to the class 7 13 Authentication using PHP code for administrators (not.htaccess) 7 14 Coded report(s) for maintenance and consumable consumption 6 15 Coded report(s) for users, vehicles, and maintenance_type 6 16 Use of MVC pattern in code development 6 17 Additional student added features; must be documented TOTAL BONUS POINTS 50 TOTAL FINAL PROJECT POINTS 150 CPT283 Final Project Grading Rubric 1803.xlsx

4 P:\CPT283\CPT283 Final Project\vehicle_log.sql phpmyadmin SQL Dump version Host: localhost Generation Time: Aug 20, 2016 at 03:59 PM Server version: PHP Version: Saturday, August 20, :01 PM SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"; SET time_zone = "+00:00"; /*!401 */; /*!401 */; /*!401 */; /*!401 SET NAMES utf8 */; Database: `vehicle_log` Table structure for table `fuel` CREATE TABLE IF NOT EXISTS `fuel` ( `fuel_id` int(12) NOT NULL AUTO_INCREMENT, `vehicle_id` int(12) NOT NULL, `fuel_source` varchar(0) NOT NULL, `fuel_gallons` int(12) NOT NULL, `fuel_cost` int(12) NOT NULL, `fuel_mileage` int(12) NOT NULL, `fuel_date` datetime NOT NULL, `fuel_date_modified` datetime NOT NULL, PRIMARY KEY (`fuel_id`) Table structure for table `maintenance` CREATE TABLE IF NOT EXISTS `maintenance` ( `maintenance_id` int(12) NOT NULL AUTO_INCREMENT, `maintenance_type_id` int(12) NOT NULL, `vehicle_id` int(12) NOT NULL, `maintenance_vendor` varchar(0) NOT NULL, `maintenance_description` varchar(255) NOT NULL, `maintenance_vendor_address` varchar(255) NOT NULL, `maintenance_cost` int(12) NOT NULL, `maintenance_mileage` int(12) NOT NULL, `maintenance_date` datetime NOT NULL, `maintenance_date_modified` datetime NOT NULL, PRIMARY KEY (`maintenance_id`) Table structure for table `maintenance_type` -1-

5 P:\CPT283\CPT283 Final Project\vehicle_log.sql Saturday, August 20, :01 PM CREATE TABLE IF NOT EXISTS `maintenance_type` ( `maintenance_type_id` int(12) NOT NULL AUTO_INCREMENT, `maintenance_type` varchar(255) NOT NULL, PRIMARY KEY (`maintenance_type_id`) Table structure for table `users` CREATE TABLE IF NOT EXISTS `users` ( `user_id` int(12) NOT NULL AUTO_INCREMENT, `first_name` varchar(0) NOT NULL, `last_name` varchar(0) NOT NULL, `user_password` varchar(50) NOT NULL, ` ` varchar(0) NOT NULL, `date_created` datetime NOT NULL, `date_lastlogin` datetime NOT NULL, `date_modified` datetime NOT NULL, PRIMARY KEY (`user_id`) Table structure for table `vehicles` CREATE TABLE IF NOT EXISTS `vehicles` ( `vehicle_id` int(12) NOT NULL AUTO_INCREMENT, `vehicle_type` varchar(0) NOT NULL, `vehicle_model` varchar(0) NOT NULL, `vehicle_year` int(4) NOT NULL, `vehicle_year_purchased` int(4) NOT NULL, `vehicle_color` varchar(50) NOT NULL, `vehicle_vin` varchar(30) NOT NULL, `vehicle_license_tag` varchar(0) NOT NULL, `vehicle_license_state` varchar(50) NOT NULL, `vehicle_purchase_price` int(20) NOT NULL, `vehicle_purchase_mileage` int(12) NOT NULL, PRIMARY KEY (`vehicle_id`) /*!401 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!401 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!401 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; -2-