[Type the document title]

CHAPTER-1

INTRODUCTION

1.1 AIM:
The main aim of this project is to develop an web application which
helps to organize an event for event organizers, using this web application
event organizer can easily request the artist to perform in their event, and
this web application also helps the users to find out the events around them
with description.

1.2 Objective:

The main objective of this project is to develop an “Online Web

application” which helps Event organizer, artists and users. Before creating
an event, event organizer has to get registered in the port; once he gets the
confirmation from the admin he can create an event. Event organizers can
easily request an artist to perform in their event; request from the event
organizer is based on their event they are going to create and based on
artist’s genre. Once the artist availability is been confirmed event will be
created and user gets the details like event date, time, artist name, and entry
fee for that event.

Page 1
 [Type the document title]

1.3 Project Description:

“event management” is an online web application which provides services

to the event organizer, artists and customers. Event organizers and artists
have to register themselves by giving basic details to the web port, once
they get the confirmation from the admin they are able to access the web
application, event organizers can organize an event and artist gets the
requests from the Event organizes to perform in their create events, and
users gets the details about the events which are organized in their
surroundings. Events are created with name, description about an event,
entry fee for the uses and the artist details who is going to perform in that
created event.

Page 2
 [Type the document title]

CHAPTER-2
LITRATURE SURVEY

2.1 Existing and Proposed System:

2.1.1 Existing System: there is no proper online web application which

helps event organizers to organize an event, event organizers have to create an
event manually, and they have to advertise an event which is going to be
organized. And event organizer has to approach an artist manually to perform in
their created event, if the artist is not available they have to approach other artist,
it requires lots of human effort and it is a time consuming process.

2.1.2 Proposed System: to overcome with the disadvantages of

existing system we are promoting new web application, which work in
online and requires less human efforts and it promotes time effective
process. In the proposed system event organizer has to register himself ,
before creating an event he has to get the confirmation from the admin,
once the admin agreed with event organizer’s request, he can start creating
event. Like way the artist has to register and should get confirmation from
the admin, later artist gets the requests from the event organizers. And also
users gets the created events details.

Page 3
 [Type the document title]

2.2 Feasibility Study:

This Study i s important to get to know whether the system or web

application is feasibly correct by accepting the points like economic,
technique. Depends on statements budget will be estimated.

By conducting a feasible study a report can have a clear picture about the
project. For this complete and success of feasibility study the following
steps need to be considered.

2.2.1 Economical: As the name defines, software or application

need be analyzed for its complete use of the financial services. The
investment for the software or application development needs to be within
the limit of organization. By holding these points in the mind it shows that
the cost, need be within the budget.

2.2.2 Technical: This analysis is made by holding the technical terms in

mind that this part is of the software feasibility system. It verifies whether
the technical resources required for the implementation of the project is
available or not. In this instance the organization need to use technical
resources that are available to them.

Page 4
 [Type the document title]

2.2.3 Schedule Feasibility: This part is used to determine whether the

current project will be finished within the given time or not. And developed
within the given budget so that it is cost effective system.

2.3 Tools and Technologies:

2.3.1 HTML5: It is a markup language; html id used for the

development of the view pages. The tags are used to determine the html
pages. The html language is proposed with some new updates on every
release of new version. The latest version is html5, which provides extra
features like ranging coloring, date tags, and some features of validation
with it.

2.3.2 CSS3: CSS(Cascading Style Sheets) are used to design the html
tags that is for the decoration purposes. These are used within the html tag
or ended within the style tags. The latest version of the style sheets is css3
is been released.

2.3.3 JavaScript: JavaScript are light weighted languages and its a

scripting language, it is called as interpreted language that are executed
without pre-compilation. It contains only executable codes. This can be
used in multiple ways at the same time with html code by using script tag or
can be written in speared JavaScript files.
Page 5
 [Type the document title]

2.3.4 php: php is one of the procedure oriented language. It is one of

majorly using programming language because of its portableness and its
security level, it also have some extra ordinary features as follows;

✓Simple

✓Secure

✓Portable

✓procedure- oriented

✓faster

✓flexibility

✓Efficiency

2.3.5 MySQL: My Structured Query Language is the called as

MySQL. MySQL is the Relational DBMS (Database Management
System) used worldwide for the back end processing. It is an open source
available in the internet for all the OS like windows, Linux, mac etcs. It is
platform independent system. MySQL is used in many top rated companies
in the world. The latest version of the MySQL is 5.7 is been released.

Page 6
 [Type the document title]

2.4 Software and Hardware Requirements:

Software Requirements:

1. Mozilla firefox 46.0 or google chrome.

2. Any OS like windows or unix etc.

Developer Requirements:

1. PHP as Interface or Front-end.

2. CSS3, HTML5, JavaScript as front end.

3. Database is MYSQL 5.7.

4. Browsers are Mozilla or chrome or IE.

5. Operating system is Windows 7.

Page 7
 [Type the document title]

2.4.2 Hardware Requirements:

1. Minimum RAM is 4GB .

2. Hard Disk is 500 GB or More.

3. Processor is Intel i5 or above

Developer Requirements:

1. Minimum RAM is 4GB

2. Hard Disk is 500 GB or More

3. Processor is Intel i5 or above

Page 8
 [Type the document title]

CHAPTER-3
SOFTWARE REQUIREMENT SPECIFICATION

3.1 Introduction:

This section provides a clear picture of the Software requirement

specification. Main goal of this part is to provide an overall view of the
developing system or web application. This describes how customers,
e v e nt o r g an iz e r , and artists are interacted through the online and
provides an interface with each other.

3.1.1 Scope:

The main scope of the system or web application is, system allows the
event organizer to create an event and event organizer can request the artist
through online, if the requested artist not available he can re-request the
new artist. And users can get the created events details in this web
application.

Page 9
 [Type the document title]

3.1.2 Purpose:

The purpose of this part is to collect and analyze the overall system
requirements with respect to users, event organizer, and artists. And also it
explains the main goal of the project, software and hardware requirements
of the project. And how users get the events details, how organizer can
create an event and request an artist, and how the artist gets the requests
from the event organizer. and also, helps the project developers and
designers in further processes.

Users:
Users gets the event details like event date and time, artist who is going to
perform in the event and entry fee for that event.

Event organizer (client):

➢Event organizer will login into the system by entering the email and

password.
➢Event organizer will create an event and request artist to perform in his

event.
Artist:
➢Artist will login into the system by entering the email and password.

➢Artist gets an event request from the event organizer.

Page 10
 [Type the document title]

3.2 FUNCTIONAL REQUIREMENTS:

➢This section holds the features and essentials (requirement) of the project

modules. All the functional requirements will be tracked. The Event

organizer and artist will login using their credentials.

 Event organizer: creates an event and requests artist to perform.

 User: gets the event details which are created by the event organizers.

 Artist: artist gets the request from the event organizer.

 Register: Registration page used to register new event organizer and artist.

 Login: Helps the users in login Process.

 Payment gateway: Helps in online payment to users.

 Admin: admin has the overall control in the application

3.3 Non-functional requirements:

The non-functional requirements are considered as whole by the system

or application. Some of the non-functional requirements are:

Page 11
 [Type the document title]

➢Security

 There system errors will be handled.

 Users Personal data is maintained safely.

➢Software quality attributes

• This Software has quality attributes like available
best software should be used in the process of
development of an application
➢Business

rules
• System is been developed According to the
company standards and rules.

Page 13
 [Type the document title]

CHAPTER-4

SYSTEM DESIGN

4.1 System Perspective:

System i s a perspective of the s y s t e m a n d t o elaborate the model
that explains the system architecture in specified way.

4.1.1 Architecture design of system:

System design can be studied in the architectural design. The contents and
attributes of the web application or system explained throughout the
architectural design in system study. This architecture design represents the
three tire architecture means working procedure of model, view and controller.
It explains which layer is meant for designing and which layer helps in
database connectivity and which involves in controlling the workflow.

Page 13
 [Type the document title]

4.1.1.1 Three-tier architecture:

1. Presentation layer (view):

This layer is for users, all designing or presentation parts are developed
under this layer. Users interact with these layers in the presentation layer.
This layer contains of Graphical user interface (GUI). User interacts with
the system or web application using the browser.

2. Application layer (controller):

The application layer stands in a second layer in three tire architecture. It

contains the major parts in the project that is business logic which means
logical part of the project. This layer is also called as business logical
layer.

3. Database layer (model):

The database layer is to get connection with the database. This layer is
called model or database layer. Functions of this layer are performed in the
backend.

Page 13
 [Type the document title]

CHAPTER-5

DETAILED DESIGN

5.1 Usecase diagram:

The usecase represents the Actors performed in the system.

5.2 Sequence Diagram:

The sequence diagram explains the flow of the system.

5.3Activity Diagram:

It shows the flow of activities performed in the system.

5.4E-R Diagram:
Page 13
 [Type the document title]

It represents the various relationship between the entities.

CHAPTER-6

IMPL E ME NT AT ION

Implementation is the step where the theoretical design is turned into

actual working system. The system can be designed only after thorough
testing is done with the system.

It involves careful investigation and planning of the present system and its
constraints on the implementation, design of methods to make the changes
over, and an evaluation of change over methods are part from planning.

Page 13
 [Type the document title]

Two major tasks of preparing the implementation are Training and

Education.

The implementation phase includes several activities. The

required hardware and software requirements are carried out. This system
may require some software to be developed. For this purpose, programs
are pre written and tested. The user can then changes over to his/her new
fully tested system or web application and the old system is discontinued.

SC REE NS HOTS :

Page 13
 [Type the document title]

CHAPTER-7
SOFTWARE TESTING

Any software or web application after development will be tested for its
specified output. Without testing any software or web application is
incompatible and not worth of using it. In simple testing it can be
defined by t h e performance of verification and validation which checks
Page 13
 [Type the document title]

the input for a valid and required output.

There are two types in testing one is “Black Box” and other is “White
Box”. The anatomic testing is called as black box system testing. The white
box testing includes ascendency a n d flows of project, coding methods etc.

This is all about verifying the developed system whether the software
or web application is working in a proper way or not. While testing the
software many errors may occur in the system. To overcome those errors
predicted and certain measures has to be taken while testing the system.
The software is tested to meet the user requirements. The software or
application is tested to its best capability.

7.1.1 Purpose of testing:

• To Minimizing the expenses of programming development or system

development.

• Whether software or web application meets the user requirement or not.

• Honest towards customers.

Page 13
 [Type the document title]

7.2 Testing Strategies:

➢Unit testing:

In “event management” unit testing is done for the followings. The text box
for entering name of the user should be in varchar (character), email should
contain a dot and at(@) symbols. If these things are not done in a proper
way then the event organizer or artist may enter the invalid data like
numbers for character field as data is mandatory.

➢Integration testing:

Integration testing will be done by combining the number of sub units into
a single unit to complete the system or web application. The tested sub
units will be integrated to form a new system. The page navigation or
diversion from one to another or between the units will be done.

In “event management”, bottom-up approach testing is been tested. Which

is developed to tested and the results are registered.

Page 13
 [Type the document title]

➢User testing:

User testing is all about the software being stored into the system of the
users. So that the requirements have been made and the software matches
the user requirement.

7.3 Test cases:

Test cases for Artist/ Client
Test
Case
Number Testing Scenario Expected result Result

REGISTRATION
TESTING

Clicking submit Alert "Please

TC – 01 Pass
without entering Enter all

Page 13
 [Type the document title]

details details"

Clicking submit Alert "

without entering Username field
TC – 02 Username is required" Pass

Clicking submit Alert "Email id

without entering field is
TC – 03 email id required " Pass

Clicking submit Alert "Phone

without entering number field is
TC – 04 phone number required " Pass

Clicking submit Alert "Address

without entering field is
TC - 05 address required " Pass

Clicking submit
without selecting Alert “Please
TC - 06 jauner select Jauner” pass

Clicking submit
for new client / Successfully
TC - 07 artist registration registered Pass

LOGIN

Page 13
 [Type the document title]

TESTING

Alert "Please
Clicking submit enter the
without entering username and
TC – 01 login details password" Pass

Alert
Clicking submit "Password
without entering field is
TC – 02 password required " Pass

Clicking submit Alert "

without entering Username field
TC – 03 Username is required " Pass

Clicking submit Alert "Invalid

entering wrong Username or
TC – 04 Username Password" Pass

Clicking submit Alert "Invalid

entering wrong Username or
TC – 5 password Password" Pass

Clicking submit
entering wrong Alert "Invalid
Username and Username or
TC – 6 password Password" Pass

Page 13
 [Type the document title]

ADMIN
MANAGEMENT
TESTING

Admin capable to
accept/reject Admin is
client/artist capable to
registration accept/reject
TC-1 request. new user. Pass

Admin capable to Admin is

accept/reject new capable to
event created by accept/reject
TC-2 client. new event.

CLIENT
WORKFLOW
TESTING

Alert "Event
Client capable to successfully
TC-1 create new event. created" Pass

Page 13
 [Type the document title]

Client capable to
select artist based Alert "Event
on jauner for new created
TC-2 event. successfully " Pass

Client can view

accepted/rejected
events list with Yes, client will
TC-3 reason. get the details. Pass

ARTIST
WORKFLOW
TESTING

Artist is able to Artist gets the

accept / reject the details for the
event request by new event
TC-1 the client request Pass

Artist can view

booked dates in Yes, Artist will
TC-2 calendar, get the details.

CHAPTER-8

Page 13
 [Type the document title]

CONCLUSION

“event management” is a w e b a p p l i c a t i o n which is developed to

help an event organizer to create an event in online, and to request the
artist to perform in his created event, if the artist is not available in that
time event organizer is able to re request the new artist to perform in his
created event. This system meets the user requirements. and this system or
web application requires less time consumption and reduces human efforts,
this system or web application works as user friendly system. And user is
able to get the events details which are organized in and around. But the
system has over all controlling by the admin.

Page 13
 [Type the document title]

CHAPTER-9

FUTURE ENHANCEMENTS

➢In future customers get the events notifications based on their location.

➢Customers can rate the event which was held by the organizers.

➢Google map integration with gps location fetching.

Page 13
 [Type the document title]

APPENDIX BIBLIOGRAPHY
Referenced Books:

Software Engineering 9th edition by Ian Sommerville

An integrated approach to software engineering by pankaj jalote

The code igniter tutorial.

Referenced websites:

http://www.w3schools.com/html

http://www.tutorialspoint.com/software_engineering/

https://www.tutorialspoint.com/codeigniter/

Page 13