Posted: January 31st, 2023

Applications 300582 Session 3 2019: Web Application Project

Technologies for Web

Applications 300582

Session 3 2019: Web Application Project

Due by 11:59 pm on Friday 31 January 2020 Assessment Weight: 30%

A. Requirements

a) ALL instructions given in this document MUST be followed in order to be eligible for full marks for the Web Application Assignment.

b) This assignment is NOT a group assignment; collusion, plagiarism, cheating of any kind is not acceptable. As part of your submission you MUST certify that all work submitted is your own. If you cannot honestly certify that the work is your own then do not submit the assignment. Breaches of the Misconduct Rule will be dealt with according to the university policy (see the learning guide for more information).

c) All assignment submissions will be checked for academic misconduct by the use of the MOSS program from Stanford University. Details on MOSS can be obtained from the MOSS web site http://theory.stanford.edu/~aiken/moss/

d) Design the web pages with ease of navigation and operation, attractiveness and accessibility in mind.

For the problem definition described in section B you must

a. Include your authorship details at the top of each file in coded comments;

b. Reference all sources that you used for inspiration of your solution as per Section C of this document;

c. Ensure that your web application renders correctly in Chrome and runs correctly from the web server.

B (i) Web Application Assignment Details

Western Sydney School Administration office has decided to develop an intranet system to assist with student workshop registration (SWR). SCR will be used by students to register workshops. This is a very simplified system and leaves out many aspects that would be required in a real system for
workshop registration service. Read the Functional Requirements section (section B(ii) of this document) to determine what is specifically required for SWR. The MySQL database that supports the functionality of SWR is named workshopRego. The SWR database is described in section B(iii) of this document. You will need to design and create the PHP web pages for this assignment.

B (ii) – Functional Requirements

SWR must

a) be coded using HTML 5, CSS, JavaScript, and PHP as necessary. Note: all four files described below must be PHP files to achieve the server-side functionality.

b) provide easy-to-use navigation for the user as described in the following page descriptions.

c) provide the following page content and functionality for each page as described.

Student login page (login.php).
Page purpose/description:
The purpose of this page is to provide a login facility for students of Western Sydney School that need to use SWR. No other pages within SWR will be accessible unless the student has successfully logged in first (see Implementation Note below).

Implementation Note: Even though this is the first page that is described in the assignment specification it might be best for some students to delay the implementation of the authentication and access control that starts from this page. If you find that the implementation of this page is difficult then do not let it become a barrier to further development work. The following pages can still be developed without the login working – some functionality will not be possible in those pages, such as displaying the logged-in employee name, but that is a minor detail.

Page content:
The page will have the following content:
1. The following text:
Western Sydney School Student Workshop Registration Application
Note: This Intranet Application is for the use of students of Western Sydney School only. Student information accessed via this system is private and confidential. Information stored within this system may not be shared with external entities without the consent of the
registered students. By logging into this system, I agree to be bound by this requirement.

2. An HTML login form which contains
• a text box to capture the student ID
• a password box to capture the student’s password
• a submit button

3. Appropriate design and instructions for the student
4. The provision for displaying error messages as detailed below

Page functionality:
The login page will
1. need to use postback (submit to itself),
2. authenticate the student credentials (student id and password) as supplied by the student in the login form against the records in the student table of the workshopRego database
3. allow or deny access to the subsequent pages of SWR depending on the result of authentication as follows:
a. Successful login attempt: Successful authentication should automatically redirect the student to the find workshop (findworkshop.php) page.
b. Failed login attempt: Unsuccessful authentication should automatically redirect to the login page so that the student may try to login again. An appropriate error message must be displayed to the student if the login attempt fails or if the student tries to access any of the protected pages of SWR. The message display must be implemented using appropriate PHP server-side code; it is not to be a JavaScript alert (or any other browser side component). The message should be displayed in an appropriate location on the login page in a suitable colour. The message must appropriately indicate the problem that caused it to occur.

Student Login Credentials:
The passwords that are stored in the student table of the workshopRego database.

Site Navigation:
The login page will have no direct hypertext links to any other pages of the system. Access to SWR is only possible after successful login.

Find Workshop Page (findworkshop.php).
Page purpose/description:
The logged-in student will be able to search the information about workshops available for registration within SWR. The student will then be able to register into a specific workshop.

Page content:
The page will have the following content:
1. Navigation to the other pages of SWR as appropriate including a Log Off link (this link must run the logoff.php page).
2. current server date
3. logged-in student name
4. An HTML form (the search form) which contains
• a text box for the Workshop name (mandatory field)
• a submit button
As indicated above the only field that is mandatory in the search form is the Workshop name. That is, a search may be performed on the basis of the name of the workshop only. However, this may result in many matches in the database.
5. A search results (Workshop List) section that lists workshop record(s) that match details from the form.
6. Appropriate design and instructions for the student

Page functionality:
The Find Workshp page will
1. validate that a Workshop name has been entered in the search form (using client-side JavaScript)
2. use postback (submit to itself) for the search form,
3. search the workshopRego database for workshop records that match details provided by the student in the search form. The search may find zero, one or many matches depending upon the search terms entered by the student. The output from the search depends on the number of matches found:
a. One or more records found: generate a list of matching workshop records underneath the search form. The student will be able to choose the record they want to view more detail about from this list (see point 4 below). The summary list provides the following details:
i. Workshop Name
ii. Workshop ID
b. Zero records found: display an appropriate message underneath the search form instead of a list of results, and prompt the student to search for a different workshop by its name
4. enable the student to choose a specific workshop record for viewing from the search results list. To do this, the workshop ID of each workshop in the summary list is to be a hypertext link. When clicked, the hypertext link sends the WorkshopID of the workshop to the Workshop Record (workshoprecord.php) page. The Workshop Record page will then display the full details of the chosen workshop record (details provided below).
General Page Notes:
• The design of this page is open to your creativity but it must appropriately display all required information in a clearly readable, well organised and usable format.
• This page must only be accessible by a logged-in student. If a student tries to access this page and they are not logged in they must be automatically redirected to the logoff.php page (which redirects to the login page) and then display an appropriate error message on the login page indicating that the error has occurred.

Workshop Record page (workshoprecord.php).
Page purpose/description:
The purpose of this page is to display to the user the content of the chosen workshop record (the choice occurs on the Find workshop page as described above).

Page content:
The page will have the following content:
1. Navigation to the other pages of the system as appropriate including a Log Off link (this link must run the logoff.php page).
2. current server date
3. logged-in student name
4. for the chosen workshop:
a. Workshop information: Name, Day, Start Time, Location, WorkshopID.
b. Registration form: This will be a form with the following fields:
i. Registration date (automatically filled in with the server date)
ii. Registration Notes
v. A submit button
5. Appropriate design and instructions for the student

Page functionality:
The Workshop Record page will
1. obtain data from the workshopRego database to display the content as indicated above in points 4(a) to 4(b) for the chosen workshop record. This information cannot be modified by the student. It is likely that separate sql queries will be required to obtain data from the database for 4(a) and 4(b). That is, you should not try to obtain the data using one sql
query.
2. need to use postback (submit to itself) for the registration form,
3. perform server-side input validation as follows for the consultation form:
i. Registration date
• must have a value
• cleaned to avoid possible sql injection
ii. Registration Notes
• must have a value,
• cleaned to avoid possible sql injection,
• may only contain alphanumeric [“0” to “9”, “a” to “z”, “A” to “Z”] characters, spaces [“ “],
hyphens [“-“], commas [“,“], period [“.”] and exclamation marks [“!”].
Note: Error messages as a result of the above server-side validation must be displayed inline (ie, no alert boxes are to be used). There is no client-side validation on this form
4. When the registration form data passes the server-side validation, the details entered in the form will need to be inserted into the registration table of the workshopRego database.

General Page Notes:
• The design of this page is open to your creativity but it must appropriately display all required information in a clearly readable, well organised and usable format.
• This page must only be accessible by a logged-in user. If a user tries to access this page and they are not logged in they must be automatically redirected to the logoff.php page (which redirects to the login page) and then display an appropriate error message on the login page indicating that the error has occurred.

Logoff page (logoff.php).
The purpose of this page is to log the student off the system and automatically return them to the login page. The page must not display anything to the student. The page should remove all session variables and end the session (if sessions were used). It should then redirect to the login page. This page can be accessed from any of the pages as detailed above.

B(iii) – Database Description

To connect to the workshopRego database use the following in your php script
$dbConn = new mysqli(“localhost”, “root”, “”, “workshopRego”);
if($dbConn->connect_error) {
die(“Failed to connect to database ” . $dbConn->connect_error);
}
Notes
• The tables within the workshopRego database have already been populated with data. Use the allTables.php script to view the data (make sure you use the connection information as indicated above).
• Tables in the workshopRego database are described in the Appendix.

C. Referencing
Referencing must follow the guidelines given in Section 2.5.2 of the TWA Learning Guide.

D. Submission Instructions
To submit your Assignment, you must do the following by the due date and time specified on page 1 of this document.
1. Upload all your assignment files in the assignment1 folder in your TWA web site ->Major Project (30%)
2. As part of the submission, you will be required to include the signed checklist within the submission folder. It is deemed to be evidence that you claim that your work is original.

E. Marking Criteria and Standards
The marking criteria and standards for the Web Application Assignment are published in Section 2.5.1 of the Learning guide and will be used to assess your assignment submission according to the specification.

Code Functionality/Correctness 55% Web Page Design 30%
Form Design 10% Code Readability 5%

Appendix:

1. workshopRego database schema

specific weightings identified in the table below:

Code Functionality/Correctness 55% Web Page Design 30%
Form Design 10% Code Readability 5%

Ap

Check Price Discount

Study Notes & Homework Samples: BCJ100 (2) Define due process, as required by the Bill of Rights »A study of the role of human rights in the fight against terrorism