Competition and Event Management System - Improved Web and Mobile Based Application for Jack Attack - Report Example

Abstract This paper proposes development of a competition and event management system on the web and a mobile friendly version of the same application. The paper explores the current system that is being used by the company, identifies gaps and proposes a modified system that can fill those gaps. The paper presents functional requirements, non-functional requirements, database model and technical requirements of the solution proposed. Table of Contents Introduction 3 Objectives of the proposed system 3 Functional requirements 3 Non-Functional requirements 6 Database model 6 Technical Requirements 7 User Interface 8 Timeline 9 Conclusion 9 References 11 Introduction The project is for Jack Attack, a brand of Darebin International Sports Centre that hosts a number of sports tournaments and events. The company already have a website http://jackattack.com.au but the website does not have many features except the search for events and club registration. There is a very little information written on the website about what is the company about. Thus, there is a need for improvement of the website by making it more dynamic and information rich that engages visitors in multiple ways. Objectives of the proposed system The objectives of the proposed system include: Cover details of play styles and tournaments on the website Simplify communication between members and the organization through the application Add a number of features to keep visitors engage or make them a part of process such as club registration, score-keeping, customization of entry with multimedia additions, access to results and schedules, etc. Keep the system reliable, safe and secure for users Allow different types of users to use the application in different ways relevant to their needs. Functional requirements The system would be used for managing the events and related communication between the project organization and its stakeholders. The functional requirements for the development of the competition and event management system include: Interface: The website would have some details captured through database and presented online such as [Swa07]: i. Provide tournament results and scheduling information to members on the desktop website as well as mobile device. The information would include various tournaments and events that would cover: A range of various play styles including: Traditional Play with specific number of ends Shots Up Play which has a particular score Sets Play with some shots per set Sets Play with some ends per set A range of various tournaments formats including: Side format having Multiple rinks with a cumulative score Side format having Multiple rinks, Majority of rink wins Knockout Sectional 3 Game Guarantees Sectional to Knockout progression Round Robin[USB16] ii. Keep the scores of the sport events online allowing members to access them? The scores have to be entered by the staff and it would get stored in the database which the application would use in the real time to display the scores on the WebPages. iii. Capture the information about each participant to record the history of sports[Aus14]. The information would include the participation and winning details. Registration: Allow members to register for entry into events through the online application. This would include user registration and event or club registration. i. User Registration: The system for user registration would have some features like: For registration, a user has to fill in an online form with details filled for name, email ID, and password. Password would act as a validation when the user would be log into the system after confirmation. In case a user forgets the password, a password reset link would be provided to the user over email. Users would be provided with a feature for log out of the system There would be three different types of registrations including registration for general club or event registering users, administrators and staff. Each would have separate panel for access[Rob92]. ii. Administrator panel: Administrator would be able to access all club and event information, make modification in schedules, and manage all events including main event and sub-events as well as manage staff access rights. Staff Panel: Staff would be allowed to register new events, clubs or tournaments, and add new users. The staff would also have provisions to make entries on the events such as the number of games player, players, and their scores. End users: These would be the people registering for tournament or club event. They would have limited rights like searching for events, registration to events, access to past event performances, and customization of personal information online[Daf11]. iii. Event or Club Registration: Once filled in the basic details for registration, the user would be able to register for the event by making payment to the company. User would be given options for selection of events uploaded in the interface from the events database[MEA15] iv. Build API integrated for the software to allow exchange of information with external software including National Members Database and Point of Sales. The system database would be connected to these databases such that queries can be run to display data from both the internal and external databases[The99]. v. There would also be some additional functionalities that the system would allow for including Put restrictions on participation with respect to age, gender, location, and disabilities allowing them different rights to registration Allow manual entry to be done by the administrators or staff users for adding entries to competitions and events in case they are taken manually from participants. Allow creation of custom entries and results pages with addition of images, colours and graphics. The system should allow staff and privilege users to print the event scorecards directly [Ash15] Allow members to select mode of communication and entry to competition or event using the online system such that their preferences gets stored in the back end database. Allow the use of multimedia for information sharing through other channels like webinars, social media, and so on. For this, the social media platforms API would be integrated to the application[Guy14]. Non-Functional requirements The website would also have to fulfil certain non-functional requirements of the business including: Performance requirements: The system needs to be reliable and must fulfil some performance needs such as: The loading time for all pages must not be more than 19 seconds. In case any requests are not processed by the system because of any reasons, the system should through relevant error message such as incorrect password message, unable to retrieve data message, and so on[Xia10]. Safety Needs: The web application should be safe for the users. Thus, a proper authentication mechanism should be used. During the password generation for registration, the system should only allow for strong alphanumeric passwords to enhance the security for users. Details of the users must be taken in specific formats and should be maintained properly. For this, a backup of the storage database would be created such that the information remains secure and is not lost in any case[Vai13]. Security requirements: The system should be secure such that the user data is not lost or hacked by a cyber criminal. Thus, antivirus and anti-malware applications would be installed over the application to keep the database secure. This security application would allow for detection of unauthentic or fishy activities and quarantine threats or send alerts to administrative users to take protective or correction actions in case of a security threat[Ami141]. Database model The database of the system would contain the details of events, tournaments, schedules, history, and users. Events/Matches: The database would have multiple events created with details of event ID, Title, duration, start dates, end dates, and description Users: There would be three levels of users of the web application including Administrators: Administrator database would contain details of their names, designation in the company, login ID, password, and job role. Staff/Coordinators: Staff database would contain details of their staff ID, names, designation in the company, login ID, password, address, job role, and clubs registered End Users: These would be the people who would be registering for the event or for the clubs online. The end user database would contain information about them including registration ID, payment done, login ID, passwords, club description, timestamps for visits, name, and address Sets: It will include the details of each set of the match that is match ID, jack position, winner of the set, result of the rest, score of the set and so on. Figure 1: EER diagram Technical Requirements The system would make use of some hardware and software components including: Hardware: A system having 8GB RAM, 1TB of hard disk space and I5 processor would be used Software: PHP as the programming language and MySQL as the database storing all the information required to be saved and retrieved via the web application. User Interface Timeline This chart presents the details of the development of the system which would take 3 months to develop starting from requirement gathering to purchase of hardware, learning of software, creation of wireframe, development of features, integration with external systems, user testing and the final go-live. Conclusion This proposal was created to suggest an improved web and mobile based application for Jack Attack which is currently running a website which lacks a variety of features. The proposed application is an improved version that would have more features and functionalities than the original website such as score keeping, integration with external applications, customization of details for users, and so on. The proposal suggests building of a new application using PHP connected with a MYSQL database that would contain details of three types of users including administrators, staff and general users registering for events or clubs. The paper provided the details of proposed system such as functional requirements, non-functional requirements, database model and technical requirements of the solution proposed. It can be said that the proposed application would provide a better engagement platform for users and it would also be better in its capability to fulfil non-functional needs like security and reliability of the website. References Swa07: , (Kodali, 2007), USB16: , (USBC, 2016), Aus14: , (Austen, 2014), Rob92: , (Zambetti, 1992), Daf11: , (Stuttard & Pinto, 2011), MEA15: , (MEA, 2015), The99: , (The MathWorks, Inc, 1999), Ash15: , (Mishra, et al., 2015), Guy14: , (Masterman, 2014), Xia10: , (Wang, et al., 2010), Vai13: , (Yalamanchili & Dr.P.Pandarinath, 2013), Ami141: , (Barate, et al., 2014), Read More