A PROJECT REPORT

ON

THE BOMB DIGZ

A project submitted in partial fulfilment

of the requirements for the award of the degree

OF

BACHELOR OF COMPUTER APPLICATION

UNDER THE SUPERVISION OF: SUBMITTED BY:-

NIKHIL BAJAJ
(Asst. Professor, SGTBIMIT) (04290202017)

SRI GURU TEGH BAHADUR INSTITUTE OF MANAGEMENT AND

INFORMATION TECHNOLOGY

AFFILIATED TO GURU GOBIND SINGH INDRAPRASTHA UNIVERSITY, DELHI

2017-2020

1
 DECLARATION

This web development project titled “THE BOMB DIGZ” towards the
completion of my course requirements for Semester V is my original work and
has been carried out under the guidance of MS. XYZ.

The material borrowed from other sources and incorporated in the report has
been duly acknowledged and referenced.

I understand that I will be held liable and accountable for my project, it is all
done by me without having any copyright(s) of any of the organisation. I further
declare that the work reported in this project has not been submitted and will not
be submitted, either in part or in full, for the award of any other degree or
diploma in this institute or any other institute or university.

DATE:

NIKHIL BAJAJ
(04290202017)

2
 CERTIFICATE

This is to certify that the project entitled: “THE BOMB DIGZ” done by MR. NIKHIL
BAJAJ having university enrolment number 04290202017 is an authentic work carried out
by them at SRI GURU TEGH BAHADUR INSTITUTE OF MANAGEMENT &
INFORMATION TECHNOLOGY. The matter embodied in this project work has not been
submitted earlier for the award of any degree or diplomas to the best of my knowledge and
belief .The suggestion as approved by the faculty was duly incorporated.

DATE:

HOD: Dr. RAJ KUMAR

Guide:

3
 ACKNOWLEDGEMENT

We would like to express our heartfelt gratitude to SGTBIMIT and MS XYZ

for giving us the opportunity to work under their guidance and help us gain
immense professional experience. A sincere thanks to our mentor for giving us
valuable inputs and ideas right from the selection of topic for project till its
successful completion.

We thank MR. RAJ KUMAR KASHYAP (HOD) for their ongoing support
and encouragement in every aspect.

The successful completion of our project would not have been possible without
the dedicated support from all our mentors, family, and friends.

DATE:

NIKHIL BAJAJ
(04290202017)

4
 Abstract

A web page is a selection of website, pictures, video clips and other electronic
resources that is organized on one or several web hosting server, usually
available via the Internet, Mobile phone or a LAN.

The project on web development is made using net beans IDE platform and the
MySQL server. The front end is designed using HTML5, CSS, BOOTSTRAP,
and the back end is designed using JQUERY, JAVASCRIPT, PHP and SQL
DATABASE.

It follows PHP for offering the sessions for the data source connection.
BOOTSTRAP is used for dynamic design of the website. Some frameworks are
used in the project that are available in the internet and are provided the source
code of the project.
The project is e-commerce website for concert ticket booking and merchandise.
User can purchase any merchandise or musical instruments offered by the band
and can book tickets.

5
 TABLE OF CONTENT
Chapter no. TOPIC Page no.

1. INTRODUCTION 10

1.1 INTRODUCTION TO THE PROJECT 11

2. REQUIREMENT ANALYSIS 12

2.1 SOFTWARE REQUIREMENT SPECIFICATION 13-14

2.2 USE CASE DIAGRAM 15

3. SOFTWARE DESIGN 16

3.1 INTRODUCTION 17
3.2 HIGH LEVEL/DETAIL DESIGN() 17
3.3 DATA FLOW DIAGRAM(LEVEL 0) 18
3.4 DATA FLOW DIAGRAM(LEVEL 1) 19

4. DATABASE DESIGN 20

4.1 INTRODUCTION 21
4.2 DATABASE FIELD SPECIFICATION 21-22
4.3 ENTITY-RELATIONSHIP DIAGRAM 23

5. TESTING 24

5.1 INTRODUCTION 25
5.2 TESTING METHODS 25-26
5.3 TEST CASES 26-27

6. ROLES AND RESPONSIBILTY 28

6.1 PROJECT ROLES AND RESPONSIBILITY 29

7. CONCLUSION AND ACHIEVEMENTS 30-31
APPENDICES
BIBLIOGRAPHY

6
 LIST OF FIGURES

Figure Page
Number
Figure 1:Use Case 15
Figure 2: Data Flow Diagram Level-0 18

7
Figure 3: Data Flow Diagram Level-1 19
Figure 4: E-R Diagram 23

8
 LIST OF TABLES

Table Page
Number
LIST OF SYMBOLS 18
DATABASE TABLES DETAILS 22
CART 22
PRODUCTS 22
USER 23
PROFILE 23
PAYMENT 23

9
 CHAPTER 1
INTRODUCTION

10
1.1 INTRODUCTION
Introduction of the project :-
1.1.1 Proposed System
The proposed system is a proper data management system which handles all of the band’s
activities like upcoming concerts and ticket bookings, online availability of the merchandise
and products. The system also provides a safe and secure environment for making the
payments for the purchases.

The proposed system has following advantages over the existing system:

 Admin login: Admin can login and make any appropriate changes to the
website.
 User registration and login: Any new customer can register following which
he/she will be provided with an unique user id and password through which
user will be able to login.
 Online booking: The user can book the concert’s ticket on the web
application in couple of minutes instead of going on to any other third-party
apps.
 Online shopping: The user can access hundreds of products available on the
website and can buy them through the web application making any user on the
earth to have access to the products.
 Online Payment: The website provides a safe and secure payment gateway to
make payments for all of the purchases.
 Uses comparatively less bandwidth.
 Look and feel is better.

1.1.2 Advantages for users:

 User can easily book tickets.

 User can purchase any product instead of going to the store.
 Thus, saves a lot of time.
 User can manage or cancel any or all of the orders through their account.

1.1.3 Advantages for admin:

 Admin can manage all users.

 Admin can make any changes to the website.

11
 Admin can manage or modify the orders placed by the user.

CHAPTER 2
REQUIREMENT ANALYSIS

12
 PROJECT TITLE – THE BOMB DIGZ
2.1 SOFTWARE REQUIREMENTS SPECIFICATION
2.1.1 CATEGORY
Web Application.

2.1.2 PURPOSE
The purpose of developing this web application titled ‘THE BOMB DIGZ’ is an effort made
by the renowned band to provide their massive fan following an application that provides
information about their upcoming concerts, ticket bookings, albums, singles and their highly
demanded merchandise and musical products all at one time, one place.

2.1.3 SCOPE
The purpose of the online management system of the band’s activity is to provide a
convenient and user-friendly application that helps them to book tickets, buy products,
albums and make payments in a safe and secure environment. The system is based on a
relational database with its data management and payment functions. Above all, we hope to
provide a comfortable user experience along with the best pricing available.

2.1.4 FUNCTIONAL REQUIREMENTS

“Functional requirement describe what a system should do.” Functional requirements of our
system are explained below:

 User must have valid User Id and password to login, thus creating their individual
profiles.
 Administration can register new products.
 User can choose products.
 User can book concert tickets.
 User can make a wish list of the products.
 All of the chosen products should be sent to the cart for further checking out.
 User could be able to make payments through his/her credit or debit card or internet
banking.
 User should be told about the successful placement of order and the estimated
delivery date.
 Admin can post new concert’s info and new arrival of products.

13
2.1.5 NON-FUNCTIONAL REQUIREMENTS
Requirement that specifies criteria that can be used to judge the operation of a system are
called non-functional requirements. Non-functional requirements of our system are
mentioned below:

 Secure access of confidential data (user’s details).

 Maximum time availability.
 Better component design to get efficiency at peak time.
 Flexible service based architecture will be highly desirable for future extension.
 Product registration and updating facility is accessible by admin only.

2.1.6 SOFTWARE TOOLS

DATABASE SERVER: Microsoft SQL Server.
CLIENT: Microsoft Internet Explorer or any other web browser.
DEVELOPMENT TOOLS: Apache Net beans 11.0
PROGRAMMING LANGUAGE: HTML, CSS, Java script, bootstrap, PHP-
AJAX.

2.1.7 DEPLOYEMENT
Operating System Server: Windows 8, LINUX, UNIX.

2.1.8 HARDWARE TOOLS

Processor: Intel Core i5.
RAM: 4GB RAM.
Hard Disk: 1TB.

14
 2.2 USE CASE DIAGRAM

SIGN UP

LOGIN

UPLOAD/
MODIFY
PRODUCT

MANAGE
PROFILE

ORDER
PLACING
AND
USER PAYMEN ADMIN
TS

MANAGE
ORDERS

MANAGE
USERS
15
 CHAPTER 3
SOFTWARE DESIGN

16
3.1 INTRODUCTION

This chapter will focus on the design of the system using diagrams to illustrate graphically
certain sections of the software system.

3.2 HIGH LEVEL/DETAILED DESIGN (HLD/DD)

3.2.1 Data flow Diagrams (DFDs)

As information moves through software, it is modified by a series of transformations. A

data flow diagram is a graphical representation that depicts information flow and the
transforms that are applied as data move from input to output.
The data flow diagram may be used to represent a system or software at any level of
abstraction. In fact, DFDs may be partitioned into levels that represent increasing
information flow and functional detail. Therefore, the DFD provides a mechanism for
functional modeling as well as information flow modeling.

LIST OF SYMBOLS

SYMBOL NAME FUNCTION

Data Flow Connect process

Perform some transformation of its

Process input data to yield output data.

A source of system inputs or

Source or sink sink of system outputs
A repository of data, the
arrowhead indicate net
Data Store input and net outputs
to store

TABLE 1

17
3.3 DFD LEVEL 0

VIEW VIEW VIEW ADD TO

PROFILE TICKETS PRODUCTS CART

USER LOGIN

PURCHASE
THE RAPTOR
BAND

ADMIN LOGIN
DELETE
ADD PRODUCT
PRODUCT UPDATE
PRODUCT

18
3.4 DFD LEVEL 1

IF NEW USER
SIGN UP

USER LOGIN ADMIN

AUTHENTICATION IF NOT MANAGES

SUCCESSFUL

USERS
RETRIEVE
AVAILABLE ADD/UPDATE/DEL
PRODUCTS AND ETE PRODUCTS
TICKETS
PRODUCTS

CART CART

MAKE
PAYMENT
PAYMENT

VIEW ORDERS ORDERS

19
 CHAPTER 4
DATABASE DESIGN

20
4.1 Introduction

This article/tutorial will teach the basis of relational database design and explains how to
make a good database design. It is a rather long text, but we advise to read all of it. Designing
a database is in fact fairly easy, but there are a few rules to stick to. It is important to know
what these rules are, but more importantly is to know why these rules exist, otherwise you
will tend to make mistakes!

4.2 DATABASE FIELDS SPECIFICATION

A small write-up on the database, giving the fields, explaining each field etc should be
written. This write-up can be evaluated on the following points.

1. Clarity and conciseness of the database design. Like, whether key is defined, whether
any redundant fields are there etc.
2. Whether data-storage calculations are made, and if so, whether they are done properly
etc.
Whether any data-backup/recovery mechanism is discussed or being thought of.

User Id is the Key of the database. The range of valid values entered below as examples need
not be taken as such. They can be modified by the team.

TABLE NAME DESCRIPTION

CART CONTAINS THE ADDED ITEM IN THE
CART
PRODUCTS CONTAINS THE INFORMATION OF
THE PRODUCTS
USER CONTAINS THE LOGINI
INFORMATION OF THE USERS
PROFILE CONTAINS THE PROFILE
INFORMATION OF THE USERS
4.2.1 TABLE 2
A) CART(ATC)
Field Name Data Type Size Constraint
ID INT 11 Primary Key
CART_ID VARCHAR 20 NOT NULL
PRODUCT_ID INT 20 NOT NULL
QTY INT 20 Not Null
USER_ID VARCHAR 100 Null
4.2.2 TABLE 3
B) PRODUCTS
Field Name Data Type Size Constraint
PRODUCT_ID INT 11 Primary Key
PRODUCT_NAME VARCHAR 20 NOT NULL
PRODUCT_DETAILS INT 20 NOT NULL

21
 PRODUCT_IMAGE INT 20 Not Null
PRODUCT_PRICE VARCHAR 100 Not Null
4.2.3 TABLE 4

C) USER
Field Name Data Type Size Constraint
USER_ID INT 11 Primary Key
PASSWORD VARCHAR 20 NOT NULL
CART_ID VARCHAR 100 NOT NULL
ENABLE/DISABLE INT 1 NOT NULL
4.2.4 TABLE 5

D) PROFILE
Field Name Data Type Size Constraint
USER_ID INT 11 Primary Key
CART_ID VARCHAR 100 NOT NULL
NAME VARCHAR 20 NOT NULL
ADDRESS VARCHAR 20 NOT NULL
PIN_CODE INT 20 Not Null
MOBILE VARCHAR 100 Not Null
EMAIL VARCHAR 100 Not Null
GENDER VARCHAR 100 Not Null
IMAGE VARCHAR 100 Not Null
4.2.5 TABLE 6

E) PAYMENT
Field Name Data Type Size Constraint
ORDER_ID INT 11 Primary Key
AMOUNT VARCHAR 20 NOT NULL
PAY_TIME VARCHAR 100 NOT NULL
PAY_MODE INT 1 NOT NULL
4.2.4 TABLE 6

4.3 ER DIAGRAM
EMAIL
PHONE
ADDRESS

NAME CART
_ID
22
 USER_ID PASSWORD
PIN_CODE
1 1
USER HAS PROFILE

IMAGE ORDERS
CART_ID USER_ID
ENABLE/DI
SABLE

SEARCHES
CART_ID PRODUCT_ID

ID
QTY
n
1
ADDS
PRODUCTS TO
CART

PRODUCT_ID PRODUCT_PRICE 1
USERID
PRODUCT_NAME
PRODUCT_DETAILS

PRODUCT_IMG
MAKES

AMOUNT
n

PAYMENT
PAY_TIME

ORDER_ID
PAY_MODE
PAY_DATE

23
CHAPTER 5
TESTING

24
5.1 Introduction

Executing a program with the intent of finding errors is called testing. Testing is vital to the
success of any system. Testing is done at different stages within the development phase.
System testing makes a logical assumption that if all parts of the system are correct, the goals
will be achieved successfully. Inadequate testing or no testing at all leads to errors that may
come up after a long time when correction would be extremely implementation. The testing
of the system was done on both artificial and live data. In order to test data test cases are
developed. Following are the various methods that are employed for testing:

5.2 METHODS EMPLOYED FOR TESTING

5.2.1 Unit Testing

In unit testing the module is tested independently. It is done to test that the module
does satisfy the functional specification. This is done to check syntax and logical
errors in programs. At the time of preparation of technical specifications, unit test
data was also prepared. The coding for that program was considered after verifying
its output against this test data.
Following are the unit testing methods:
In Conditional Testing, the logical conditions that are given in the module were
checked to see whether they satisfy the functionality of the module. This is done
by using the test data was prepared.
In Loop Testing, different loops in the module like nested loops were tested using
the data. Attempts to execute the loops to their maximum range are done.

5.2.2 Integration Testing

In Integration testing whole system was checked when all the individual modules
were integrated together in order to test whether the system is performing as
according to the requirements specified. Interface errors if any were corrected.
Test data was prepared was fed into the system to check whether the system fails to
detects an error.

5.2.3 Functional Testing

This is done foreach module/sub module of the system.Functional testing serve as a

means of validating wheater the functionality of the system confers the original
user requirement i.e. does the module do what it wa supposed to do? Seprate
schedules were made for functional testing. It involves prepration of test

25
 data,writing test cases,testing for conformance to test cases and preparation of
bug’s listing for non-comformities.

5.2.4 System Testing

System testing is done when the entire system has been fully integrated. The
purpose of the system testing is to test how the different modules interact with each
other and whether the entire system provides the functionality that was expected.
System testing consists of the following steps:
 Program Testing
 System Testing
 System Documentation
 User Acceptance Testing

5.3 TEST-CASES (TC)

The test-cases is basically a list of test cases that need to be run on the system. Some of the
test cases can be run independently for some components (report generation from the
database, for example, can be tested independently) and some of the test cases require the
whole system to be ready for their execution. It is better to test each component as and when
it is ready before integrating the components.

No Test case Title Description Expected Outcome Result

.
1 Successful User The login to the Login should be Passed
Verification system should successful and the
be tried with user should be
the login name connected to
and the correct server.
password.
2 Unsuccessful Login to the Login should fail Passed
User Verification system with a with an error
due to wrong wrong

26
 password password ‘Invalid password’.
3 Unsuccessful Login to the Login should fail Passed
User Verification server with an with an error
due invalid
‘Invalid Login Id’.
to invalid Login id login id
4 The server should An option for Option for Passed
provide the allowing new adding/removing
admin for users and users is shown.
allowing newly deleting old
registered user to users of the
access the system
website.

5 The system A form for Form for register Passed

should provide creating new users is shown
sign up form for users login id of
creating new user the system

Login id
6 Unsuccessful user Filling the Field can’t be Passed
verification if they registration empty
do not enter their form without
all details being entering the
asked. whole details

27
 CHAPTER-6

ROLES AND RESPONSIBILITIES

28
6.1 Project Roles and Responsibilities

6.1.1 ROLE

 Work as a developer, designer, tester of the application.

6.1.2 RESPONSIBILITIES

 Work on definition of development requirements and priorities.

 Data migration.
 Interfaces with other systems.
 Reporting configuration and deployment.
 Set up and maintence of security rights and access permission.
 Contributing to technical strategy,policy and procedure.
 Development and operation of technical testing programmes.
 Production of technical documentation to agreed quality standards.
 Reporting on progress/issues to management and users.

29
 CHAPTER 7
CONCLUSION
AND
ACHIEVEMENTS

CONCLUSION

30
“THE BOMB DIGZ” Software has been designed to purchase or display different products
with their specifications. It is designed to replace the manual system thereby making it more
efficient and easily approachable.
The system is strong enough to withstand regressive daily operations under conditions
where the database is maintained and cleared over a certain time of span. The
implementation of the system in the organization will considerably reduce manual
generation of tickets and payments, time and also provide readily calculated reports.
The project from a personal point of view also helped us in understanding the following
aspects of project development:

1. The planning that goes into implementing a project.

2. The Importance of proper planning and an organized methodology.

3. The key element of team spirit and co-ordination in a successful project.

FUTURE SCOPE

The future scope of this project is to provide the best of the services possible. This project
lacks of real payment processing with which it can be more powerful and convenient for
users. Once the payment gateway is incorporated, we can buy a domain name and a web
server for this website to publish it on the internet with which the reach of this website to
anyone would be very easy. We can add the venue’s map to know about the area and space
for the people which would help users to know about the limited tickets of the venue for the
band’s concert.

31
APPENDICE

32
 BIBLOGRAPHY

 http://www.google.co.in
 http://www.youtube.co.in
 http://www.wikipedia.com
 http://www.w3schools.com

PHP for the Web: Visual Quick Start Guide

Book by Larry Ullman

PHP and MySQL Web Development

Book by Luke Welling

33