A Project Report

On

ONLINE DJ MANAGEMENT SYSTEM

Submitted in partial fulfilment of the requirements for the award of degree of

Bachelor of Business Administration (Computer Application)

Submitted By:

Prathmesh Jadhav(A-53)
&
Aarti Tarde(A-14)

Academic Year: 2021– 2022

Submitted to:

Savitribai Phule Pune University

Shree Chanakya Education Society

Indira College of Commerce and Science, Pune

Vice Principal & (H.O.D) Guided By

Prof. Shivendu Bhushan Prof. Shubangi chavan
 Index
Sr. No Particulars Page No.
1 Abstract 4

2 Introduction 4
2.1 Motivation 4
2.2 Problem statement 4
2.3 Purpose/Objectives/goals 5
2.4 Literature survey 5-6
2.5 Project Scope and Limitations 6
3 System Analysis 6
3.1 Existing System 6
3.2 Scope and Limitation of existing system 7
3.3 Project perspective, features, stakeholders 7
3.4 Requirement Analysis 7-8
3.4.1 Functional Analysis 8
3.4.2 Performance Analysis 8-9
3.4.3 Security Analysis 9
4 System Design 10
4.1 Design constraints 10
4.2 System Model 11
4.2.1 Data Flow Diagram 11-20
4.2.2 Data Model 21-28
4.3 User Interface 29-38
5 Implementation Details 39
5.1 Software and hardware specifications 39
6 Output and Report Testing 40
6.1 Test Plan 40
6.2 Black Box Testing/Data validations Test 40
cases
6.3 White Box Testing/functional validations 41
Test cases and results
7 Conclusion and Recommendation 41-42
8 Future Scope 42-43
9 Bibliography and References 43
 Acknowledgement
We would like to express our sincere and heartfelt gratitude to our institution” Indira
College of Commerce and Science” which provided us with excellent opportunity to achieve
our most cherished goal in life to become Bachelor degree in BBA-CA.

We are extremely grateful to our respected Vice Principal and HOD Prof, Shivendu
Bhushan for providing excellent academic environment which has made this endeavour
possible.

We take this opportunity to express our deep sense of gratitude to our guide Prof. Divya
Chitre for their resplendent idea and constant encouragement in making this project
unmitigated success. Their thoughtfulness and understanding was vast and thoroughly helpful
in successful completion of project. Our sincere thanks to all our faculties and non-teaching
staff for their at most co-operation.

Finally we proudly thank our parents and friends for their constant support and priceless
guidance in throughout this endeavour.

Prathmesh Jadhav & Aarti Tarde

1) Abstract:
In this paper, the objective of this application is to develop a system that
effectively manages all the data related to the various DJ events that take place in a function. The
purpose is to maintain a centralized database of all DJ event related information. The goal is to
support various functions and processes necessary to manage the data efficiently. This will end
the practice of calling various DJ agencies and explaining the various requirement, here the user
can view the website and check out the information about the ODJMS (Online DJ Management
System) services and they can also enquire and book the DJ. The admin manage the types of
event, add or remove the event. The admin can view the number of bookings approved or
rejected.

2) Introduction:

2.1) Motivation:
First of all it’s all free; user can register totally free and can avail
all of the web portal features for FREE. This Web Portal is available for every type of plants.

2.2) Problem statement:

Problem statement is one of the basic and important phases
of project phase. When the basic problem is determined, it is documented and the symptomatic
problem is analyzed, then the current list of basic problem is completed. A system is simply a set
of components that interact to accomplish some purpose. A problem statement is a concise
description of an issue to be addressed or a condition to be improved upon. It identifies the gap
between the current (problem) state and desired (goal)state of a process or product. Focusing on
the facts, the problem statement should bedesigned to address the Five Ws. The first condition of
solving a problem is understanding the problem, which can be done by way of a problem
statement. [1] Problem statements are widely used by businesses and organizations to execute
process improvement projects. A simple and well-defined problem statement will be used by the
project team to understand the problem and work toward developing a solution. It will also
provide management with specific insights into the problem so that they can make appropriate
project approving decisions. As such, it is crucial for the problem statement to be clear and
unambiguous.

2.3) Purpose/Objectives/goals:
✓ Reduced entry work
 ✓ Easy retrieval of information
✓ Reduced errors due to human intervention
✓ User friendly screens to enter the data
✓ Portable and flexible for further enhancement
✓ Web enabled.
✓ Fast finding of information request

2.4) Literature survey:

Before selecting from this large array of technologies, the following aspects, which
are characteristic to windows based application like this one, have been kept in mind:

1)Data validation

2)Performance

3)Reliability
4)Scalability

5)Portability

6)Performance

7)Time Constraint

8)Cost Constraint

2.5) Project Scope and Limitations:

The objective of this application is to develop a system that effectively manages all the data related
to the various DJ events that take place in a function. The purpose is to maintain a centralized
database of all DJ event related information. The goal is to support various functions and processes
necessary to manage the data efficiently.
3) System Analysis:
3.1) Existing System :
This existing system is not providing secure registration and
profile management of all the users properly. This system is not providing on-line Help. This
system doesn’t provide tracking of users activities and their progress. This manual system gives
us very less security for saving data and some data may be lost due to mismanagement. This
system is not providing event management through internet. This system is not providing proper
events information. The system is giving manual information through the event management
executerp

3.2) Scope and Limitation of existing system :

▪ Very Complicated.

▪ Hard to browse through.

▪ Mocused more on the design rather than the usability.

▪ Users with low PC knowledge cannot easily use the websites.

3.3) Project perspective, features, stakeholders :

• This System has many unique features of its own. The main feature is that it is very
user friendly and not complicated like many other systems that are used today.
• This feature becomes a selling point of this system as many other systems tend to feel
complicated to use and ordering plants isn’t supposed to be complicated.
• The Stakeholders of this project are the Users of the system and the administrators who
control and manage the system.
• The buyer registers themselves with their details and can login with the same
credentials. He is then redirected to the homepage of the system. From there he can
browse the items that are listed, check out the prices and choose them and add to cart
to purchase them later.
• The buyer is then redirected to the checkout page where he is to enter his personal
details into the given fields and place an order. The data he enters is saved into the
database and can be used later too.
• The admin is another stakeholder of the system. He can access the admin page and edit
or delete the products from there. He has a separate admin registration portal where he
can enter his email and name and become an admin.
• He can then Login using his credentials and modify, view and even delete the products
he wishes to. The system is even easy for the admin to use as it has been designed to
be simple yet effective.
 3.4) Requirement Analysis :
• The information domain of the problem must be represented and understood.

• The functions that the software is to perform must be defined.

• The behavior of the software as a consequence of external events must be defined.

• The models that depict information, function and behavior must be partitioned in a

hierarchical or layered fashion.

• The analysis process must move from essential information to implementation detail.

3.4.1) functional Analysis :

• Functional analysis is the next step in the Systems Engineering
process after setting goal and requirements.
• Functional analysis divides a system into smaller parts, called
functional elements, which describe what we want each part to do.
• We do not include the how of the design or solution yet.
• In this system, the goals were to create a simple system that would
be easy for anyone to use and work with.
• With that in mind, we created a system with a simple user interface
with elements that are easy to use and understand.
• Every button and every textbox has been designed and coded in
such a way that every element is easily visible and accessible to the
user, which makes ordering food a very simple task like it should
be.
• This in-turn has enabled us to create a system that is only functional
instead of being overdesigned, which is sometimes a hassle to use
and maintain.
• Thus, we have achieved every basic function the requirement stated
that the system must have.
3.4.2) Performance Analysis :
• Performance analysis looks at how a specific program is performing
on a daily basis and chronicles what slows down performance and
causes errors now and what could pose a problem into the future.
• In this systems analysis, there are some minor drawbacks that have
been noted.
• The system, while fast and simple, has a small responsiveness issue
that occurs when we resize the window now and then. The problem
hasn’t occurred many times but nevertheless, it still exists.
• The system generates a bill when an order is placed, but the bill isn’t
very user-friendly or useful as it only shows the basic information
needed but cannot be saved either.
• There are many minor glitches in the system which appear
sometimes such as images not loading properly or carts being
duplicated sometimes.

3.4.3) Security Analysis :

• The web server and database server should be protected from
hacking, virus etc
4) System Design :
4.1) Design constraints :
• System design is transition from a user oriented document to programmers or data base
personnel. The design is a solution, how to approach to the creation of a new system.
This is composed of several steps. It provides the understanding and procedural details
necessary for implementing the system recommended in the feasibility study. Designing
goes through logical and physical stages of development, logical design reviews the
present physical system, prepare input and output specification, details of implementation
plan and prepare a logical design walkthrough.
• The database tables are designed by analyzing functions involved in the system and
format of the fields is also designed. The fields in the database tables should define their
role in the system. The unnecessary fields should be avoided because it affects the
storage areas of the system. Then in the input and output screen design, the design should
be made user friendly. The menu should be precise and compact.
4.2) System Model :
1.) Entity RelationshipDiagram: -
1) Data Flow Diagram:-

7
Class Diagram :
Object Diagram: -
Use case diagrams:

Use case diagram consists of actors, use cases and their relationships. These diagrams are
especially important in organizing and modelling the behaviours of a system.

Visit
Website

View Service
Detail

Enquiries

Book DJ

USER
 Sign in

Dashboard

My Profile

Change
Password

Manage Services
(Add / Delete)

Manage Event
Type
(Add / Delete)
Admin

Manage Bookings
(Approved /
Cancelled)
Manage Queries

Search
Booking/Queries

Generate Report
 1. A) File Design/Normalized Database: -

tbladmin : This table store the admin login details

tblbooking: This table store the booking details.

tbleventtype: This table store the type of event details.

tblpage: This table about us and contact us detail.

tblservice: This table store the details of DJ services.

tblbookings: This table store the event booking details.

tbluser: This table store the details user queries.

4.3) User Interface:
Home Page
Contact Us
Book Services

Sign In
Change Password

Sample code:

Login_page :
5.IMPLEMENTATION

▪ Implementation is the stage of the project when the theoretical design is

turned out into a working system. Thus, it can be considered to be the most
critical stage in achieving a successful new system and in giving the user,
confidence that the new system will work and be effective. The
implementation stage involves careful planning, investigation of the
existing system and its constraints on implementation, designing of
methods to achieve changeover and evaluation of changeover methods.

5.1) Software and hardware specifications:

a) Software Requirements: -

Database : MySQL

Server : Apache

Frontend : HTML

Scripting language : Java Script

IDE : Sublime

Technology : PHP

b) Hardware Requirements: -

Processor Speed : 2.0. GHz

RAM : 1GB

Hard Disk : 40GB to 80GB

6.) Output and Report Testing:

6.1) Test Plan:

The purpose of testing is to discover errors. Testing is the process of trying to discover
every conceivable fault or weakness in a work product. It provides a way to check the
functionalities of components, sub-assemblies, and/or a finished product it is the
process of exercising software with the intent of ensuring that the software system
meets its requirements and user expectations and does not fail in an unacceptable
manner. There are various types of tests. Each test type addresses a specific testing
requirement.

6.2) Black Box Testing/Data validations Test cases:

Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of tests,
must be written from a definitive source document, such as specification or requirements
document, such as specification or requirements document. It is a testing in which the software
under test is treated, as a black box. you cannot “see” into it. The test provides inputs and
responds to outputs without considering how the software works
6.3) White Box Testing/functional validations Test cases and results:
White Box Testing is a testing in which in which the software tester has knowledge of the inner
workings, structure and language of the software, or at least its purpose. It is purpose. It is used to
test areas that cannot be reached from a black box level.

23
7) Conclusion and Recommendation:
Our project is only a humble venture to satisfy the needs to manage their project work. Several
user friendly coding have also adopted. This package shall prove to be a powerful package in
satisfying all the requirements of the school. The objective of software planning is to provide a
frame work that enables the manger to make reasonable estimates made within a limited time
frame at the beginning of the software project and should be updated regularly as the project
progresses.

At the end it is concluded that we have made effort on following points…

• A description of the background and context of the project and its relation to work already done
in the area.
• Made statement of the aims and objectives of the project.

• The description of Purpose, Scope, and applicability.

• We define the problem on which we are working in the project.

• We describe the requirement Specifications of the system and the actions that can be done on
these things.

• We understand the problem domain and produce a model of the system, which describes
operations that can be performed on the system.

• We included features and operations in detail, including screen layouts.

• We designed user interface and security issues related to system.

• Finally the system is implemented and tested according to test cases.

24
8) Future Scope :

In a nutshell, it can be summarized that the future scope of the project circles around
maintaining information regarding:

• We can add printer in future.

• We can give more advance software for Nursery Management System including more
facilities
• We will host the platform on online servers to make it accessible worldwide
• Integrate multiple load balancers to distribute the loads of the system
• Create the master and slave database structure to reduce the overload of the database
queries
• Implement the backup mechanism for taking backup of codebase and database on regular
basis on different servers

The above mentioned points are the enhancements which can be done to increase the
applicability and usage of this project. Here we can maintain the records of stocks(Plants).
Also, as it can be seen that now-a-days the players are versatile, i.e. so there is a scope for
introducing a method to maintain the Nursery Management System. Enhancements can be
done to maintain all the Farm,Plants , Pesticides.

We have left all the options open so that if there is any other future requirement in the
system by the user for the enhancement of the system then it is possible to implement them.In
the last we would like to thanks all the persons involved in the development of the system
directly or indirectly. We hope that the project will serve its purpose for which it is develop there
by underlining success of process.

9) Bibliography and References :

1. www.w3schools.com

2.www.apache.org

25
26