A

Project Report On
Event Management

INDEX
Sr Subject Page
no no:
1 Project Profile 5
1.1 Definition 5
1.2 Scope 5
1.3 Objective 6
2 System analysis and specification 7
2.1 System analysis 7
2.2 User requirement 8
3 System Requirement and specifications 9
4 SDLC 10
5 Overview of .net Technology 14
6 System Design 17
6.1 Data Flow Diagram 17
6.2 E-R Diagram 19
6.3 Data Dictionary 20
7 Screenshot 22
8 Testing 37
9 Enhancements 39
(8.1) Advantages 31
(8.2)Limitation 36
(8.3) Future Scope 37
10 References 40
 1-Project Profile
(1.1)Defination:-
Event management is the process by which an event is planned,
prepared, and produced.
As with any other form of management, it encompasses the
assessment, definition, acquisition, allocation, direction, control, and
analysis of time, finances, people, products, services, and other
resources to achieve objectives.
An event manager’s job is to oversee and arrange every aspect of an
event, including researching, planning, organizing, implementing,
controlling, and evaluating an event’s design, activities, and
production.

(1.2) scope:-

Event management encompasses a multitude of types of

events. Although the industry has delineated itself into various
categories, all represent the planning and production of an event
that brings people together at a particular time, in a particular place,
for a particular purpose.

(1.3)Objective:-
 Our site very useful in people.
 In this system is worked properly.
 Our main aim is to manage the Booking.
 User can book the hall any time.
 We had developed a fully computerized system.
 2-System analysis and specification

(2.1)System Analysis:-

 Feasibility Study:-
In this system there are logically three concepts we can cosider as a feasibility
study on eventmanagemant.

1. Technical Feasibilit:-
.Net framework and sqlserver is installed or required for the current system.

 Software requirement:-

 Operating system:Microsoft Windows 8

 Visual Studio 2012
 Tools:SQL server 2012

 Hardware Requirement:-

 C.P.U : Pentium c4 2.40 GHZ

 RAM : 256 of RAM
 Hard Disk : 40GB HDD

2. Economical feasibility:-

The Current System Is Require No Cost of SoftWare Because In Which Environment of

SoftWare.
This System Is Developed Is Very Cheap.
In Event Manager We Need Some Time To Handel Specific Events .

3. Operation feasibility:-

In The Current System Is When Develop. There Are Two Developer Is enough Or
Require To Develop This System.
 No Other Programmers or Developer Are Needed

(2.2)User requirement:-

 Registration/Login:
User can register and can login to the website.
 Feedback:
User can give feedback.
 View Event:
User can see the all event.
 Booking Of Event:
User can book any Event on the basis of date.
 3-System Requirement and specifications
UserSide:-

 Registration/Login:
User can register and can login to the website.
 Feedback:
User can give feedback.
 View Event:
User can see the all event.
 Booking Of Event:
User can book any Event on the basis of date.

AdminSide:-

 Login:
This webpage will display Login form.

 ManageUser:
This web page will show all the detail of user which have being
registered to the site.

 Upload Hall Detail&view:

This webpage will be useful for uploading venue and all the
details of hall. For Ex: Seats, Venue, Price, Status, Type like A.C. or Non. A.C.

 ManageFeedback:
This webpage will show all the feedback given by the user.

 ManageBooking:
This webpage will display all the booking in date wise and
venue selected by the user. If particular venue and date are already booked
then that will not given to other user.

4-SDLC
SDLC Overview
SDLC, Software Development Life Cycle is a process used by
software industry to design, develop and test high quality
softwares. The SDLC aims to produce high quality software that
meets or exceeds customer expectations, reaches completion
within times and cost estimates.

SDLC is a process followed for a software project, within a

software organization. It consists of a detailed plan describing how
to develop, maintain, replace and alter or enhance specific
software. The life cycle defines a methodology for improving the
quality of software and the overall development process.

A typical Software Development life cycle consists of the following

stages:

Stage 1: Planning and Requirement Analysis: Requirement analysis is the

most important and fundamental stage in SDLC. It is performed by the
senior members of the team with inputs from the customer, the sales
department, market surveys and domain experts in the industry. This
information is then used to plan the basic project approach and to
conduct product feasibility study in the economical, operational, and
technical areas.
Planning for the quality assurance requirements and identification of the
risks associated with the project is also done in the planning stage. The
outcome of the technical feasibility study is to define the various
technical approaches that can be followed to implement the project
successfully with minimum risks.

Stage 2: Defining Requirements: Once the requirement analysis is done

the next step is to clearly define and document the product requirements
and get them approved from the customer or the market analysts. This is
done through ‘SRS’ – Software Requirement Specification document
which consists of all the product requirements to be designed and
developed during the project life cycle.

Stage 3: Designing the product architecture: SRS is the reference for

product architects to come out with the best architecture for the product
to be developed. Based on the requirements specified in SRS, usually
more than one design approach for the product architecture is proposed
and documented in a DDS - Design Document Specification. This DDS is
reviewed by all the important stakeholders and based on various
parameters as risk assessment, product robustness, design modularity ,
budget and time constraints , the best design approach is selected for the
product.

A design approach clearly defines all the architectural modules of the

product along with its communication and data flow representation with
the external and third party modules (if any). The internal design of all the
modules of the proposed architecture should be clearly defined with the
minutest of the details in DDS.

Stage 4: Building or Developing the Product: In this stage of SDLC the

actual development starts and the product is built. The programming
code is generated as per DDS during this stage. If the design is performed
in a detailed and organized manner, code generation can be accomplished
without much hassle.

Developers have to follow the coding guidelines defined by their

organization and programming tools like compilers, interpreters,
debuggers etc are used to generate the code. Different high level
programming languages such as C, C++, Pascal, Java, and PHP are used for
coding. The programming language is chosen with respect to the type of
software being developed.

Stage 5: Testing the Product: This stage is usually a subset of all the
stages as in the modern SDLC models, the testing activities are mostly
involved in all the stages of SDLC. However this stage refers to the testing
only stage of the product where products defects are reported, tracked,
fixed and retested, until the product reaches the quality standards
defined in the SRS.

Stage 6: Deployment in the Market and Maintenance: Once the product

is tested and ready to be deployed it is released formally in the
appropriate market. Sometime product deployment happens in stages as
per the organizations’ business strategy. The product may first be
released in a limited segment and tested in the real business environment
(UAT- User acceptance testing).
Then based on the feedback, the product may be released as it is or with
suggested enhancements in the targeting market segment. After the
product is released in the market, its maintenance is done for the existing
customer base.

5-Overview of .net Technology

ASP.NET is a web application framework developed and marketed by
Microsoft to allow programmers to build dynamic web sites, web
applications and web services. It was first released in January 2002 with
version 1.0 of the .NET Framework, and is the successor to Microsoft's
Active Server Pages (ASP) technology. ASP.NET is built on the Common
Language Runtime (CLR), allowing programmers to write ASP.NET code
using any supported .NET language. The ASP.NET SOAP extension
framework allows ASP.NET components to process SOAP messages.

History
After the release of Internet Information Services 4.0 in 1997, Microsoft
began researching possibilities for a new web application model that
would solve common complaints about ASP, especially with regard to
separation of presentation and content and being able to write "clean"
code. [1] Mark Anders, a manager on the IIS team, and Scott Guthrie, who
had joined Microsoft in 1997 after graduating from Duke University, were
tasked with determining what that model would look like. The initial
design was developed over the course of two months by Anders and
Guthrie, and Guthrie coded the initial prototypes during the Christmas
holidays in 1997. [2]

The initial prototype was called "XSP"; Guthrie explained in a 2007

interview that, "People would always ask what the X stood for. At the
time it really didn't stand for anything. XML started with that; XSLT started
with that. Everything cools seemed to start with an X, so that's what we
originally named it."[1] The initial prototype of XSP was done using Java,[3]
but it was soon decided to build the new platform on top of the Common
Language Runtime (CLR), as it offered an object-oriented programming
environment, garbage collection and other features that were seen as
desirable features that Microsoft's Component Object Model platform
didn't support. Guthrie described this decision as a "huge risk", as the
success of their new web development platform would be tied to the
success of the CLR, which, like XSP, was still in the early stages of
development, so much so that the XSP team was the first team at
Microsoft to target the CLR.

With the move to the Common Language Runtime, XSP was re-
implemented in C# (known internally as "Project Cool" but kept secret
from the public), and the name changed to ASP+, as by this point the new
platform was seen as being the successor to Active Server Pages, and the
intention was to provide an easy migration path for ASP developers. [4]

Mark Anders first demonstrated ASP+ at the ASP Connections conference

in Phoenix, Arizona on May 2, 2000. Demonstrations to the wide public
and initial beta release of ASP+ (and the rest of the .NET Framework)
came at the 2000 Professional Developers Conference on July 11, 2000 in
Orlando, Florida. During Bill Gates' keynote presentation, Fujitsu
demonstrated ASP+ being used in conjunction with COBOL, [5] and support
for a variety of other languages was announced, including Microsoft's
new Visual Basic .NET and C# languages, as well as Python and Perl
support by way of interoperability tools created by ActiveState. [6]

Once the ".NET" branding was decided on in the second half of 2000, it
was decided to rename ASP+ to ASP.NET. Mark Anders explained on an
appearance on The MSDN Show that year that, "The .NET initiative is
really about a number of factors, it's about delivering software as a
service, it's about XML and web services and really enhancing the
Internet in terms of what it can do ... we really wanted to bring its name
more in line with the rest of the platform pieces that make up the .NET
framework."[4]
After four years of development, and a series of beta releases in 2000 and
2001, ASP.NET 1.0 was released on January 5, 2002 as part of version 1.0
of the .NET Framework. Even prior to the release, dozens of books had
been written about ASP.NET, [7] and Microsoft promoted it heavily as part
of their platform for web services. Guthrie became the product unit
manager for ASP.NET, and development continued apace, with version 1.1
being released on April 24, 2003 as a part of Windows Server 2003. This
release focused on improving ASP.NET's support for mobile devices.
6- System Design

(6.1)Data Flow Diagram:-

 0-level:-

 1level:-
(6.2)E-R Diagram:-
(6.3) Data Dictionary:-

Table1:-Registration
ColumnName DataType Constrain
u_id Int PrimaryKey
f_name varchar(50) -
l_name varchar(50) -
city varchar(50) -
contactno varchar(50) -
email_id varchar(50) -
address varchar(50) -
birthdate varchar(50) -
username varchar(50) -
password varchar(50) -
utype nchar(10) -
question varchar(50) -
answer varchar(50) -

Table2:-Upload_Hall_Detail
ColumnName DataType Constrain
e_id int PrimaryKey
u_id int ForeignKey(registration)
event_title varchar(50) -
city varchar(50) -
event_description varchar(50) -
venue varchar(50) -
price nchar(10) -
status varchar(50) -
image varchar(50) -
seat nchar(10) -
type varchar(50) -
 Table3:-Feedback
ColumnName DataType Constrain
f_id int PrimaryKey
u_id int ForeignKey(registration)
name varchar(50) -
city varchar(50) -
contactno varchar(50) -
email_id varchar(50) -
comment varchar(50) -

Table4 :-Booking
ColumnName DataType Constrain
b_id int PrimaryKey
e_id int ForeignKey(upload_hall_detail)
name varchar(50) -
address varchar(50) -
contactno varchar(50) -
email_id varchar(50) -
total_seat nchar(10) -
book_date varchar(50) -
regin_date varchar(50) -
event_description varchar(50) -
venue varchar(50) -
event_title varchar(50) -
 7. Screen Shot
Home

Home Page of website which will be shown to user without login into the site.
 Contactus

Contact Page of website which will be shown to user without login into the site.
 About us

Aboutus Page of website which will be shown to user without login into the site.
 Registration

This page allow user to create a new account.

 Login

User can login after registering to the site.

If registration done successfully then any time user can login.
 Gallery

This page will show the Hall detail of different event .

 Services

This page include services provided to the user.

For example:- They can book a hall for wedding purpose, Birthday Party, Engagement Ceremony, Reception,
etc.

ForGot Password
This page will be useful to user in case he/she forgot the password.
 Feedback

User can give feedback or suggestion or any complains.

 Booking

User can book the hall.

 Add Hall

This page will be useful for admin after login from the admin panel.
From this page Admin will Upload & Add New Hall Detail…
 Manage FeedBack

Admin can get the details of Feedback.

 Manage User

This page gives information about the registered user.

 Manage Booking

Admin can have view & delete the Booking.

 Manage Hall

Admin update & delete & Add the view Hall………

8. Testing
 Testing Principal:-
Following are the testing principal, which are used.
All testing should be traceable to user reuirements.
Tests should be being in small and progress toward testing in
the large.
Exhaustive testing is not possible.
To be most effective testing should be consulted by an
independent third party.
Testing Methods:-

 White box testing or glass box texting or structural

testing.
 Black box testing or function testing.
 Interface testing.

White Box Testing:-

This is concerned with the implementation of the program.in
this type of testing different programming structures and data
structure used in the program are tested for proper operation.
This test concentrates on the examination of the coding. The
system software engineers and programmer join test cases and test
data. The system designer creates test cases that have the like hood
of finding out possible errors.

Black Box Testing:-

 This is concerned with the proper execution of the program
specification. In this testing each function or sub program used
in the main program is first identified.

Interface Testing:-
This is concerned with both program spection and program
implementation .this type of testing is particularly important for
object oriented system.
 9. Enhancements
(9.1) Advantages:-

 Maintain whole system through one Admin.

 Routin work is done more effecitively is less time.
 No extra supported staff needed.
 It is also less costly and more effective system.
 The safety of data is increased to provide utilities.

(9.2) Limitation:-

 Replacement facility is not available.

 Online payment is not allowed.
 Only cash on delivery.

(9.3) Future Scope:-

 We want to do following enhancements in projects.

 Some of limitation is removed by using some advance
technology in future.
 We will also add some additional features so that admin
functionality will be less cumbersome.
 Reminder facility will be providing to user and admin.
 Online help can be introduced into the system.
 Online payment facility will also be included into the
system.
9. References
Web site
Http://www.w3school.com
Http://www.google.com
THANK YOU…