AMIT2043 Web Systems and Technologies
Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: daixieit
AMIT2043 Web Systems and Technologies
Group Assignment
1.0 General Information |
Objective:
At the end of this assignment, the student should be able to:
(i.) Produce data-driven web application using client-side and server-side scripting. (P4, PLO3)
(ii.) Demonstrate dynamic and interactive webpages by adopting current emerging web technologies. (P4, PLO3)
Assessment Weight: |
This project contributes 100% to the coursework component. |
Group Size: |
3 - 4 members in a team. |
Submission Mode: |
Softcopy. Refer to Section 4.0. |
Submission Date: |
Prototype Demo Week 7 (Practical) System Submission and Presentation Week 12 (Practical)
|
Feedback to Student: |
Week 14. |
2.0 Assignment Specifications |
You are required to develop a web application by using client-side and server-side technology for any society (it can be real or imagined) of your choice. The web application implements the society and event management system. The system includes the basic society and event management features, for example, an administrator able to add new event and related activities, edit existing events and activities, view participants, sell tickets or free booking, etc. Participants can register as member and log in, browse for events, search for events, buy tickets or register for events, checkout and view booking’sstatus.
The web application should be able to capture the following information about: -
• Events or Activities (such as competition, workshop, talk, etc.)
• Event Volunteers / Participants
• Buy Ticket/ free enrollment.
The web application should provide the features as follows: -
• An administrator should be able to:
o Add new events.
o Edit existing events.
o Update seat availability
o Manage online ticketing/booking.
o View and manage booking.
• Participants should be able to:
o Register and login.
o Browse for events.
o Search for events
o Buy ticket / Join event.
o Complete booking
o View ticket / booked event records.
For more detail requirements, please refer to 3.2 Fundamentals of Web Development
The web application allows user to maintain their records in MariaDB/MySQL, an open- source database tool. The web application should support the basic CRUD (Create, Read, Update and Delete) operations to the database table.
There are NO minimum and maximum limits to the number of web pages you should create.
2.0 Assignment specifications and 3.2 fundamental as a sample guideline, students may get more relevant functions/requirements needed from the resources below:
• TAR UMT Societies/Clubs (https://tarc.edu.my/dsa/a/society-club/society-club/)
o You can contact the person who works for the Society or the Club for more information
• Societies and Associations - One Stop Malaysia (https://www.onestopmalaysia.com/directory/organisations/societies-and-associations/)
o This website lists societies/clubs that provide official links. You can click on these official links to get some inspiration from their website user interface design and content.
3.0 Assessment Criteria |
Society/Event management system
Web Prototype
No |
Criteria |
Marks |
1. |
Web and Navigation Design, HTML Form Controls, System Prototype |
30% |
TOTAL: |
30% |
Web System
No |
Criteria |
Marks |
1. |
Database |
10% |
2. |
Functionality: Record Adding, Listing, Updating, Deleting, Search and Filter |
30% |
3. |
Usability |
10% |
4. |
Programming Logic and Style |
10% |
5. |
Additional Features |
10% |
TOTAL: |
70% |
For detailed assessment criteria, and learn how marks are to be awarded, refer to the Marking Rubric as attached with this assignment specification.
3.1. Database Programming |
Students are required to use MySQL database tool to create an online application database. In the database, example of tables that can be included are Participants, Events, Event_Details, Tickets, and Bookings to store relevant records.
3.2. Fundamentals of Web Development |
A. Record Adding
The web pages allow user to add record by entering necessary details. The requirements are as follows:
• Use appropriate GUI components to design the web pages. Try to use GUI components that can minimize user input and input error whenever possible. Using text fields for all input fields is a very BAD idea.
• Include input features: -
o Admin to add a new event.
o Participant to register and login.
o Participant to book to join an event / buy ticket.
o Participant complete booking / print ticket.
• Perform input validations and confirmation message before data is submitted (simple or complex). Display appropriate error message if an input error is detected.
B. Record Listing
• Features Includes:
o Event catalog. Participant able to browse the event categories view the events based on the specific category.
o Participant records and booking list. Admin able to browse and view the full participant record and booking list.
o Ticketing/Booking module. Display the contents of the ticketing system in detail and give the participant the option of updating the ticket/booking by changing the quantity or remove the items.
• Display a count that indicates the number of records in the list.
• The output should be NEATLY formatted.
• Include buttons or hyperlink that allow user to:-
o View Remove all records from the list.
o Navigate to other webpages.
C. Participant to search event, Admin to search ticketing or booking record
The web page allows participant to enter a target event searches through the event list for matching event record. If there is a match, the details of the matched record will be displayed on the web page. Otherwise, display a message to indicate the event is not found. Admin panel should allow admin to search booking/ticketing details and participant record by specific ticketID or other specific like date or participant name.
The requirements areas follows: -
• Use appropriate GUI components to capture the event/ticket and display the matched event/ticket records.
• Include buttons that allow user to:
o Search the event or ticket record based on the given search specific.
o Navigate to other webpages.
D. Updating event, participant, and ticket/booking details
UPDATE an existing event, participant, and ticket/booking record. This operation is based on the primary key (EventID, ParticipantID, TicketID) provided.
Create web pages that are able to retrieve and display event information, participant details and ticket/registration details by a search on valid primary key.
Basic requirements include:
• Update an existing record based on the primary key (EventID, ParticipantID, TicketID) provided.
• If primary key is valid, display forms with relevant HTML input controls and pre- populate these controls with the original record’s field values. Use appropriate HTML input controls for each field (except EventID, ParticipantID, and TicketID which should not be changed).
E. Record deleting
DELETE an existing event, participant, and ticket/booking record.
Basic requirements include:
• Delete an existing record based on the primary key (EventID, ParticipantID, or TicketID/BookingID) provided.
• Ask for user confirmation before the operation takes place. Use JavaScript code to achieve this.
Notes :
• In a real event system, is not a wise decision to delete completely the record from database/ system. An alternate way is to hide from front end but still keep the data in database, or provide alternate log data to keep record on deleted data.
F. Additional Features
• Covers additional features for advanced users. Additional features should be very useful and implemented perfectly and completely.
G. Web design, System Prototype and HTML Form Controls
• Create a clean, simple, consistent, and informative web site for the society. A good and attractive website gets more traffic and retention to attract event participants, students and public. Use right color, font size and other relevant elements to ensure that visitors easy to view the society information and event details they are looking for.
• Use the right HTML controls for validation purpose. The right HTML controls should be able to minimize the input errors and provide the necessary feedbacks to user if the inputs inserted by users are invalid. All the HTML controls should be well structured.
• Demo a Complete System prototype which shows the complete usability and the functioning of the system with all the detailed web pages and user interfaces.
H. Usability
• Improve user experience in event management from browsing to confirm a booking/transaction or/and payment.
o E.g. Create neat and smooth navigation to ensure that participant are able to locate information, register, book the event, buy ticket, and make payment with minimal click.
o E.g. Add functions which will ease participant action like seating capacity, fast booking, wish list, compare events, event notification, etc.
• Fulfilled the society and event system need.
• Able to deploy and used by the society.
I. Programming Logic and Style
• The student should develop the online application in logical manner.
• Codes are well-structured, effective, and well-tested.
• Codes are indented properly and highly readable.
• The variable names used should be meaningful.
• Standard and convention are followed strictly.
• Comments are used appropriately.
J. Other General Requirements
• Try your best to make the online event application easy to use and easy to navigate.
• Make your source codes easy to read and understand. Use comments to provide brief description to a complex logic. Format your source codes with appropriate spaces and line breaks.
3.3 Cross Device and Cross-Browser Compatibilities |
• The student is encouraged to implement the web application using various web technologies. Students can use a variety of third-party libraries (e.g. Bootstrap, jQuery, Font Awesome, etc.) to design the front-end of a web application. Below are some resources from which students can find some third-party libraries useful for front-end design:
o CSS
. Animate.css (https://animate.style/)
. Bootstrap (https://getbootstrap.com/)
. Font Awesome (https://fontawesome.com/docs/web/setup/get- started)
. CSS WAND (https://www.csswand.dev/)
o JavaScript
. Chart.js (https://www.chartjs.org/)
. Sweetallert2 (https://sweetalert2.github.io/)
. Dropzone (Dropzone.js)
• The web application must be supported by all devices and browsers. Each web page should be displayed properly in different screen sizes.
4.0 Deliverables |
Assignment documentation
The final report should be arranged as follows:
1. Cover page
2. Marking Rubric
The project source codes. Arrange and submit your files according to the following file and folder structure:
SocietyName
The top-most folder, named with the society name. |
Project
The entire NetBeans IDE project folder contains the project source codes. The project folder must be able to be opened in NetBeans IDE without any problem. |
Readme.txt
Include the demo User accounts for different roles, like username and password in the Readme.txt file. For the tutor to test the system |
SocietyName.sql
Includes all sql code ("export" function in phpMyAdmin) for creating the tables used in the assignment. For tutors to test the system. |
Web projects that cannot be opened and successfully interpreted in NetBeans or Visual Studio Code will be rejected and may be required to submit a working project. It is recommended that you comment out sections containing errors that you cannot resolve so that your application can run successfully. Please note the unresolved error in the Readme.txt file so that the tutor is aware of it.
5.1 Plagiarism |
Works submitted must be ORIGINAL. You can discuss with your friends. You can research from web resources. However, the program must be your own work. You can teach your friends how to solve a certain programming problem, but not to program for them. Do not share your program and source codes with other teams.
The student who copies AND the student who provides an opportunity for others to copy his/her programs, will both be penalized. BOTH PARTIES will receive ZERO (0) MARK for this assignment. The matter will also be brought to the school for further disciplinary action.
5.2 Late Submission |
Late submission which does not supported by VALID and CONCRETE reason will be penalized according to the following:
No. of Day Late |
Deduction |
1 to 3 days |
10% from the assignment marks earned |
4 to 7 days |
20% from the assignment marks earned |
more than 7 days |
100% from the assignment marks earned |
2024-02-25