INDEX

Sr. No Topic Title

1 INTRODUCTION
1.1 Abstract
1.2 Existing System And Need
1.3 Scope
1.4 Operating Environment- Hardware and Software
1.5 Detail Description of Technology Used
2 PROPOSED SYSTEM
2.1 Proposed System
2.2 Object of The System
2.3 Feasibility Study
2.4 Advantages of System
3 ANALYSIS & DESIGN
3.1 Object Diagram
3.2 Class Diagram
3.3 Use Case Diagrams
3.4 Module Hierarchy Diagram
3.5 Component Diagram
3.6 Deployment Diagram
3.7 Module Specifications
3.8 ER Diagram
3.9 Sequence Diagram
3.10 Activity Diagram
3.11 Table specifications
3.12 Test Procedures and Implementation

4 User Manual
7 Drawbacks & Limitations
8 Conclusion
9 Bibliography
10 SCREEN SHOT
11 SAMPLE PROGRAM CODE
12 SRS- SOFTWARE REQURIMENT SPECIFICATION)
13 ANNEXURE 5(DESIGN AND SPECIFICATION)
 INTRODUCTION

CHAPTER 1: INTRODUCTION
1.1 Company Profile
1.2 Project Introduction
1.2 Existing System and Need for System
1.3 Scope of Work
1.4 Operating Environment - Hardware and Software
 Chapter 1
INTRODUCTION
This is an Online Event Management system software project that
serves the functionality of an event manager. The system allows only
registered users to login and new users are allowed to resister on the
application. This is a web application developed in Asp.net and Sql
but desktop application of the same application is also available. The
project provides most of the basic functionality required for an event.
It allows the user to select from a list of event types. Once the user
enters an event type eg(Marriage, Dance Show etc), the system then
allows the user to select the date and time of event, place and the
event equipment’s. All this data is logged in the database and the user
is given a receipt number for his booking. This data is then sent to the
administrator (website owner) and they may interact with the client as
per his requirements and his contact data stored in the database.

1.1 ABSTRACT

Online event management system is a best way to keep clients engaged

with the service as they are on the move. As technology is growing rapidly
we are also moving to a technical world where everything we want is to be
online. The main aim of this proposal is to develop an online event
management system. To analyse the current management system used by
fruitions Event Planners in order to identify the system requirements. to
gather requirements for designing an online event management system. To
design or model an online event management system and to test, validate and
implement the designed system. The system will be developed using IIS
server, SQL Server, and Asp.Net using C#.
1.2 Existing System and Need for System
According to the study of the existing system in the that is being followed till
now. presently all the Online Event Management System functionalities are
done manually. This makes the very difficult. The main disadvantage
is time consuming.

LIMITATIONS OF EXISTING SYSTEM

 System will be a very basic project which is intended to provide a base for
further development.
 Other functionalities are supposed to be developed as per custom need on
this framework.

Need for the System

1. Planned approach towards working: - The working in the organization
will be well planned and organized. The data will be stored properly in data
stores, which will help in retrieval of information as well as its storage.

2. Accuracy: - The level of accuracy in the proposed system will be higher.

All operation would be done correctly and it ensures that whatever
information is coming from the center is accurate.

3. Reliability: - The reliability of the proposed system will be high due to the
above stated reasons. The reason for the increased reliability of the system
is that now there would be proper storage of information.

4. No Redundancy: - In the proposed system utmost care would be that no

information is repeated anywhere, in storage or otherwise. This would
assure economic use of storage space and consistency in the data stored.

5. Immediate retrieval of information: - The main objective of proposed

system is to provide for a quick and efficient retrieval of information. Any
type of information would be available whenever the user requires.

6. Immediate storage of information: - In manual system there are many

problems to store the largest amount of information.

7. Easy to Operate: - The system should be easy to operate and should be

such that it can be developed within a short period of time and fit in the
limited budget of the user.
1.3 Scope of Work
 To register and keep the information about all events.
 To build up a system that provides and generates the summary
 Report from the database records in order to get the whole view about the events.
 Summarize the accidental records and responds for the further improvements.
 A web based tool where user can search for additional information of the events.

 The Online Event Management System have now also become like events,
user report can interact with popular events
 I have seen some Online Event Management System are showing effective and
time consuming approach. .
 In all type of offices the computer is a necessary part so visitors browse the
internet to have solution of their problems. So the this system have to keep
eye in the future and have to write in some different way that is not common
to other Online Event Management System.

1.3 Operating Environment - Hardware and Software

MINIMUM HARDWARE REQUIREMENTS

 Monitor
 Keyboard
 Processor > 2.0 GHz
 RAM > 4Gb
 Internet Connection

SOFTWARE REQUIREMENTS

 Windows/Unix/Linux
 MS-SQL
 Visual Studio 2019
 IIS Server
 Front end- Browser with support for C# and ASP
 PROPOSED SYSTEM

CHAPTER 2: PROPOSED SYSTEM

2.1 Proposed System

2.2 Objective Of The System

2.3 Feasibility Study

2.4Advantages of System
2.1 Proposed System

The Website will be built using the MVC Architecture is used Perform easily
Some Functionality
1. Easily update page content and Images
2. Integrate with analytical software to track page answer site performance
3. Post new Content of Patient Test

Website will have the following pages

1. Home
2. Events
3. Feedback
4. Events Category
5. User Sign in
6. User Sign up
7. Admin Login

Backend
1. Events Table
2. Validate Admin during login
3. User Table
4. Events Booking Table
5. Confirmed Events Table
6. All Orders Table
7. Enquiry Table
8. Enquiry Response Table
9. Cancel Order Table
2.2 Objective Of The System

This project intend to automate some of the basic operations of an Online

Event Management System. Scope would be to provide basic functionalities
using a web application so that those manual process can be automated. Main
functionalities involved would be around actors such as user record, events
details, booking & System Admin. Basic operations will be allowed for these
actors along with listing & search capability.

2.3 Feasibility Study

Feasibility study is a process to check possibilities of system development. It is

a method to check various different requirements and availability of financial &
technical resources. Before starting the process various parameters must be
checked like: • Estimated finance is there or not? • The man power to operate
the system is there or not? • The man power is trained or not? There are three
different ways feasibility can be tested

1) Economical Feasibility

2) Technical Feasibility

3) Operational Feasibility.

2.4.1 Economical Feasibility:

In economical feasibility, analysis of the cost of the system is carried

out. The system should be only developed if it is going to give returned the
current manual system user can get the price only by purchasing the
newspapers. In addition if he/she wants to see archives of particular equity then
he has to refer to online vehicle booking. For research reports he has to buy
another vehicles. So Instead of buying no of vehicles customer has to just go
online and with a single click he can get whatever information he wants. So our
project of online share vehicle information the test of economical feasibility.

2.4.2 Technical Feasibility:

It is basically used to see existing computer, hardware and software

etc, weather it is sufficient or additional equipment are required? Minimum
System Requirement is such that it can be affordable by of the user who is
having computer. All the user requires is compatible browser and .net
framework installed so our system is fully technical feasible.
2.4.3 Operational Feasibility:

Once the system is designed there must be trained and expert operator.
If there are not trained they should given training according to the needs of the
system. From the user’s perspective our system fully operational feasible as it
just requires some knowledge of computer. Operators only need add daily prices
of various equities and there are enough validations available so operator does
not require any special technical knowledge. So our system also passes the test
of operational feasibility.

2.4 Advantages of System

 This system will be useful for user to get to know details of events.
 This system will help everyone by sharing notification and updates at a
central place.
CHAPTER 3: ANLYSIS AND DESIGN

3.0 System Requirement

3.1 Object Diagram

3.2 Class Diagram

3.3 Use Case Diagrams

3.4 Module Hierarchy Diagram

3.5 Component Diagram

3.6 Deployment Diagram

3.7Module Specifications

3.8 User Interface Design

3.9 ER Diagram

3.10 Sequence Diagram

3.11 Activity Diagram

3.12 Table specifications 3.13 Test Procedures and Implementation

3.0 System Requirements
Requirements Analysis in systems engineering and software engineering,
encompasses those tasks that go into determining the needs or conditions to
meet for a new or altered product, taking account of the possibly conflicting
requirements of the various stakeholders, such as beneficiaries or users.
Requirements analysis is critical to the success of a development project.
Requirements must be documented, actionable, measurable, testable, related to
identified business needs or opportunities, and defined to a level of detail
sufficient for system design. Requirements can be functional and non-
functional.
Conceptually, requirements analysis includes three types of activity:

to determine what their requirements are. This is sometimes also called

requirements gathering.

unclear, incomplete, ambiguous, or contradictory, and then resolving these

issues.
ng requirements: Requirements might be documented in various
forms, such as natural-language documents, use cases, user stories, or process
specifications.

1. Functional Requirements:

This subsection presents the identified functional requirements for the Online Event
Management System. Initially, general requirements that pertain to the whole system
are given. Where possible, subsequent requirements have been demarcated based on
their relevance to the users of the system that are customer, event and admin.
3.2.1 <Functional Requirement or Feature #1>
3.2.1.1 Introduction
3.2.1.2 Inputs
3.2.1.3 Processing
3.2.1.4 Outputs
3.2.1.5 Error Handling
<Functional Requirement or Feature #2>

Visit Page

3.3.1 Customer use case:

Brief Description: The user accesses the Online Event Management System website,
searches for Event Booking

Initial Step-By-Step Description

Before this use case can be initiated, the Reader has already accessed the Event Management
website.

1. The User accesses the site or page by connecting to the internet.

2. The system User fill up Sign In form.

3. The System User will login with appropriate credentials.

4. The User will create his/her own profile.

5. The User will searches for the desire event report.

Visitor Use case:

Visits the
site

Visitor

Brief Description

The visitor will visits the various profiles.

Initial Step-By-Step Description

1. Visitor logins into the website.

2. Selection of the sample report.

Xref: section 3.3.11

Admin Use case:

Update
System

Brief Description

Admin is responsible for update system on the requirement basis.

Initial Step-By-Step Description

1. The Admin login.

2. The System verifies the login credentials and allows to manage the database.
3. The System admin update the system.
3.4 Classes / Objects
3.4.1 <Class / Object #1>
3.4.2 <Class / Object #2>

2 Non-Functional Requirements:
The Online Event Management System will be on a server with high speed Internet
capability. The physical machine to be used will be determined by the Historical
Society. The software developed here assumes the use of a tool such as Internet
Information Services for connection between the Web pages and the database. The
speed of the customers connection will depend on the hardware used rather than
characteristics of this system. The Admin will run on the editor’s PC and will contain
an MS-SQL database. MS-SQL is already installed on this computer and is a
Windows operating system.

3.5.1 Performance
3.5.2 Reliability
3.5.3 Availability
3.5.4 Security
3.5.5 Maintainability
3.5.6 Portability
3.6 Inverse Requirements State any *useful* inverse requirements.
3.7 Design Constraints Specify design constrains imposed by other standards, company
policies, hardware limitation, etc. that will impact this software project.
3.8 Logical Database Requirements The logical structure of the data to be stored in the
internal Insurance system database is given below.
 Event Booking

Object Diagram : +id:Int Admin login

+ Event_Title: Varchar(20) +username: Varchar(20)

User_Registartion + EventSponcer : Varchar(20) +password: Varchar(20)
+id: Int + Event_Location: Varchar(20) +S_Login();
+name: Varchar(20) + Event_Date:Varchar(20)
+email :Varchar(20) + Image: Varchar(20) Add Event
+contact: Varchar(20) + CustomerName:Varchar(20) +id : int
+address: varchar(20) + CustomerEmail: Varchar(20) + Event_Title: Varchar(20)
+Password: Varchar(20) +CustomerContact:Varchar(20) + EventSponcer : Varchar(20)

+registration() +CustomerCity : varchar(20) + Event_Location: Varchar(20)

+PinCode : varchar(20) + Event_Date:Varchar(20)
+EventBooking() + Image: Varchar(20)
+S_Registration();
User_Login
+Event()
+username: Varchar(20) Enquiry Response

+password: Varchar(20) +id:Int

+S_Login(); +Name: Varchar(20)

+Email: Varchar(20)

+Contact: varchar(20)
Feedback
+Query: varchar(20)
+id:Int
+ Response: varchar(20) All Orders
+Name: Varchar(20) +id:Int
+ Enquiry Response()
+Email: Varchar(20) + Event_Title: Varchar(20)
+Contact: varchar(20) + EventSponcer : Varchar(20)
+Description: varchar(20) Confirm Booking
+ Event_Location: Varchar(20)

+Feedback() +id:Int + Event_Date:Varchar(20)

+ Event_Title: Varchar(20) + Image: Varchar(20)

Enquiry + EventSponcer : Varchar(20) + CustomerName:Varchar(20)

+id:Int + Event_Location: Varchar(20) + CustomerEmail: Varchar(20)

+ Event_Date:Varchar(20) +CustomerContact:Varchar(20)
+Name: Varchar(20)
+ Image: Varchar(20) +CustomerCity : varchar(20)
+Email: Varchar(20)
+ CustomerName:Varchar(20) +Status : varchar(20)
+Contact: varchar(20)
+ CustomerEmail: Varchar(20) + AllOrders()
+Query: varchar(20)
+CustomerContact:Varchar(20)
+ Enquiry ()
+CustomerCity : varchar(20)

+Status : varchar(20)

+ ConfirmBooking()
 C: Online Event Management
Class Diagram

C:Customer A:Admin

Username:= abc Username:= abc

Password = abc123 Password = abc123

E: Event Booking
E: Event
F:Feedback
id:1
Id = 1 EventTitle : Award Function
id:1
Name =ABC PQR Event_Category: Function
Event_Title : Award
Email: [email protected] Events_Location : Pune Function

Contact: 9864726474 EventDate : 30 july 2021 Event_Category: Function

Image : award.png Events_Location : Pune

City : Pune
CustomerName:ABC PQR EventDate : 30 july 2021
Description: Thanku for
Website CustomerEmail: Image : award.png
[email protected]

E: Enquiry CustomerContact:
7365347464CustomerCity :
Id = 1 Pune
Name =ABC PQR
Email: [email protected]
Contact: 9864726474 CB: Confirm Booking
Query: Is there any new id:1
plants ? EventTitle : Award Function
Event_Category: Function
ER: Enquiry_Response
Events_Location : Pune
Id = 1 EventDate : 30 july 2021
Name =ABC PQR Image : award.png
Email: [email protected] CustomerName:ABC PQR

Contact: 9864726474 CustomerEmail: [email protected]

Query: Is there any new CustomerContact: 7365347464

plants ? CustomerCity : Pune

Response : Yes, 20 new Status : Confirmed

plants
 Use Case Diagrams

Visit Website

Registration

Login
Customer

Event

Admin
Feedback

Event Booking

Confirmed Booking

Cancel Booking

All Orders

Report
Module Hierarchy Diagram

Online Event Management

HOME User Admin

CONTACT US Home Home

Maintenance

Events Events Add Event

Informa
User
tionLogin Event Booking Added Event

Use Registration Confirmed Booking Booking Request

Confirmed
Eenquiry
About Us

Cancelled
Eenquiry Response
Admin Sign in

All Orders
Sign out

Message

Sign out
3.5 Component Diagram

HOME Page

User Events

Enquiry

Feedback
Booking Event

Confirmed
Event
3.6 Deployment Diagram

Central System
Device
Web Service
Device
Application

DB XML SOAP

<<HTTP>>

Work Station
Web
Application
<<HTTP>>
Web Browser
HTML
3.8 User Interface Design

3.7.1 Context Level DFD:

Event

Event
Management

Events Events Booking Feedback

3.7.2 First Level DFD:

User
User User
Profile Information

Event
Event INFORMATION

Event
Booking

Feedback Feedback
INFORMATION
3.9 ER Diagram
3.9 Sequence Diagram

User SERVER

1.Registration

2. Login

3. Response

4. Event Booking

5.Feedback
 3.10 Activity Diagram

START

User Admin

REGISTARTIO LOGIN
N

Event

Enquiry Enquiry Booking Confirmed All Orders

View Event
Response Event

END
3.11 Module Specification:

1. Register. 6. Order Request

2. Login 7. Ignore

3. Fetch 8. Accept

4. Search 9. Decline

5. View Profile 10.Feedback

11. Enquiry

1. Register: User needs to register themselves by filling up basic registration details and
by creating valid login credentials..

2. Login: After successful registration, user needs to login using their valid login
credentials.

3. Fetch: Fetch all Information of User filled by user.

4. View Event: View the details of the desired event .

5. Send Request: Send the request for Event.

6. Accept: Admin Accept the Event Booking Request.

7. Feedback: Provided feedback details.

Table Structure
Table Name Column Name Data Type Key
User Id Int Primary
Name varchar(20) Key
Email varchar(20) Unique
Contact varchar(20)
City varchar(20)
Password varchar(20)

Feedback ID int Primary

name varchar(20) Key
email varchar(20)
Contact varchar(20)
Description varchar(20)
Event Id Int Primary
EventName varchar(20) Key
EventType varchar(20)
EventLocation varchar(20)
EventDate varchar(20)
Image varchar(20)

Event Booking Id Int

EventName varchar(20)
EventType varchar(20)
EventLocation varchar(20)
EventDate varchar(20)
Image varchar(20)
CustomerName varchar(20)
 CustomerEmail varchar(20)
CustomerContact varchar(20)
CustomerCity varchar(20)

Confirmed Event Id Int

EventName varchar(20)
EventType varchar(20)
EventLocation varchar(20)
EventDate varchar(20)
Image varchar(20)
CustomerName varchar(20)
CustomerEmail varchar(20)
CustomerContact varchar(20)
CustomerCit
varchar(20)
Status
varchar(20)

Enquiry Id Id
CustomerName varchar(20)
CustomerEmail varchar(20)
CustomerContact varchar(20)
Query varchar(20)

Enquiry Response Id Id
CustomerName varchar(20)
CustomerEmail varchar(20)
CustomerContact varchar(20)
Query varchar(20)
Response varchar(20)
3.13 Test Procedures and Implementation

Test Procedure: The importance of software testing and its implication with respect to software
quality cannot be over emphasized. Software testing is typical element of software quality assurance.
Testing represents the ultimate review of specification, design and coding.

Any engineered product can test in one of two ways : The First approach is called Black Box
Testing and the second one is called as White Box Testing: When computer software is considered,
Black Box Testing alludes to test that is conducted at the software interface. Although they are
designed to uncover errors, Black Box Test are used to demonstrate that software functions are
operational that input properly accepted and output correctly produced; that integrity of external
information is maintained. Black Box Test examines some aspects of system with little regard for
internal structure of software. White Box testing of software is predicted on a close examination of
procedural details. Providing test cases that exercise specific sets of conditions and /or loops test
logical paths through software.

Test Plan: The Test Plan is designed to describe the scope, approach, resources, and schedule of all
testing activities. The Test plan identifies the items to be tested like Authentication, the features to be
tested like (for Authentication module) whether user is having privilege to login to the system or not,
the types of testing to be performed like Unit Testing, Security Testing, User Interface Testing,
Performance Testing, Regression Testing, the resources required to perform testing.

Unit/Module Testing: Testing conducted to verify the implementation of the design for one
software element (e.g., unit, module) is called unit testing. The purpose of unit testing is to ensure
that the program logic is complete and correct and ensuring that the component works as designed.
In each module will be go through Unit testing after the completion of the module. The bugs in
module testing will be reported in Test Log document and will be reported to the developers. After
fixing the bug successfully, one more iteration of module testing (Regression Testing) is done. This
process is repeated till all critical test cases pass.

Integration Testing: Testing conducted in which software elements, hardware elements, or both are
combined and tested until the entire system has been integrated. The purpose of integration testing is
to ensure that design objectives are met and ensures that the software, as a complete entity, complies
with operational requirements. This type of testing will be done after all module test cases are passed
through module testing, security testing, performance testing, user interface testing and regression
testing. User Interface Testing: Testing done to ensure that the application operates efficiently and
effectively on each client machine

Security Testing: In Authentication component, user needs to enter his login id and password. If the
user name and password is valid then user is allowed to log in. As per the role of user will get the
access over the different options.
Regression Testing: Testing done to ensure that, the changes to the application has not adversely
affected previously tested functionality. In Effort tracking system, testing will take care of the test
cases passed during the first module testing will not be affected in the subsequent rounds of module
testing.

Acceptance Testing: This testing is conducted to determine whether the product satisfies the
acceptance criteria of the user. It enables the customer to determine whether or not to accept the
system. Acceptance testing ensures that customer requirements are met.

Beta Testing: Testing, done by the customer, using a pre-release version of the product to verify and
validate that the system meets business functional requirements. The purpose of beta testing is to
detect application faults, failures, and defects in application on regular worked basis. The Consistent
performance of whole product will be tested for period of time to ensure that the product is ready in
release stage.
Tools: Testing is performed manually without using any automated tools.
 4.1 User Manual

ation is start with sign up or login.

up will be confirm from admin then new user applicable to login.

will create his own profile.

will view user’s event booking

e user will view the events.

5. Drawbacks & Limitation
 System will be a very basic project which is intended to provide a base for
further development.
 Other functionalities are supposed to be developed as per custom need on
this framework.

10. Conclusion
A Online Event Management System conclusion is an
opportunity to inspire customer from site and make them see how
great your brain is. You should leave offline cake rather you get
details about patient‘s sample and get best trusted sample report.

Unfortunately, many of you are writing garbage, throwaway

conclusions, and you don't even realize it.

Never fear busying online! I'm on a one-woman mission to help

you turn this ship around. Today, you're going to learn smart work.
 11. Bibliography

Web Sites:
www.google.com
www.youtube.com
www.youtube.com
10. SCREEN SHOT

1. Home Cake
2. Sign in
3.Sign up
4.Admin Login
5. Booking Event
6.Admin Published Event
7.Publishing Event
9.Confirmed Booking
11.Event On User Profile
12.Event Booking Request
12. SAMPLE PROGRAM CODE
ASP Code:
1. HomeMaster.master
<%@ Master Language="C#" AutoEventWireup="true"
CodeBehind="HomeMaster.Master.cs"
Inherits="Online_Event_Management_System.AdminMaster" %>

<!DOCTYPE html>

<html>
<head runat="server">
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-
scale=1, shrink-to-fit=no">
<meta name="description" content="">
<meta name="author" content="">
<link rel="icon"
href="/docs/4.0/assets/img/favicons/favicon.ico">

<title>Online Event Management System</title>

<link rel="canonical"
href="https://getbootstrap.com/docs/4.0/examples/pricing/">

<!-- Bootstrap core CSS -->

<link href="bootstrap-4.0.0/dist/css/bootstrap.min.css"
rel="stylesheet">

<link href="css/blog.css" rel="stylesheet" />

<asp:ContentPlaceHolder ID="head" runat="server">

</asp:ContentPlaceHolder>
</head>
<body>
<form id="form1" runat="server">
<div class="d-flex flex-column flex-md-row align-items-center p-
3 px-md-4 border-bottom box-shadow" style="background-
color:#ccccff;">
<h5 class="my-0 mr-md-auto font-weight-bold text-dark">Online
Event Management System</h5>
<nav class="my-2 my-md-0 mr-md-3">
<asp:Button ID="Button2" class="p-2 text-dark btn btn-
warning btn-outline-danger font-weight-bold" runat="server"
Text="Home" OnClick="Button2_Click" />
 <asp:Button ID="Button1" class="p-2 text-dark btn btn-
warning btn-outline-danger font-weight-bold" runat="server"
Text="Events" OnClick="Button1_Click" />
<asp:Button ID="Button3" class="p-2 text-dark btn btn-
warning btn-outline-danger font-weight-bold" runat="server"
Text="Contact_Us" OnClick="Button3_Click" />
<asp:DropDownList ID="DropDownList1" AutoPostBack="true"
class="p-2 text-dark btn btn-warning btn-outline-warning font-
weight-bold" runat="server"
OnSelectedIndexChanged="DropDownList1_SelectedIndexChanged">
<asp:ListItem Selected="True"
Value="EventCategory">Event Category</asp:ListItem>
<asp:ListItem Value="EducationalEvent">Educational
Event</asp:ListItem>
<asp:ListItem Value="SocialEvent">Social
Event</asp:ListItem>
<asp:ListItem Value="SportsEvent">Sports
Event</asp:ListItem>
</asp:DropDownList>
<asp:Button ID="userLogin" class="p-2 text-dark btn btn-
warning btn-outline-warning font-weight-bold" runat="server"
Text="User Login" OnClick="userLogin_Click" />
<asp:Button ID="userRegistration" class="p-2 text-dark btn
btn-warning btn-outline-warning font-weight-bold" runat="server"
Text="User Registration" OnClick="userRegistration_Click" />
</nav>
<asp:Button ID="Button6" class="btn btn-outline-primary
font-weight-bold" runat="server" Text="Admin Login"
OnClick="Button6_Click" />
</div>

<asp:ContentPlaceHolder ID="ContentPlaceHolder1"
runat="server">
</asp:ContentPlaceHolder>

</form>

<script src="https://code.jquery.com/jquery-3.2.1.slim.min.js"
integrity="sha384-
KJ3o2DKtIkvYIK3UENzmM7KCkRr/rE9/Qpg6aAZGJwFDMVNA/GpGFF93hXpG5KkN"
crossorigin="anonymous"></script>
<script>window.jQuery || document.write('<script src="bootstrap-
4.0.0/assets/js/vendor/jquery-slim.min.js"><\/script>')</script>
<script src="bootstrap-
4.0.0/assets/js/vendor/popper.min.js"></script>
<script src="bootstrap-4.0.0/dist/js/bootstrap.min.js"></script>
<script src="bootstrap-
4.0.0/assets/js/vendor/holder.min.js"></script>
 <script>
Holder.addTheme('thumb', {
bg: '#55595c',
fg: '#eceeef',
text: 'Thumbnail'
});
</script>
</body>
</html>

2.UserMaste
<%@ Master Language="C#" AutoEventWireup="true" CodeBehind="UserMaster.master.cs"
Inherits="Online_Event_Management_System.UserMaster" %>

<!DOCTYPE html>

<html>
<head runat="server">
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-
fit=no">
<meta name="description" content="">
<meta name="author" content="">
<link rel="icon" href="/docs/4.0/assets/img/favicons/favicon.ico">

<title>UserProfile</title>

<link rel="canonical" href="https://getbootstrap.com/docs/4.0/examples/pricing/">

<!-- Bootstrap core CSS -->

<link href="bootstrap-4.0.0/dist/css/bootstrap.min.css" rel="stylesheet">

<link href="css/blog.css" rel="stylesheet" />

<asp:ContentPlaceHolder ID="head" runat="server">
</asp:ContentPlaceHolder>
</head>
<body>
<form id="form1" runat="server">
<div class="d-flex flex-column flex-md-row align-items-center p-3 px-md-4 border-
bottom box-shadow" style="background-color:#ccccff;">
<h5 class="my-0 mr-md-auto font-weight-bold text-dark">User Profile</h5>
<nav class="my-2 my-md-0 mr-md-3">
<asp:Button ID="Button2" class="p-2 text-dark btn btn-warning btn-outline-
danger font-weight-bold" runat="server" Text="Home" OnClick="Button2_Click" />
<asp:Button ID="Button1" class="p-2 text-dark btn btn-warning btn-outline-
danger font-weight-bold" runat="server" Text="Events" OnClick="Button1_Click" />

<asp:DropDownList ID="EventCategory" AutoPostBack="true" class="p-2 text-

dark btn btn-warning btn-outline-warning font-weight-bold" runat="server" >
<asp:ListItem Selected="True"
Value="EventCategory">EventCategory</asp:ListItem>
<asp:ListItem Value="EducationalEvent">Educational Event</asp:ListItem>
<asp:ListItem Value="SocialEvent">Social Event</asp:ListItem>
<asp:ListItem Value="SportsEvent">Sports Event</asp:ListItem>
</asp:DropDownList>
<asp:Button ID="BookingEvents" class="p-2 text-dark btn btn-warning btn-
outline-warning font-weight-bold" runat="server" Text="Booking Events"
OnClick="BookingEvents_Click" />

</nav>
 <asp:Button ID="Signout" class="btn btn-outline-primary font-weight-bold"
runat="server" Text="Signout" OnClick="Signout_Click" />
</div>

<asp:ContentPlaceHolder ID="ContentPlaceHolder1" runat="server">

</asp:ContentPlaceHolder>

</form>
</body>
</html>

3.AdminAddEvent.aspx
<%@ Page Title="" Language="C#"
MasterPageFile="~/AdminMaster.Master" AutoEventWireup="true"
CodeBehind="AdminAddEvent.aspx.cs"
Inherits="Online_Event_Management_System.AdminAddEvent" %>
<asp:Content ID="Content1" ContentPlaceHolderID="head"
runat="server">
</asp:Content>
<asp:Content ID="Content2"
ContentPlaceHolderID="ContentPlaceHolder1" runat="server">

<div class="jumbotron bg-white">

<div class="container">

<div class="row justify-content-center">

<div class="card text-center col-8">

<div class="card-body">
<h3 class="text-center">Publish Event</h3>

<div class="form-group">
<asp:Label ID="message" class="font-weight-bold text-danger"
runat="server" Text=""></asp:Label>
</div>

<div class="form-group">
<label class="font-weight-bold">Event Name</label>
<asp:TextBox ID="eventName" class="form-control"
placeholder="Event Name" runat="server"></asp:TextBox>
</div>

<div class="form-group ">

<label class="font-weight-bold">Event Category</label>
<br />
<asp:DropDownList ID="EventCategory" AutoPostBack="true"
class="btn btn-outline-danger font-weight-bold" runat="server" >
<asp:ListItem Selected="True"
Value="EventCategory">Event Category</asp:ListItem>
 <asp:ListItem Value="EducationalEvent">Educational
Event</asp:ListItem>
<asp:ListItem Value="SocialEvent">Social
Event</asp:ListItem>
<asp:ListItem Value="SportsEvent">Sports
Event</asp:ListItem>
</asp:DropDownList>
</div>

<div class="form-group">
<label class="font-weight-bold">Event Chief Guest</label>
<asp:TextBox ID="EventChiefGuest" class="form-control"
placeholder="Event Chief Guest" runat="server"></asp:TextBox>
</div>

<div class="form-group">
<label class="font-weight-bold">Event Sponcer</label>
<asp:TextBox ID="EventSponcer" class="form-control"
placeholder="Event Sponcer" runat="server"></asp:TextBox>
</div>

<div class="form-group">
<label class="font-weight-bold">Event Date</label>
<asp:TextBox ID="EventDate" class="form-control"
placeholder="Contact" runat="server"></asp:TextBox>
<asp:Button ID="Date" CssClass="btn btn-outline-danger mt-
1" runat="server" Text="Date" OnClick="Date_Click1" />
<asp:Calendar ID="Calendar1" runat="server"
Visible="False"
OnSelectionChanged="Calendar1_SelectionChanged"></asp:Calendar>
</div>

<div class="form-group">
<label class="font-weight-bold">Event Location</label>
<asp:TextBox ID="EventLocation" class="form-control"
placeholder="Event Location" runat="server"></asp:TextBox>
</div>

<div class="form-group text-center">

<label class="font-weight-bold">Event Photo</label>
<asp:FileUpload ID="EventPhoto" class="form-control-file
align-content-center" runat="server" />
</div>

<div class="card-footer text-muted bg-white">

<asp:Button ID="AddEvent" class="btn btn-danger font-
weight-bold w-50" runat="server" Text="Add Event"
OnClick="AddEvent_Click" />
</div>
 </div>

</div>
</div>
</div>
</div>
</asp:Content>

2.C# Code
1.HomeMasterr.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

namespace Online_Event_Management_System
{
public partial class AdminMaster : System.Web.UI.MasterPage
{
protected void Page_Load(object sender, EventArgs e)
{

protected void userLogin_Click(object sender, EventArgs e)

{
Response.Redirect("UserLogin.aspx");
}

protected void userRegistration_Click(object sender,

EventArgs e)
{
Response.Redirect("UserRegistration.aspx");
}

protected void Button6_Click(object sender, EventArgs e)

{
Response.Redirect("AdminLogin.aspx");
}

protected void Button1_Click(object sender, EventArgs e)

{
Response.Redirect("HomeEvents.aspx");
}
 protected void DropDownList1_SelectedIndexChanged(object
sender, EventArgs e)
{
Response.Redirect("HomeEvents.aspx");
}

protected void Button3_Click(object sender, EventArgs e)

{
Response.Redirect("ContactUs.aspx");
}

protected void Button2_Click(object sender, EventArgs e)

{
Response.Redirect("HomePage.aspx");
}
}
}

2.AddEvent.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data;
using System.Data.SqlClient;

namespace Online_Event_Management_System
{
public partial class AdminAddEvent : System.Web.UI.Page
{
String path;
SqlConnection con = new SqlConnection(@"Data
Source=(LocalDB)\MSSQLLocalDB;AttachDbFilename=C:\Users\91702\source
\repos\Online Event Management System\Online Event Management
System\App_Data\EventManagementDB.mdf;Integrated Security=True");
protected void Page_Load(object sender, EventArgs e)
{

protected void AddEvent_Click(object sender, EventArgs e)

{
EventPhoto.SaveAs(Request.PhysicalApplicationPath +
"/image/" + EventPhoto.FileName.ToString());
path = "image/" + EventPhoto.FileName.ToString();
 con.Open();
SqlCommand cmd = con.CreateCommand();
cmd.CommandType = CommandType.Text;
cmd.CommandText = "insert into Event values('" +
eventName.Text + "','" + EventCategory.SelectedValue.ToString() +
"','" + EventChiefGuest.Text + "','" + EventSponcer.Text + "','" +
EventDate.Text + "','" + EventLocation.Text + "','"+ path.ToString()
+"')";

int i = cmd.ExecuteNonQuery();
if (i > 0)
{
Response.Write("<script> alert('Event Has Benn Added
Successfully...'); </script>");
}
else
{
message.Text = "something went wrong...!";
}
con.Close();

eventName.Text = "";
EventChiefGuest.Text = "";
EventSponcer.Text="";
EventDate.Text = "";
EventLocation.Text = "";

protected void Date_Click1(object sender, EventArgs e)

{
Calendar1.Visible = true;
}

protected void Calendar1_SelectionChanged(object sender,

EventArgs e)
{
EventDate.Text =
Calendar1.SelectedDate.ToLongDateString();
Calendar1.Visible = false;
}
}
}

3.ConfirmedBooking.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data;
using System.Data.SqlClient;

namespace Online_Event_Management_System
{
public partial class AdminConfirmedBooking : System.Web.UI.Page
{
SqlConnection con = new SqlConnection(@"Data
Source=(LocalDB)\MSSQLLocalDB;AttachDbFilename=C:\Users\91702\source
\repos\Online Event Management System\Online Event Management
System\App_Data\EventManagementDB.mdf;Integrated Security=True");
protected void Page_Load(object sender, EventArgs e)
{

con.Open();

SqlCommand cmd = con.CreateCommand();

cmd.CommandType = CommandType.Text;
cmd.CommandText = "select * from ConfirmedBooking";
cmd.ExecuteNonQuery();
DataTable dt = new DataTable();
SqlDataAdapter da = new SqlDataAdapter(cmd);
da.Fill(dt);
DataList1.DataSource = dt;
DataList1.DataBind();
con.Close();
}
}

}
SRS- SOFTWARE REQURIMENT SPECIFICATION

Software Requirements Specification

“Online Event Management”

<1.0>

<25th July, 2022 >

Your Name
Lead Software Engineer

Submitted in Partial fulfillment of Project

Revision History

Date Description Author Comments

<date> <Version 1> < Your Name> <First Revision>

Document Approval

The following Software Requirements Specification has been accepted and approved by the following:

Signature Printed Name Title Date

< Your Name > Lead Software Eng.

Table of Contents
REVISION HISTORY....................................................................................................................2
DOCUMENT APPROVAL............................................................................................................2
1.INTRODUCTION ............................................................................................................4
1.1PURPOSE..................................................................................................................................4
1.2 SCOPE .....................................................................................................................................5
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS.....................................................5
1.4 REFERENCES.........................................................................................................................6
1.5 OVERVIEW.............................................................................................................................6

2. GENERAL DESCRIPTION.............................................................................................7

2.1 PRODUCT PERSPECTIVE .........................................................................................8

2.2 PRODUCT FUNCTIONS ............................................................................................8

2.3 USER CHARACTERISTICS ....................................................................................... 8

2.4 GENERAL
CONSTRAINTS.................................................................................................9

2.5 ASSUMPTIONS AND

DEPENDENCIES............................................................................9

2.6 SYSTEM
ENVIRONMENT..................................................................................................9

3. SPECIFIC REQUIREMENTS .....................................................................................10

3.1SYSTEM INTERFACE………………………………………………………...………...11

3.1.1ANDROID……………...................................................................................................11
3.1.2HIGHLIGHTOFANDROID………………………..……..............................................11

3.1.3 INTRODUCTION OF ANDROID…………………………………………………..12

3.1.4 APPLICATION FUNDAMENTALS………..……...…………………………...…..12

3.1.5 LOCATION SENSING TECHNOLOGY………………………….........................13

3.2 EXTERNAL INTERFACE REQUIREMENTS ..................................................14

3.2.1 HARDWARE INTERFACES..................................................................................14

3.2.2 SOFTWARE INTERFACES ...................................................................................14

3.2.3 COMMUNICATIONS INTERFACES ................................................................14 3.3
FUNCTIONAL REQUIREMENTS ..........................................................................14
3.3 USE CASES ................................................................................................................15
3.3.1 USER USE CASE ...................................................................................................15
3.3.2 ACCESS INFORMAION USE CASE ...................................................................15
3.3.3 ADD USE CASE ....................................................................................................15
3.3.4 ADMIN USE CASE ...............................................................................................15
3.3.5 FEEDBACK USE CASE ……………………….………………..........................15
3.4 NON FUNCTIONAL REQUIREMENTS .................................................................16
3.5 LOGICAL STRUCTURE............................................................................................17
3.6 DATABASE OF APPLICATION……………...........................................................20
 1. INTRODUCTION
This is an Online event management system software project that serves
the functionality of an event manager. The system allows only registered
users to login and new users are allowed to resister on the application. This
is a web application developed in Asp.net and Sql but desktop application
of the same application is also available. The project provides most of the
basic functionality required for an event. It allows the user to select from a
list of event types. Once the user enters an event type eg(Marriage, Dance
Show etc), the system then allows the user to select the date and time of
event, place and the event equipment’s. All this data is logged in the
database and the user is given a receipt number for his booking. This data
is then sent to the administrator (website owner) and they may interact
with the client as per his requirements and his contact data stored in the
database.

1.1 Purpose

This research is done to achieve four objectives:

i) To identify people’s requirements during finding the Event.

ii) To develop a web based application for best cake selection on site

iii) Reduce the human energy and unnecessary cost to search event.

iv)To give online help to search the cake information.

1.2 Scope
This project deals with the various functioning in Online Event System process.
The main idea is to implement a proper process to system .In our
existing system contains a many operations registration, search event, booking
event, report, customer details, performance of the admin etc.
1.3 Definitions, Acronyms, and Abbreviations
User Someone who interacts with the

mobile phone and computer system

Admin/Administrator System administrator who is given

specific permission for managing and

controlling the system

Web-portal A web web application which present

special facilities for admin

Website An web web application on mobile

phone or computer which helps user

to find new compatible web

applications with mobile phone

platform and download them from

Internet

DESC Description

RAT Rational
1.4 References
The document in this file is an annotated outline for specifying software requirements

adapted from the IEEE Guide to Software Requirements Specifications (Std 830-1993).

1.4 Overview
The next chapter, the Overall Description section, of this document gives an overview of

the functionality of the product. It describes the informal requirements and is used to

establish a context for the technical requirements specification in the next chapter. The third

chapter, Requirements Specification section, of this document is written primarily for the

developers and describes in technical terms the details of the functionality of the product.

Both sections of the document describe the same software product in it entirety, but are

intended for different audiences and thus use different language

Following area of operations are being covered under the scope of this project.

A. Admin B. Customer

2.GENERAL DESCRIPTION

2.1 SYSTEM ANALYSIS : The system analysis section may contain two types, they are

existing system and proposed system.

2.1.1 EXISTING SYSTEM:

According to the study of the existing system in the that is being followed till now. Presently

all the Online Cake Shop functionalities are done manually. This makes the very difficult.

The main disadvantage is time consuming.

2.1.2 DRAWBACK OF EXISTING SYSTEM :

a. Large amount of data cannot be stored.
b. Advanced features cannot be added.
c. Less number of modules are applied
2.1.3 PROPOSED SYSTEM

The Website will be built using the MVC Architecture is used Perform easily
Some Functionality
4. Easily update page content and Images
5. Integrate with analytical software to track page answer site performance
6. Post new Content of Patient Test

Website will have the following pages

8. Home
9. Events
10. Feedback
11. Events Category
12. User Sign in
13. User Sign up
14. Admin Login

Backend
12. Events Table
13. Validate Admin during login
14. User Table
15. Events Booking Table
16. Confirmed Events Table
17. All Orders Table
18. Enquiry Table
19. Enquiry Response Table
20. Cancel Order Table
21.

2.1.4 ADVANTAGES OF THE PROPOSED SYSTEM :

 This system will be useful for admin to get to know details of event and user.
 This system will help everyone by sharing notification and updates at a
central place.
3.1.2 SPECIFIC REQUIREMENTS
Requirements Analysis in systems engineering and software engineering,
encompasses those tasks that go into determining the needs or conditions to
meet for a new or altered product, taking account of the possibly conflicting
requirements of the various stakeholders, such as beneficiaries or users.
Requirements analysis is critical to the success of a development project.
Requirements must be documented, actionable, measurable, testable, related to
identified business needs or opportunities, and defined to a level of detail
sufficient for system design. Requirements can be functional and non-
functional.
Conceptually, requirements analysis includes three types of activity:

to determine what their requirements are. This is sometimes also called

requirements gathering.

unclear, incomplete, ambiguous, or contradictory, and then resolving these

issues.
ng requirements: Requirements might be documented in various
forms, such as natural-language documents, use cases, user stories, or process
specifications.

3.1.3 Software Interfaces:

The Online Event Management System will interface with a
Database Management System (DBMS) that stores the information necessary
for the Online Cake Shop System to operate. The DBMS must be able to
provide, on request and with low latency, data concerning the doctor, Admin
and profiles and available dietary requirements. The DBMS must store all data
such that it can be used for accounting, as well as accountability
3.2 Functional Requirements:

This subsection presents the identified functional requirements for the Online Event
Management System. Initially, general requirements that pertain to the whole system
are given. Where possible, subsequent requirements have been demarcated based on
their relevance to the users of the system that are customer, event and admin.
3.2.1 <Functional Requirement or Feature #1>
3.2.1.1 Introduction
3.2.1.2 Inputs
3.2.1.3 Processing
3.2.1.4 Outputs
3.2.1.5 Error Handling

3.2.2 <Functional Requirement or Feature #2>

Visit Page

3.3.1 Customer use case:

Brief Description: The user accesses the Online Event Management System website,
searches for Event Booking

Initial Step-By-Step Description

Before this use case can be initiated, the Reader has already accessed the Event Management
website.

1. The User accesses the site or page by connecting to the internet.

2. The system User fill up Sign In form.

3. The System User will login with appropriate credentials.

4. The User will create his/her own profile.

5. The User will searches for the desire event report.

3.3.4 Visitor Use case:

Visits the
site

Visistor

Brief Description

The visitor will visits the various profiles.

Initial Step-By-Step Description

1. Visitor logins into the website.

2. Selection of the sample report.

Xref: section 3.3.11

3.3.5 Admin Use case:

Update
System

Brief Description

Admin is responsible for update system on the requirement basis.

Initial Step-By-Step Description

1. The Admin login.
2. The System verifies the login credentials and allows to manage the database.
3. The System admin update the system.
3.4 Classes / Objects
3.4.1 <Class / Object #1>
3.4.2 <Class / Object #2>

3.5 Non-Functional Requirements:

The Online Event Management System will be on a server with high speed Internet
capability. The physical machine to be used will be determined by the Historical
Society. The software developed here assumes the use of a tool such as Internet
Information Services for connection between the Web pages and the database. The
speed of the customers connection will depend on the hardware used rather than
characteristics of this system. The Admin will run on the editor’s PC and will contain
an MS-SQL database. MS-SQL is already installed on this computer and is a
Windows operating system.

3.5.1 Performance
3.5.2 Reliability
3.5.3 Availability
3.5.4 Security
3.5.5 Maintainability
3.5.6 Portability
3.6 Inverse Requirements State any *useful* inverse requirements.
3.7 Design Constraints Specify design constrains imposed by other standards, company
policies, hardware limitation, etc. that will impact this software project.
3.8 Logical Database Requirements The logical structure of the data to be stored in the
internal Insurance system database is given below.