Design and create the following php documents:
1. Login page ([url removed, login to view]). 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
&iuml;‚&sect; a text box to capture the Reviewer ID
&iuml;‚&sect; a password box to capture the user&acirc;€™s password
&iuml;‚&sect; 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 do
Page 3 of 8
not 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.
2. List MPS Applications page ([url removed, login to view]). 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
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
This page must also contain appropriate navigation to other appropriate pages of the site.
3. MPS Application Section 2 ([url removed, login to view]). 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
The content of this page will generally be the same as the assignment 1 section 2 form. The table
below shows the way in which the data items are to be obtained and displayed:
When the submit button is clicked the form should submit to the MPS