Scribd
Upload
268 views6 pages

Project Proposal Event Booking Mangemnt V1.0

The document is a project proposal for an Event Booking System (EBS). The key points are: 1) The EBS will allow general users to easily plan and book events and allow administrators to manage the system. 2) It will aim to improve event planning, collect revenue, provide a user-friendly service, detect fraud, and standardize hard event management tasks. 3) The system will be web-based using Laravel and PHP for development, with a MySQL database hosted on XAMPP server.

Uploaded by

হিট বাংলা
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
268 views6 pages

Project Proposal Event Booking Mangemnt V1.0

The document is a project proposal for an Event Booking System (EBS). The key points are: 1) The EBS will allow general users to easily plan and book events and allow administrators to manage the system. 2) It will aim to improve event planning, collect revenue, provide a user-friendly service, detect fraud, and standardize hard event management tasks. 3) The system will be web-based using Laravel and PHP for development, with a MySQL database hosted on XAMPP server.

Uploaded by

হিট বাংলা
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

1

Project proposal

Event Booking System


Version:01

Course Code: SWE332


Course Title: Software Development project-2
Course Teacher: Asif khan Shakir

1) Pranto Das 171-35-1858


2) Amit Hasan Faysal 163-35-1773

.
2

Table of Contents

Topic Page

1. Introducti on
1.1 Purpose …………………………………………………………………………………………………………….. 3
1.2 Documentati on Conventi ons……………………………………………………………………………… 3
1.3 Gap………………………………………………………………………………………………………...............3
1.4 Product Scope …………………………………………………………………………………………………… 4
1.5 Glossary ……………………………………………………………………………………………………………. 4
1.6 Overview ………………………………………………………………………………………………………….. 4
2. User Classes & Characteristi cs ……………………………………………………………………………….. 5
2.1 General User……………………………………………………………………………………………………... 5
2.2 Admin …………………………………………………………………………………………………….. .........5
3. Design & Implementati on Constraints ……………………………………………………………………. 5
3.1 Operati ng Environment …………………………………………………………………………………….. 5
3.2 Soft ware Language Used ……………………….………………………………………………………... 5
3.3 Development Tools ……………………….…………………………………………………………………… 5
3.4 Database Support ……………………………………………………………………………………………… 5
3

1. Introduction

1.1 Purpose
Proper event booking system management is vital for any successful event. The EBS
is the document that establishes how all the distinct parts and disparate elements of
your event will be work and result in your event being safe and enjoyable. Give a
good service from this management system and any general user organizer can do
their arrangement successfully and easily.

1.2 Documentation Conventions

This SRS is divided up into sections detailing an overall description, the external
interface requirements, system features, and other non-functional requirements. As
this is the final draft, any future modifications of this document would involve
adapting the product to changing systems and uses. We hope to have the product
evolve to changing times as to ensure continued use and success. The Document
and Specification team have prepared the overall information in this document to
the best of their ability. Once read, it is evident that each section is important to
the overall SRS and significant to the project in its own right.

1.3 Gap
All event arrangement booking wouldn’t added in this project but most needed will
be must. The user have to knowledge about the use mobile or pc and have good in
English without these requirement they wouldn’t able to book an event.
4

1.4 Product Scope


The proposed software product is Event management System for general user and
admin control. It will be used to maintain many event planning and booking such
as wedding-ceremony, Birthday-celebration, maintain all kind of providing facility
information, describing all event before booking.
The system is expected to
• Ensure better event planning distribution,
• collection of revenue as business,
• User-friendly service,
• Fraud detection,
• new collection event arrangement and even token,
• Standard solutions for any hard arrangement management to easier ,

1.5 Glossary 
Here there are some clarifications of the terms uses in this document and also some
explanation related to Event Booking Management (EBM) 

Terms Definition: An Event organizer will use this system and will can book, they
can add their some information of their general and logging with proper verification,
the system contain all facilitate information when booking an event. After approve by
admin team member will must communicate with the booked customer.

1.6 Overview 
This Software Requirements Specification (SRS) specifies all the requirements for
EBS. Various techniques such as interviews, brain storming and idea reduction, use
cases and prototyping were used to elicit the requirements and we have identified the
needs, analyzed and refined them. The objective of this document therefore is to
formally describe the system’s high-level requirements including functional
requirements, non-functional requirements and constraints.
5

2. User Classes & Characteristics 

2.1 General User


In the EBS the major and sensitive role is played by the Users or Customers, in EBS
this role is played by the main character. The general user will check all the process
of every event and can book an event easily as their requirement.

2.2 Admin
In the EBS the secondary important role plays by super-admin, He can check the
report of new ordered event information and can Approve or reject new event
proposal. They can add new post on user site also can edit and update the all
functionalities. So, Admin will be the main controller of this project.

3. Design & Implementation Constraints 

3.1 Operating Environment: 


The EBS will be web-based system. Thus, anyone having a browser can hit the
specific link and can get access to it. Thus, it will ensure its best usage and will ease
the means of getting access to the system. Moreover, it will remove the complexities
of running the system in multiple platforms as it will be deployed in a web server. 

3.2 Software Language Used: 


The application will be developed using Laravel 6.0 Framework. The used language
will be PHP and the front end will be developed using Laravel MVC. Besides for eye
soothing user interface experience CSS 4 will also be used. 

3.3 Development Tools: 


For the development purpose Sublime text 3 edition will be used. For handling
different database operations XAMPP MySQL server will be used. 

3.4 Database Support: 


The database that will be used is XAMPP server. Entity framework 4.1 will be used
from the applications end to insert, update and delete the data. 
6

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy