project sample

Event management is the application of project management to the creation and development of large-scale events such as festivals, conferences, ceremonies, weddings, formal parties, concerts, or conventions. It involves studying the brand, identifying its target audience, devising the event concept, and coordinating the technical aspects before actually launching the event.

The process of planning and coordinating the event is usually referred to as event planning and which can include budgeting, scheduling, site selection, acquiring necessary permits, coordinating transportation and parking, arranging for speakers or entertainers, arranging decor, event security, catering, coordinating with third party vendors, and emergency plans. Each event is different in its nature so process of planning & execution of each event differs on basis of type of event.

The events industry now includes events of all sizes from the Olympics down to business breakfast meetings. Many industries, charitable organizations, and interest groups hold events in order to market themselves, build business relationships, raise money, or celebrate achievement.

Event Management System includes 3 persons they are: Admin, Organizer and Visitor. Each and everyone has their own tasks to develop an application.

Table of Contents:

Table of Contents Executive Summary: 2 Introduction: 4 Project Plan: 5 Functional Specifications: 12 System Design Specifications: 14 Functional Test Plans: 19 Database: 24 Integration Tests Plan: 28 Program Environment and Tools: 29 Unit/Module Tests Plan: 29 Demo: 30 Conclusion: 45 References: 46

Event Management when compared to other traditional professions such as medicine, law and accounting is relatively a young field. It is an area that is growing rapidly and now represents hundreds of professionals who are responsible for planning, coordinating and evaluating a wide range of events all year round.

Event management is predominantly about creating an experience. Bearing in mind that first impressions last, it is important when embarking on any event regardless of its scale to take the correct approach and use the right techniques to ensure that your event is successful.

Event Management is a people oriented field. As a direct result of this fact the following areas will be addressed. The relevant skills and characteristics required for the field of Event Management. The importance of effective communication among stakeholders Leadership type skills necessary to motivate and empower teams to function at their maximum

People can visit an official site and can register with his details and can view the events available. He can select the event that he likes and can view entire details along with tickets and price so that he can book an event there itself.

Project Plan:

Table :PROJECT REPORT

Fig: Project SDLC

• Project Requisites Accumulating and Analysis

• Application System Design

• Practical Implementation

• Manual Testing of My Application

• Application Deployment of System

• Maintenance of the Project

Project Requisites Accumulating and Analysis

It’s the first and foremost stage of the any project as our is a an academic leave for requisites amassing we followed of IEEE Journals and Amassed so many IEEE Relegated papers and final culled a Paper designated by setting and substance importance input and for analysis stage we took referees from the paper and did literature survey of some papers and amassed all the Requisites of the project in this stage

Application System Design

In System Design has divided into three types like GUI Designing, UML Designing with avails in development of project in facile way with different actor and its utilizer case by utilizer case Page, flow of the project utilizing sequence, Class diagram gives information about different class in the project with methods that have to be utilized in the project if comes to our project our UML Will utilizable in this way The third and post import for the project in system design is Data base design where we endeavor to design data base predicated on the number of modules in our project

Practical Implementation

The Implementation is Phase where we endeavor to give the practical output of the work done in designing stage and most of Coding in Business logic lay coms into action in this stage its main and crucial part of the project

Testing

Unit Testing

It is done by the developer itself in every stage of the project and fine-tuning the bug and module predicated additionally done by the developer only here we are going to solve all the runtime errors

Manual Testing

As our Project is academic Leave we can do any automatic testing so we follow manual testing by endeavor and error methods

Deployment of System

Once the project is total yare we will come to deployment of client system in genuinely world as its academic leave we did deployment i our college lab only with all need Software’s with having Windows OS

Maintenance

The Maintenance of our Project is one time process only

The following is a 3 – tier architecture which divides the functionality of the application into 3 layers. These layers include Client layer or presentation layer, Application service layer and the third one is database layer.

Figure: Database Architecture for Event Management System.

Figure: GSU Event Management System Architecture

After clearly analyzing the functionalities of the application, the following information is gathered and we are treating them as the functional requirements. While gathering the information, we came to know different roles of the people who are involved in usage of this application. This application is basically used by 3 different types of users, they are Admin, Organizer and the visitor. Let us have the functional requirements of each user.

Admin Requirements:

View user’s login details: Admin can have the right to know the information about the users that when they are logging into their application and how much time they have spent with the application are recorded and they can be viewed by the Admin.

Edit/Delete Events: Admin is having the right to edit and delete the events. He can able to communicate with the organizers and convey the information.

Review the user’s list: Whatever the registrations had with the application, all the registrations can be viewed by the admin.

View the organizers list: There are different organizers will be there for organizing the events. The list of organizers for the event can be viewed by the admin.

Location Information: The information related to the event and the location where this event is organized will be known to admin.

Organizer Requirements: He is the person who will be organizing the events. He is having the information related to the events, he can create the events, edit the events, he can know the information about the payments, and he can view the events list created him.

To become an organizer, he has to register first with the application and then he can perform the organizer functionalities.

Registration: To become an organizer, he must register with the application by submitting the user credentials.

Login: After registering with the application, if the organizer wants to implement his roles and responsibilities then he has to login into the application. This is one sort of security that is provided to the application.

Create and Edit events: Organizer is having the right to create and edit events. All the necessary information which is related to the event will be given by the organizer.

Payments information: Organizer can know the details of the payments made by the user. All users’ payment information can be viewed by the organizer.

View list of events: An organizer can create more than one event, he can view all the events information which is created by him.

Visitor Functionalities:

The following are the operations which can be performed by the visitor when he entered the application. These functionalities include

Profile creation: User can create his/her profile by signing up with the application.

Search Facility: He can search the information of the events and about the information which is present in the application.

View the events information: User can view all the information about the events along with the images, videos and any other information which is related to the events.

Payments: He can able to make the payment for any of the event. All this information will be stored and at the later stages the same information can be viewed by the user.

Booking History: He will be knowing the information of the events and their bookings.

It is individual application and not running with any other application.

Currently there are no interactions with any other application. If needed, we can establish the interactions with different other services like payment gateways and others.

A. Registration page for the organizer and the visitor:

Visitor and the organizer should register, if the registration is completed successfully then all the details of the users will be stored in the database automatically.

B. Login page for the organizer and the visitor:

System establishes the security by providing the login and registration process. It checks whether the user is valid user or not.

C. Applying Filters:

Users can apply filters in searching process. This will able to reduce the user burden as well as the search time.

D. Payments page. Application allows the user to make the payment by using the payment page. This type of payment is much secured, and the user can trust the payment system which is implemented.

If there are threats, then there may be a chance of occurring vulnerability which may breakdown the running of application. To overcome such kind of threats, from the starting phase onwards one must concentrate on the risk management process, which will be taking care of such things. This kind of risk management will be done for different sort of reasons, out of which the main 4 important reasons are given below.

1. There will be different disasters in the implementation of software like schedule slippage, cost increments, requirements missing etc., will occur. These things should be avoided by implementing RMM plan.

2. Requirements should be very clear before implementing the application. Once the application implementation is completed, then there should not be any rework to be done on the project. This may cause the increase of 50 percent of the cost.

3. One should avoid the win-win software solutions.

4. No need of implementing the error detection, prevention strategies when there is everything going well, this kind of implementation may lead to schedule slippage, cost over runs etc.

All these steps should be implemented in the risk management plan so that there won’t be any errors or inconsistencies in the implementation of the application.

Functional Specifications:

Functional specifications are the business operations that will be had with the organizations. These specifications should be finalized in the first stage of the project development, so that the developmental activities will be done according to the requirements.

To identify the complete functional specifications of any of the business, one need to know different types of the stakeholders, here, and this organization is having three different types of users are there like the administrator, event handler and the user.

Administrator: The following are the operations that will be doing by this person.

1. He can directly log into the application. After logging into the application he will be provided an interface which consists all the operations that he will be doing.

2. Information about the even handler can be seen by the administrator, apart from this he is having the right to give the permission to the event handlers for the completion of the registration process.

3. There should be communication interface between the event handler and the administrator to exchange the information.

4. If any of the event should be published on the application, then prior approval of the administration is compulsory.

5. The information which is related to the event handlers can be viewed by the administrators.

6. Events information can be seen by the administrator.

7. Deletion of the evens can be done by this person.

Event Handler:

1. For any of the event handler, he should be identified by the application, for that reason there is a registration process need to be completed by the event handler.

2. Events can be edited, added and deleted by the event handler.

3. Viewing the information related to the events.

4. Payments and tickets information can be viewed by the event handler.

5. This registration should be permitted by the admin, after acceptance of the registration then he will be able to create the events.

6. This events should be accepted by the admin, then only it will gets published in the web.

7. Information search facility is provided to the event handler.

8. Communication between the event handler and the users should be established.

User:

1. Without any registration with the application, view of the information related to the events can be possible.

2. Information search should be provided.

3. Tickets booking and the payments options should be provided.

4. Event handlers contact information should be provided so that the user can able to establish the communication.

UML Design:

Use-case Diagram:

Fig: Use-Case Diagram

Organizer Activity Diagram:

Figure: Organizer Activity Diagram

Admin Activity Diagram:

Figure: Admin Activity Diagram

Visitor Activity diagram

Figure: Visitor Activity diagram

Sequence Diagrams:

Admin:

Fig: Admin Sequence Diagram

Organizer:

Fig: Organizer Sequence Diagram

Visitor:

Fig: Visitor Sequence Diagram

Functional test plans are done practically whether each and every task executed and get expected results or not. We have three persons they are Admin, organizer, visitor so that have to check they are performing their tasks should check practically. Admin can login directly by giving his username and password when he is entered those details it will check whether details are matched with details that are stored in database or not. If he enters matched details then he will view his home page which includes Events, Organizers list and Visitors list he can track their details like when they signed in and when organizer crested an event and visitor booked events. If Organizer is new organizer then we have another option before login that is new user register here by clicking on that we will have new page for organizer registration so that organizer has to enter all the details includes his personal details contact number etc., after entering all those details by clicking on register button that details will stored in database which are useful when he wants to sign in. After sign in he will enter in to his home page includes event registration, events (organizer’s) so that he can create an event in event registration page it will store in database includes details like event id, event description, event date, time, place, image etc., he can also view his events in another page that his created events along with viewing he can also edit/delete an event and can view visitors list who booked his events. Event management system is mainly customer based, when visitor wants to view the events he has to login if he is new user he has to register by entering all his details which will stores in database. He can login by using username and password. After login he can view all the events of all organizers and can book an event and then proceed for the payment those all will store in database.

Test Case 1: Admin Login

Test Case 2: Organizer Registration:

Test Case 3: Organizer Login:

Test Case 4: Visitor Registration:

Test Case 5: Visitor Login:

Test Case 6: Event Registration:

Test Case 7: Book Event

Test Case 8: Payment details:

Table: Admin Table

Table: Event Details Table

Table: Organizer Table

Table: Payment Details Table

Table: Booking details Table

Table: Ticket Prices Table

Table: Event Date Table

Table: Visitor Details Table

E-R Diagram:

Fig: E-R diagram

Firstly here we have three members they are Admin, Organizer and Visitor. Admin has to login directly can track the details of both organizer and visitor. Organizer has to register first before login if he is new organizer ones he login he can create an event edit and delete an event and meanwhile he will have the list of events booked by visitor.

Visitor have to register if he is new visitor or else he can directly login by giving username and password when he logged in he can view all the events created by many organizers , he can visible in events there is an organizer id belongs to that event, after viewing all events he can book an event for what he is feels good in all matter like dates available, place etc., he can view how many tickets are available, cost of each ticket if he satisfied with all these he will book the tickets and proceed for the payment. After payment that visitor details will store in organizer then he can view how many tickets booked by visitor and how many remained.

Admin can view or track all the details of organizer and visitor that when they get logged in and organizer created events and visitor booked events all those details will available for admin by using their Id’s.

Performance is measured in terms of the output provided by the application. Requirement specification plays an important part in the analysis of a system. Only when the requirement specifications are properly given, it is possible to design a system, which will fit into required environment. It rests largely with the users of the existing system to give the requirement specifications because they are the people who finally use the system.

Software Requirements:

· Dot.Net Framework

· C# language

· IDE Visual Studio 2017

· Database SQL Server

First we will get a home page of event management system here we have Home, contact, about us, Admin login ,Organizer Login , Visitor Login. Here Contact page includes contact details, about us explains event management system. Admin can login directly by giving his username and password when he is entered those details it will check whether details are matched with details that are stored in database or not. If he enters matched details then he will view his home page which includes Events, Organizers list and Visitors list he can track their details like when they signed in and when organizer crested an event and visitor booked events. If Organizer is new organizer then we have another option before login that is new user register here by clicking on that we will have new page for organizer registration so that organizer has to enter all the details includes his personal details contact number etc., after entering all those details by clicking on register button that details will stored in database which are useful when he wants to sign in. After sign in he will enter in to his home page includes event registration, events (organizer’s) so that he can create an event in event registration page it will store in database includes details like event id, event description, event date, time, place, image etc., he can also view his events in another page that his created events along with viewing he can also edit/delete an event and can view visitors list who booked his events. Event management system is mainly customer based, when visitor wants to view the events he has to login if he is new user he has to register by entering all his details which will stores in database. He can login by using username and password. After login he can view all the events of all organizers and can book an event and then proceed for the payment those all will store in database.

Home page: This is the home page of an Event Management System.

Fig: Home Page

Contact Page: Contact Page consists of contact details.

Fig: Contact Details Page

About Us: This page explains about application.

Fig: Website Details Page

Admin Login Page: When admin wants to login he will used to login here and wants to enter username and password.

Fig: Admin Login page

Admin Home Page: After Admin login he can view this page which includes organizers list, Visitors list after tracking or visiting all those he can sign out.

Fig: Admin Home page

Organizer list:

This list contains the details of all organizer who are supposed to register the events and also update and delete the events. So that in this page Admin can track the organizer details by using select button and if he does not satisfied with events created by an organizer he can delete an organizer by choosing delete option.

Fig: Organizer details Page

Tracking details:

This page is about tracking organizer by an admin. When admin wants to track he chooses select option then he will get below mentioned details about an organizer which includes when organizer created an event and when he gets login.

Fig: Organizer tracking details Page

Visitor list: Visitor list contains the details of visitors. Here we will have so many visitors that they visit our event management but in this visitor list we are not supposed to list all those visitors. Only we will have the list of visitors who are completed their payment or who are supposed to book an event.

Fig: Visitor details Page

Tracking details: Tracking details of visitor is available for admin so that he can track visitor that when he gets login and what event he has booked by choosing select button in above diagram so that he can get all details as below.

Fig: Visitor Tracking Page

Logout: Logout page will appear when admin, organizer and visitor gets sign out.

Fig: Logout Page

Organizer Registration: New organizer wants to register in this page by giving all his details which include his name, contact num, email, address, password and then register so that by next time he can get login directly by giving correct username and password in login page.

Fig: Organizer Registration Page

Organizer Login: When Organizer wants to login he can get login here by giving username and password or if he is new organizer then he can choose new user register here option.

Organizer Home page: When organizer gets login he can view his home page which includes event registration and events.

Fig: Organizer home page

Event Registration: Event registration present in organizer home page because he is the one who create an event or register an event. In this page organizer will register an event by entering event name, event description, event time, date, place, uploading event image and then register. So that it will get store and visitor can view all those events and admin too.

Fig: Event Registration Page

Example : By filling all those details event get registered and when organizer upload an image can view on the right side of the screen.

Fig: Event Updated details Page

Ticket Details: After Registering an event have to fill ticket details of concern event it includes eventid, no of tickets available for that event , and price of ticket for that event. After filling all those details will get an alert message that event details saved successfully then click on ok it will go back to organizer home page.

Fig: Ticket Details Page

Organizer Events: My events page present in organizer home page that it means these are the events created by an organizer. Here we can see all the events and details of those events which entered while registering and also at the bottom of each event we can see three options that are Edit, Delete, View visitors list. So that organizer can edit the details of an event, he can delete an event and he can view the visitors who booked that event.

Fig: Event Details Page

Edit: Organizer can edit an event details here and click on update button so that the details get updated.

Fig: Modify the Event Details Page

Visitors list

When organiser wants to view visitor list he used to click on view visitor list on particular event that he registered so that he can get details as below.

Fig: Visitor’s Booking Page

Visitor Registration:

Visitor have to register in this page by giving all his details which include his name, contact num, email, address, password and then register so that by next time he can get login directly by giving correct username and password in login page.

Fig: Visitor Registration Page

Visitor Login: When Visitor wants to login he can get login here by giving username and password. If he is new user he can go the below option that is new user register here so that he will go to the registration page.

Fig: Visitor Login Page

Visiotor Home page: When visitor gets login he can view this home page. It includes all events that are presented and visitor events too.

Fig: Visitor Home page

Events: In this events page it contains all the events that are registered or created by an organizer so that visitor can view all these in his page and he can also view details of particular event by clicking on event then he will get entire details of that event.

Fig: Events Page

Search(by place):Here he can search an event by place or date between that by entering from date and to date so that he can view the events that are present between that dates. And when he given place name then events will display belongs to that particular place.

Fig: Search by Location

Search(by date):

Fig: Search by Date Events

Book Event: When he selected an event then entire details will display as follow for that particular event. Here we can see an option book event when visitor eants to book that event then he click on book event button and go for further details.

Fig: Book Event Page

Payment information: This page includes payment details of visitor here visitor booked event id , visitor id, amount for tickets booked will come defaultly he has to enter cardnumber, expiry date, cvv of card details manually so that the payment process will done.

Fig: Payment Details Page

Payment done:After completion of payment he will get this page.

Fig: After Successful payment

Visitor Events:

In visitor home page there is also option that my events these are the events that visitor get booked. When he completed all those processes mentioned above including payment so that those events for those he get booked all details of events will display in this page.

Fig: Booking details of visitors

My predictions are that in few years’ time the events industry will increase due to key factors such as:

The more individuals partaking in events the more profit an event makes therefore increasing overall profit for each classification of events.

Social media has a massive impact on the events industry due to details being updated and published for events to increase individuals awareness of events running therefore attracting a vast amount of potential customers to increase profit to the business. Tickets can now be brought via Face book, Twitter and websites this impacts the events easy access to tickets online which increases individuals to attend due to saving time to buy a ticket. 

Events are the refreshment for people from their routine life, now everyone prefers to participate in an event no matter of its cost.  Technology has made a massive change to the events industry. Apps for phones are designed so the public can get details on upcoming and ongoing events. As new technologies emerge, marketers will continue to reach out to new consumers through these new mediums.