All functionality required for this assignment must be achieved using PHP server side scripting. No browser side scripting is to be used.
In assignment you created the initial user interfaces for the MPS application web pages. In assignment 2 you will implement some of the php server-side scripts to support the MPS application process. These scripts are implemented from the perspective of the Medical Practitioners and Roads and Maritime Services (RMS) staff that review MPS applications. Specifically, you will be implementing a simple authentication and access control system that will enable medical practitioners and RMS reviewers to login to the system; make changes to existing records; and review current applications. To do this the PHP scripts that you write will need to interact with a MySQL database that has been installed on TL28serv. This database is called MPS and is described in detail in Appendix A of this document.
Tip: It is recommended that before starting on the individual PHP pages indicated below that you determine the content of each of the tables of the MPS database. You can do this in the same way that you determined the warehouse database content for Prac 3 - see tasks 3 and 4 in the prac 3 document for the general structure of how to do this.
Your task is to implement five (5) php pages. The requirements of these five (5) php pages are explained below.
Assignment 2 Specifications
Design and create the following php documents:
1. Login page (login.php). The purpose of this page is to provide a login facility for RMS staff and
Medical Practitioners that need to review MPS applications. All other pages within the system will not be accessible unless the user has successfully logged in first.
The login page will contain a login form that will capture from the staff member their login information (Username and Password) and then verify those details against the records in the database before allowing the user access to the subsequent pages of the system. This section of the page will have the following content:
o An XHTML form which contains
- a text box to capture the Reviewer ID
- a password box to capture the user's password
- a submit button and a reset button
o Appropriate design and instructions for the user
o The provision for displaying error messages as required (see challenge 1 for details)
This page will need to submit to itself. If the login details supplied by the user match user credentials that are in the database then the page should automatically redirect the user to the List MPS Applications page which is detailed in section 2 below. If the login details supplied by the user donot match those stored in the database then the login page should be redisplayed so that the user may try to login again. This page will have no direct links to any other pages.
Note: if the login page does not submit to itself but instead submits to a separate page for authenticating user credentials then lesser marks will be awarded. Please see the marking guide for details of the marks associated with the login page.
Challenge 1 is associated with this page. See the Challenge section for details.
Save the login.php file, any associated images, and the Assign2.css file in the assignment2 folder in your TWA web site.
2. List MPS Applications page (MPS_List.php). The purpose of this page is to generate two dynamic listings of MPS Applications; the first representing all Pending applications; the second representing all Completed applications.
Listing of pending applications:
The listing of pending applications can only be viewed by medical practitioners. The listing should display the application number, customer number, and application date, in ascending order of the application date and then descending order of application number for all pending applications. Each application displayed in the listing should be selectable in some way. That is, the user should be able to choose one of the applications to review; doing so will result in the MPS Section 2 page being opened to display the chosen application (details of the MPS Section 2 page are given in point 3 below).
Listing of completed applications:
The listing of completed applications can only be viewed by RMS reviewers. The listing should display the application number, customer number, customer surname, permit type, and application date, in ascending order of the application date and then descending order of customer surname for all completed applications. The listing should be selectable in some way. That is, the user should be able to choose one of the applications to view; doing so will result in the MPS Outcome Letter page being opened to display the chosen application outcome letter (details of the MPS Outcome Letter page are given in point 4 below). Note: completed applications are those that have a status that is not P in the database.
This page must also contain appropriate navigation to other appropriate pages of the site.
Challenge 2 is associated with this page. See the Challenge section for details. Save the
MPS_List.php page, any associated images and the Assign2.css file in the assignment2 folder in your TWA web site.
3. MPS Application Section 2 (MPS_section2.php). This page should only be accessible to a logged in medical practitioner. A medical practitioner uses this page when they need to provide their assessment of eligibility for the MPS permit for the application chosen in the List MPS_Applications page.