Home > Sample essays > Web-Based Event Management -Create an Event w/ Web Based Event Mgt

Essay: Web-Based Event Management -Create an Event w/ Web Based Event Mgt

Essay details and download:

  • Subject area(s): Sample essays
  • Reading time: 11 minutes
  • Price: Free download
  • Published: 1 April 2019*
  • Last Modified: 23 July 2024
  • File format: Text
  • Words: 3,529 (approx)
  • Number of pages: 15 (approx)

Text preview of this essay:

This page of the essay has 3,529 words.



Web Based Event Management

Submitted By

Farrukh Javed

2767/FBAS/BSCS4/F13

Project Supervisor

Dr. Jamal Abdul Nasir

Assistant Professor

Department of Computer Science and Software Engineering Faculty of Basic and Applied Sciences

International Islamic University Islamabad (2017)

Dissertation

Dissertation submitted to the Department of Computer Science and Software Engineering, International Islamic University, Islamabad’s Partial Fulfillment of the Requirements for the Award of Degree of Bachelors of Science in Computer Science.

Dedication

I dedicate this project to ALMIGHTY ALLAH who created us and made me able to usemyabilitiesandstrengthtocompletethistaskasmyfinalyearproject.Thisproject is also dedicated to my parents, my siblings, respected teachers, supervisor andfriends who supported and helped me in allcircumstances.

Declaration

IherebydeclarethatIdevelopedthissoftwareandthisreportentirelyonthebasisof my personal efforts made under the sincere guidance and support of my project supervisorDr.JamalAbdulNasir.Noportionofthisworkpresentedinthisreporthas been submitted in support of our application for any other degree or qualification of this or any other University or institute of learning. I further declare that this software and all associated documents, reports are submitted as partial requirements for the degree of Bachelor of Science in ComputerScience.

Farrukh Javed

2767/FBAS/BSCS4/F13

Abstract

In this project, I have built a web application that allows users to create an event of any type and make changes according to their requirements. User can select various event options e.g the number of people, catering, decorations etc and will get an estimate of the total cost. The user can also view various package deals offered and can avail discount package deals. User can then make orders which will be sent to the administration and will accordingly receive the response from the admin. This project also has an admin panel to maintain account management, event planning, inventory management as well as all the employees management.

Acknowledgement

Itake this occasion to thank God Almighty for blessing us with his grace and taking ourendeavortoasuccessfulculmination.Iextendoursincerethankstomysupervisor, Dr. Jamal Abdul Nasir, for providing me the right guidance and advice at the crucial junctures and for showing me the right way. I extend my sincere thanks to other respected faculty teachers, for providing me the right guide. Last but not the least, I would like to thank my friends and family for support and encouragement they have given me during the course of ourwork.

Web BasedEventManagement v

Project in Brief

Project in Brief

Project Title Event Management

Objective A web application which allows users to create an event as desired and get an estimate or make orders for the required services.

Undertaken By Farrukh Javed – 2767-FBAS/BSCS4/F13

Supervised By Dr. Jamal Abdul Nasir

Date Started September 2017

Date Completion November 2017

Language and Technology Used

 PHP

 JavaScript

 Bootstrap

 Html

 CSS

 MySQL

Tools Used

 XAMPP

 Sublime Text

 phpMyAdmin

Operating System Microsoft Windows 8

Web BasedEvent Management vi

Table ofContents

Table of Contents

1. Introduction

1.1 ExistingSystem……………………………………………………………….…………2

1.2 ProjectObjective………………………………………………………………………………….3

1.3 ScopeofProject………………………………………………………….………………….3

1.4 ProposedSystem………………………………………………………………………..3

2. Requirements and System analysis

2.1 UseCaseModel…………………………………………………………………………5

2.2 Use CaseBrief Detail…………………………………………………………………..6

2.3 Use CaseDescription Detail…………………………………………………………….7

2.4 Domain Model…………………………………………………………………………..18

2.5 ActivityDiagram……………………………………………………………………….19

3. System Design

3.1Sequence Diagrams…………………………………………………………………….203.2 Class Diagram.……………………………………………………………………………………….25 3.3 Entity Relationship Diagram…………………….…………………………………….26

4. Implementation

4.1 Details of Implementation ToolsandTechnologies…………………………….………29

4.2.DeploymentDiagram…………………………………………………………………31

5. Testing

5.1 SoftwareQualityAssurance……………………………………………………………30

5.1.1 SoftwareQualityControl…………………………………………………………….30

5.1.2 TestCase…………………………………………………………………………….31

6. Conclusion

6.1 Projectscreenshots………………………………………………………………………38

6.2 FutureWork……………………………………………………………………………..48

Web BasedEventManagement vii

Chapter 1

Introduction

1 Introduction

EventManagementisawebbasedapplicationinwhichadmincanrunitsbusinessandcanmanageallits account management as well as employee management. It provides a good and user friendly GUI. With thisapplication“EventManagerOwner”canselltheirservicesandproducts.Theapplicationprovidesthe owners to registered, login and add their events with image and details including the services they provides. That helps hundreds of users on a daily basis to find the right products that fit their needs and fulfils theirrequirements.

Withduetothisapplicationusercansearchandselectthedeals.Usercansearchtheirrequiredproducts by searching it through special deals which helps them to find best deal according to their needs. Therefore this application almost remove the manualsystem.

Also Event Manager Owner can manage employee by editing or deleting their id. This application will allow its customer to rent products online.

It gives option to user to plan their event themselves and rent the products required.

User can also give us complete authority to organize their event according to their wishes and they can also option for best deals available.

1.1 Existing System

There is no existing system yet like this application. This application fulfill basic need of

users and also help the owner to manage all their business. Yet there is no such application which helptheusertorenttheproductsonlinetillnow,althoughtherearemanymanagementsystemfor event managements but there is no website which help the user to choose their requiredproducts.

1.2 ProjectObjective

The objective of this web app is to create a web application through Web based Event Management can extend their business to online. In order to build such an application complete web support need to be provided. An entire and productive web application which can give the web based knowledge is the fundamental goal of the venture. This way, they will be able to attract a bigger market and sell services items to more customers. This web application will also make it easier to manage the orders. This web facilitate the people in managing the events.

1.3 Scope ofProject

This system can be implemented to any event creator everywhere in Pakistan. The system recommends a user’s with facilities which can make users happy.Since the application is available in the web it is easily accessible and always available.

1.4 ProposedSystem

In the proposed system user’s require not go to the search the event owners manually and fight over the price of the products. Users can search event of their choice through his browser on the smartphone as wellasontheotherdevicesaswell.TheEventownerwillbemainpartofthesystem.Eventownerinsert their product to sell.

Chapter 2

Requirements and System Analysis

2 Requirements and SystemAnalysis

Requirements Analysis is also called requirements engineering, a process in which “whatis to be done” is elicited, modeled and communicated. The descriptions of the services and constraintsaretherequirementsforthesystemtheprocessoffinding,analyzing,documentingand checking these services and constraints. The first use of the term 'requirements engineering' was probablyin1979inaTRWtechnicalreportbutdidnotcomeintogeneraluseuntilthe1990swith thepublicationofanIEEEComputerSocietytutorialandtheestablishmentofaconferenceseries on requirements engineering. In the waterfall model, requirements engineering is presented asthe first phase of the developmentprocess.

In next pages we have inserted the Use Case Model for the system and detailed use case descriptions for the system.

2.1 Use CaseModel

Use case model gives us information in a visual form about the system and itsenvironment. In a quick glance it can give us the idea about how the user is interacting with the system. This generally include a UML use case diagram to show the name of use case and actors, and their relationships.

Ausecasediagramisagraphicdepictionoftheinteractionsamongtheelementsofasystem.Ause case is a methodology used in system analysis to identify, clarify, and organize system requirements.UsecasediagramsareemployedinUML(UnifiedModelingLanguage),astandard notation for the modeling of real-world objects andsystems.

2.1.1 Use CaseDiagram

Fig. 2.1 – Use Case Diagram

2.2 Use Case BriefDetail

2.2.1 Registration

Use Case ID: UC-001

Use Case Name: Registration

Description: This use case describes the process by which users can Sign up for the first time

Actors: User/Admin

2.2.2 Log In

Use Case ID: UC-002

Use Case Name: Log In

Description: This use case describes the process by which users can login

Actors: User/Admin

2.2.3 Add Products

Use Case ID: UC-003

Use Case Name: Add products

Description: This use case describes the process by which admin can add products and deals.

Actors: Admin

2.2.4 SearchDeals

Use Case ID: UC-004

Use Case Name: Search deals

Description: This use case describes the process by which user can search deals.

Actors: User

2.2.5 Select Products

Use Case ID: UC-005

Use Case Name: Select products

Description: This use case describes the process by which user views all the products and select the required products.

Actors: User

2.2.6 ManageAccount

Use Case ID: UC-006

Use Case Name: Manage Account

Description: This use case describes the process by which admin can manage all the financial accounts as well as employee account as well.

Actors: User

2.2.7 View Data

Use Case ID: UC-007

Use Case Name: View Data

Description: This use case describes how admin can view data.

Actors: User

2.2.8 Profile

Use Case ID: UC-008

Use Case Name: Profile

Description: This use case describes how user can view his profile and make selected changes if wanted. User can also remove his account from here.

Actors: User

2.3 Use Case DescriptionDetail

2.3.1 Registration

Use Case ID: UC-001

Use Case Name: Registration

Description: This use case describes the process by which users can register for the first time

Actors: User/Admin

Pre-condition: 1. Working internetconnection

2. Facebook/Gmail account or an Email account

Post-condition: User will be redirected to homepage

Flow: 1. User will click onregistration

2. User will enter credentials

3. After verification user is loggedin

Exception: N/A

Frequency of use: Once per session

2.3.2 Log In

Use Case ID: UC-002

Use Case Name: Log In

Description: This use case describes the process by which users can login

Actors: User/Admin

Pre-condition: 1. Working internetconnection

2. Facebook/Gmail account or an Email account

Post-condition: User will be redirected to homepage

Flow: 1. User will click onlogin

2. User will enter credentials

3. Web app will verify the user fromdatabase

4. After verification user is loggedin

Exception: N/A

Frequency of use: Once per session

2.3.3 Add Products

Use Case ID: UC-003

Use Case Name: Add Products

Description: This use case describes the process by which admin can add products and the deals.

Actors: Admin

Pre-condition: 1. Working internetconnection

2. User is loggedin

3. Web App is fullyloaded

Post-condition: Users can see all the new deals and products added by the admin

Flow: 1. Admin will go to the producttap.

2. Admin select the new product and deal and then addthem.

Exception: 1. Internet stops working.

Frequency of use: Numerous

2.3.4 SearchDeals

Use Case ID: UC-004

Use Case Name: Search Deals

Description: This use case describes the process by which user can search the products and deals according to their requirement.

Actors: User

Pre-condition: 1. Working internetconnection

2. Web App is fullyloaded

Post-condition: User will be shown all existing products and deals in the web.

Flow: 1. User will go to searcharea.

2. They search products by Hostel namedeals.

Frequency of use: Numerous

2.3.5 Select Products

Use Case ID: UC-005

Use Case Name: Select Products

Description: This use case describes the process by which user select all his required products according to their requirement.

Actors: User

Pre-condition: 1. Working internetconnection

2. Web App is fullyloaded

Post-condition: Product will be listed as selected by the users

Flow: 1. User will go Invitespage

2. Web App will show the friends in in friend listtab

Frequency of use: Numerous

2.3.6 ManageAccount

Use Case ID: UC-006

Use Case Name: Manage Account

Description: This use case describes the process by which admin can manage all the financial accounts and employee management as well.

Actors: Admin

Pre-condition: Working internet connection

Web App is fully loaded

Post-condition: Admin can see all the account details.

Flow: 1. Admin will go to account management

2. Web App will show existing account details and a button to add newdetails.

Frequency of use: Numerous

2.3.7 View Data

Use Case ID: UC-007

Use Case Name: View Data

Description: This use case describes how Admin can view all the data.

Actors: Admin

Pre-condition: 1. Working internetconnection

2. Admin is loggedin

3. Web App is fullyloaded

Post-condition: Admin can see all data.

Flow: 1. Admin will go to viewtap.

2. Admin can see all data.

Frequency of use: Numerous

2.3.8 Profile

Use Case ID: UC-008

Use Case Name: Profile

Description: This use case describes how user can all his data and profile.

Actors: User

Pre-condition: 1. Working internetconnection

2. User is loggedin

3. Web App is fullyloaded

Post-condition: Profile will be changed as per user’s need

Flow: 1. User will go to profilepage

2. Web App will display the profile of theuser

3. User can make selected changes

Frequency of use: Numerous

Frequency of use: Seldom

2.4 Domain Model

This domain model diagram.

Fig. 2.4 – Domain Model

2.5   Activity Diagram

This Activity Diagram.

Fig. 2.5 – Activity Diagram

Chapter 3

System Design

3 SystemDesign

We have designed our system in a way that it consists of two different parts. One part is the Client-side, and the other is Server-side. The following diagram shows different components of the system:

Figure 3.1 – System Design

3.1 SequenceDiagrams

Asequencediagramisakindofinteractiondiagramthatshowshowprocessesoperate with one other and in what order. It is a construct of a message Sequence Chart. A sequence diagram shows object interaction arrange in timesequence.

3.1.1 Registration

This sequence diagram describes the process by which user can register to the system.

3.1.2 Login

Fig 3.2 – Registration

This sequence diagram describes how the user can log in to the system.

Fig. 3.3 Log In

3.1.2 Profile

This sequence diagram describes how the user can view and make changes to his profile.

Fig. 3.4 – Profile

3.1.3 EventManagement

This sequence diagram describes the event management process.

Fig. 3.5 – Event Management

3.2 Class Diagram

This class diagram.

Fig. 3.2 – Class Diagram

3.3Entity Relationship Diagram (ERD)

This entity relationship diagram.

Fig. 3.3 – Entity Relationship Diagram

Chapter 4

System Implementation

4 SystemImplementation

System implementation is the process of defining how the information system should be built ensuring that the information system is operational and used and meets quality standard. Implementation is the process of realizing the design as a program.

We have implemented Event Management using different modern technologies and techniques. The choice of the technologies used was based on the principle of modularity and performance.

Now with the technologies implemented the system design diagram that we have shown in chapter 3 looks like this:

Fig. 4.1 – System Design

4.1 Details of Implementation Tools andTechnologies

The details of the languages, tools and technologies we used are following:

4.1.1 JavaScript

JavaScript, a reverse-engineered implementation of Netscape's JavaScript, was part of Internet Explorer. JavaScript was also available for server-side scripting in Internet InformationService.InternetExplorer3alsoincludedMicrosoft'sfirstsupportforCSSand variousextensionstoHTML,butineachcasetheimplementationwasnoticeablydifferent to that found in Netscape Navigator at the time. These differences made it difficult for designers and programmers to make a single website work well in both browsers, leading to the use of "best viewed in Netscape" and "best viewed in Internet Explorer" logos that characterized these early years. JavaScript began to acquire a reputation for being one of the roadblocks to a cross-platform and standards-driven Web. Some developers took on thedifficulttaskoftryingtomaketheirsitesworkinbothmajorbrowsers,butmanycould not afford thetime.

4.1.2 PHP

PHP code may be embedded into HTML or HTML5 markup, or it can be used in combinationwithvariousWebtemplatesystem,andWebmanagementsystem.PHPcode is usually processed by a PHP interpreter implemented as a module in the web server or as a Common Gate Interface (CGI). The Web Server software combines the results of the interpretedandexecutedPHPcode,whichmaybeanytypeofdata,includingimages,with the generated web page. PHP code may also be executed with a command-line  interface (CLI) and can be used to implement standard alonegraphics.

4.1.3 Bootstrap

Bootstrapping is any test or metric that relies on random sampling with replacement. Bootstrapping allows assigning measures of accuracy   (defined   in   terms   of   bias,   variance, confidence interval, prediction error or some other such measure) to sample estimates. This technique allows estimation of the sampling distribution of almost any statistic using random sampling methods. Generally, it falls in the broader class of resamplingmethods.

4.1.4 HTML

Hypertext Markup Language (HTML) is the standard markup language for creating web pagesandwebapplications.With CascadingStyleSheets (CSS)andJavaScriptitformsatriadof cornerstonetechnologiesforthe WorldWideWeb.Webbrowsers receiveHTMLdocumentsfrom a webserver or from local storage and render them into multimedia web pages. HTML describes the structure of a web page semantically and originally included cues for the appearance of the document

4.1.5 CSS

Cascading   Style Sheets (CSS) is a style sheet language used for describing   the presentation of a document written in a markup language. Although most often used to set the visual style and user interfaces written in HTML and XHTML, the language can be applied to anyXMLdocument,includingplainXML,SVGandXUL,andisapplicabletorenderinginspeech,or on other media. Along with HTML and JavaScript, CSS is a cornerstone technology used by most websites to create visually engaging webpages, user interfaces for web applications, and user interfaces for many mobileapplications.

4.2 Deployment Diagram

Fig. 4.2 – Deployment Diagram

Chapter 5

System Testing

5 SystemTesting

5.1 Software Quality Assurance

A set of activities designed to evaluate the process by which products are developed or manufactured. Software Quality Assurance Plan(SQAP) consists of those procedures, techniques and tools used to ensure that a product meets the requirements specified in the softwarerequirements specification.

5.2 Software Quality Control

SoftwareQualityControlisthefunctionthatcheckswhetherthesoftwareproject follows its standards processes, and procedures, and that the project produces the desired internal and external (deliverable) products i.e. output.

5.2.1 Black BoxTesting

Blackboxtestingisalsoknownasspecification-basedtesting.Blackboxtesting referstotestactivitiesusingspecification-basedtestingmethodsandcriteriatodiscover program errors based on program requirements and productspecifications.

The major testing focuses:

(1) Specification-based functionerrors

(2) Specification-based component/system behaviorerrors

(3) Specification-based performanceerrors

(4) User-oriented usage errors

(5) Black box interfaceerrors

5.3 TestCase

Following are the Test Cases for our project (Event Management):

5.3.1 Registration

TC1: Registration

Test Case ID: UC-001

Wrote By: Farrukh Javed

Test Type: Black box testing

Product Name: Event Management

Test Item: Web App

Documented Date: 15/10/2017

Test Suite: 1a

Version Number: 1.0

Test case description: This test case is designed to successfully sign up

Operation procedure: 1. Go to index page

2. Click on theregistration.

3. Clicking on registration will open a modal which allows options to signup from Facebook, Gmail or Emailaddress.

4. Using Auth0, the user is authenticated and the Web App takes credentials fromAuth0.

5. Web App redirects to homepage.

Pre-conditions: Internet is required and Web App must be running

5.3.2 Login

TC2: Log In

Test Case ID: UC-002

Wrote By: Farrukh Javed

Test Type: Black box testing

Product Name: Event Management

Test Item: Web App, MYSQL

Documented Date: 15/10/2017

Test Suite: 1a

Version Number: 1.0

Test case description: This test case is designed to successfully log in

Operation procedure: 1. Go to indexpage

2. Click on thelogin

3. Clicking on login will open a modal whichallows options to login through email which you registered.

4. The user is verified and his credentials is sent to the WebApp.

5. Web App redirects to indexpage.

Pre-conditions: Internet is required, User must have created an account.

5.3.3 AddProduct

TC3: Add Product

Test Case ID: UC-003

Wrote By: Farrukh Javed

Test Type: Black box testing

Product Name: Event Management

Test Item: Web App, MySQL

Documented Date: 15/10/2017

Test Suite: 1a

Version Number: 1.0

Test case description: This test case is designed to successfully uploaded product data.

Operation procedure: 1. Admin will go to his productpage.

2. Web App will refresh to showhistory

Pre-conditions: Internet is required, Web App must be running, user must be logged in and they must have run test at least once

5.3.4 SearchProduct

TC4: Search Product

Test Case ID: UC-004

Wrote By: Farrukh Javed

Test Type: Black box testing

Product Name: Event Management

Test Item: Web App, MySQL

Documented Date: 16/10/2017

Test Suite: 1a

Version Number: 1.0

Test case description: This test case is designed to successfully search the product and deals.

Operation procedure: 1. User goes to productpage

2. Web App will display allproducts

3. User can option for specialdeal.

Pre-conditions: Internet is required and Web App must be running

5.3.5 Email Verification

TC5: Email Verification

Test Case ID: UC-005

Wrote By: Farrukh Javed

Test Type: Black box testing

Product Name: Event Management

Test Item: Web App

Documented Date: 16/10/2017

Test Suite: 1a

Version Number: 1.0

Test case description: This test case is designed for email verification

Operation procedure: 1. User goes to verificationpage.

2. Insert all data aboutproduct.

3. After Uploading Email will be sent after click on link, data will insert in todatabase.

Pre-conditions: Internet is required and Web App must be running n

5.3.6 Select Product

TC6: Select Product

Test Case ID: UC-006

Wrote By: Farrukh Javed

Test Type: Black box testing

Product Name: Event Management

Test Item: Web App, MySQL

Documented Date: 19/10/2017

Test Suite: 1a

Version Number: 1.0

Test case description: This test case is designed to select product by the user

Operation procedure: 1. User goes to productpage

2. User select theproduct.

Pre-conditions: Internet is required, Web App must be fully loaded and user must be logged in

Test Suite: 1a

Version Number: 1.0

Test case description: This test case is designed to view and create nearby events

Operation procedure: 1. User goes to Eventspage

2. User creates new events and can deletethem.

3. User views existing events happeningnearby.

Pre-conditions: Internet is required, Web App must be fully loaded and user must be logged in

Post-conditions: Events page will be updated.

Required test scripts: No

5.3.7 Profile

TC7: Profile

Test Case ID: UC-007

Wrote By: Farrukh Javed

Test Type: Black box testing

Product Name: Event management

Test Item: Web App, MySQL

Documented Date: 20/10/2017

Test Suite: 1a

Version Number: 1.0

Test case description: This test case is designed to view and make changes to Profile

Operation procedure: 1. User goes to Profilepage

2. User views theprofile.

3. User can edit hisdescription.

4. User can delete hisaccount.

Pre-conditions: Internet is required, Web App must be fully loaded and user must be logged in

Chapter 6

Conclusion

6 Conclusion

In this project we have developed a system in the form of web that can help both owner and user. Whereas previous works focused on either one of these aspects. Users can registration to our web application using Google, Face book or an Email Address. User can search different product and deals and select them according to their need. Profile of the user is created and the user can make desired changes. We have used moderntechnologiestomakethewebhighlyresponsiveandeasytomanage.Thiswork willbeusefultobothcommonusersinlearningaboutthemselvesandtoresearchersto produce more work in this area.

6.1 Project Screenshots

Below are some of the screenshot of our project:

6.1.1 Main Homepage

Figure 6.1.1 Main homepage

6.1.2 Sign Up

Figure 6.1.2  Sign Up

6.1.3 Login

Figure 6.1.3 Login

 6.1.4   Services

 

 Figure 6.1.4 Services

6.1.5   Gallery

Figure 6.1.5 Gallery

 

6.1.6  Contact Us

Figure 6.1.6 Contact Us

6.1.7   Request Order

Figure 6.1.7 Request Order

6.1.8   Booking Order

Figure 6.1.8 Booking Order

 6.1.9 Inventory Dashboard

Figure 6.1.9 Inventory Dash Board

 6.1.10  Admin Dashboard

Figure 6.1.10 Admin Dashboard

6.2   FutureWork

The work I did in this project presents many opportunities for future work. The following is a list of ideas that can improve upon this project and provide a guideline in this heading.

6.2.1   Video Calling

A conference all functionality can be added between users and admin where user can share his video live with admin.

6.2.2 Screen haring

This feature would allow users to share screens with admin in the group. Admin can remotely view the screen of other users in the group.

.

About this essay:

If you use part of this page in your own work, you need to provide a citation, as follows:

Essay Sauce, Web-Based Event Management -Create an Event w/ Web Based Event Mgt. Available from:<https://www.essaysauce.com/sample-essays/2017-11-28-1511854167-2/> [Accessed 15-04-26].

These Sample essays have been submitted to us by students in order to help you with your studies.

* This essay may have been previously published on EssaySauce.com and/or Essay.uk.com at an earlier date than indicated.