A

Minor Project Report

On
“SPORTS SHOP MANAGEMENT SYSTEM”
Submitted in partial fulfilment for the award of the degree
of
BACHELOR OF COMPUTER APPLICATIONS
from
CHAUDHARY CHARAN SINGH UNIVERSITY, MEERUT
(Session: 2022-23)

Meerut Institute of Technology (Professional Courses), Meerut

Submitted To: Submitted By:

Mr. Lalit Kumar Hamza Nabeel
HOD, BCA Deptt. BCA 5th Sem
Roll No: 201110106040
 TABLE OF CONTENTS

Content Page No.

1. Declaration 3

2. Certificate 4

3. Acknowledgement 5

4. Abstract 6

5. Introduction of the Project 7

6. Objectives of the Project 8

7. Hardware and Software Requirements 11

8. Project Analysis & Designing

- DFD

- ER Diagram

9. Modules

- Process logic of each module

10. Input / Output Screenshot

11. Coding

12. Testing

13. Future Scope

14. References
 DECLARATION

I, Hamza Nabeel, bearing roll number 201110106040, hereby declare that the work which is

being presented in the Minor Project, entitled “SPORTS SHOP MANAGEMENT

SYSTEM” in partial fulfilment for award of Degree of “Bachelor of Computer Applications”

in Department of Computer Application is submitted under the Guidance of “Mr. Manoj

Kumar”.

I have not submitted the matter presented in this work anywhere for the award of any other

Degree.

Date: ..............................

Student Name: Hamza Nabeel

Roll No.: 201110106040

 CERTIFICATE

Certified that the Project Report entitled “SPORTS SHOP MANAGEMENT SYSTEM”

submitted by Hamza Nabeel bearing roll no. 201110106040 in partial fulfilment of the

requirements for the award of the degree of Bachelor of Computer Applications is a record

of the student’s own work carried out under my supervision and guidance. To the best of our

knowledge, this Minor Project work has not been submitted anywhere for the award of any

other Degree.

It is further understood that by this certificate the undersigned does not endorser approve of

any statement made, opinion expressed or conclusion drawn therein but approve Minor

Project for the purpose for which it is submitted.

Mr. Manoj Kumar Mr. Lalit Kumar

(Project-Coordinator) (HOD, BCA Deptt.)
 ACKNOWLEDGEMENT

Many people have supported me, in different ways, during the work with the minor project.

I would like to thank my guide Mr. Manoj Kumar & HOD Mr. Lalit Kumar for their kind

and active support and valuable guidance during the work process. My family has, as always,

offered me their unconditional support, during my efforts in completing this Minor Project.

However, it would not have been possible without the kind support of many individuals and

institution.

I would like to extend my sincere thanks to each and every member related to MIT (PC).

Student Name: Hamza Nabeel

BCA Vth Sem
Roll No: 201110106040
.
 ABSTRACT

The sports shop management system is a software application designed to automate the

management of a sports shop. The system provides an easy-to-use interface for managing

inventory, sales, and customer information. It includes features such as product catalogue

management, sales tracking, customer management, and employee management. The

system allows users to create, modify and delete products, manage inventory levels, track

sales, and generate reports. The customer management module allows users to create and

manage customer profiles, track customer orders and purchase history. The system also

provides the functionality for employee management, including scheduling, payroll, and

performance tracking. The sports shop management system helps streamline operations,

improve productivity and efficiency, and provide better customer service.

 TITLE OF THE PROJECT

SPORTS SHOP
MANAGEMENT SYSTEM
 INTRODUCTION

The “Sport Shop Management System” is targeted to automate almost all of the processes

mentioned above to reduce the clerical labor of the staff working in Shops both technical as

well as Accounts departments using the software Industry’s latest technologies and cost

effective tools there by providing better control to the management by avoiding manual errors

etc..

In this project, modules under study are Material Issues module, Reports module.

The proposed system is computerized and has been developed using advance language

therefore it gives more facilities than present system. It provides quick access to any data. In

this system user have to enter the data only once and then it gets linked with all files. This

reduces the workload of user and it is also a time saving process.

The information about any Subscriber can be easily retrieved. The system
maintains all records easy.

Advantages of Proposed System:

• All the information about sale, purchase will be maintain properly in this system.

• All manual calculation of sale or all the money management will be performed by the
computer automatically.

• This system will provide timely report information.

• It will produce report for sale, bill information.

• The computer can hold amount of data in its storage device.

• The operation and speed of the computer is very high.

 • We can calculate result and print any report within seconds.

• Any difficulties we can solve easily.

• A database application can be stored in computer effectively.

• It is very user friendly and easy to handle.

So, the computerized system is more suitable than the manual system.
 PURPOSE OF THE PROJECT

Sports Shop Management System is developed following system development stages for

smooth running and management of the Shop. The system was carefully designed to ensure

maximum efficiency of the system at the Shop. The system can skilfully and carefully codded

to seal any possible loopholes in the system.

The system will indeed help the Shop management and the esteemed staff members to

manage and steer the Shop’s functionality and transactions to realize its maximum potential

in addition to its competence in the Sports Shop business field.

The objective of Sports Shop management system project is to provide help shop owner to

serve his customers.

Due to huge losses suffered by the Shop due to the existing manual system, the Shop

management opted for a computerized system, which would provide the following facilities:

1. Be friendlier to customers and the staff.

2. Improve customer care and service at the Shop.

3. Increase the Shop performance.

4. Reduce the operational costs of the Shop.

THE BASIC OBJECTIVES OF THE PROPOSED SYSTEM

1. To enable computerization of sports shop.

2. To enable automated data entry methods.

3. Ensure efficient and reliable communication within the Shop.

4. Avoid data entry errors by use of input masks.

5. Enable easy authorized modification of data.

6. Enforce security measures to avoid unauthorized access to guest records.

7. Enable fast and easy retrieval of guest records and data for fast reference activities.
 HARDWARE AND SOFTWARE
REQUIREMENTS

HARDWARE REQUIREMENTS:

1. RAM : 4GB RAM

2. Processor: Dual Core

Software Requirements:

Operating System : Windows 7

Front End : Netbean Java
Back End : MYSQL
Web server : Apache
Tool : XAMPP
 PROJECT ANALYSIS AND DESIGNING
DFD SYMBOLS: -
1. External Entity:
The producer or the consumer of information that resides outsides the bound of the system to
be modelled. The following rectangular shape denotes it.

2. Process:
It is the agent that performs the transformation of information from one state to another. The
following shape denotes it.

3. The Data Flow

A data flow connects the output of an object or process to the input of another object or
process. The arrows’ denote flow of intermediate data value within a computation. The
arrowhead indicated the direction of flow of data.

4. Data Store
A repository of data is a passive object within a DFD for later access. A data store does not
generate any operations on its own but merely responds to requests to store and access data.
The following shape denotes it.
 ER DIAGRAM OF OHRS
1. Data flows
Data flows model the passage of the system and are represented by
lines joining the system components. An arrow indicates the direction
of the flow and the lines is labeled by the name of the data flow. Flow
of data in the system can take place.
Use Case Diagram:
E-R Diagram:
 USER CHARACTERISTICS

User Interfaces
The User Interface Screens are described in table 1.
Table 1: Shop Management User Interface Screens
Screen Name Description

Login Log into the system as a CSR or Manager

Reservation Retrieve button, update/save reservation, cancel reservation, modify

reservation, change reservation, adjust room rate, accept payment
type/credit card

Check-in Modify room stay (e.g., new credit card), check-in customer (with or
without a reservation), adjust room rate, special requests, accept
payment type/credit card

Checkout Checkout customer, generate bill

Shop Payment Accept payment for room and food

Room Service/Restaurant Create order, modify order, view order, cancel order, generate meal
bill

Customer Record Add or update customer records

Administer Rooms Availability and rates

Administer User Create, modify, and delete users; change password

Reports Select, view, save, and delete reports

Software Interfaces
The system shall interface with MySQL database.

Hardware Interfaces
The system shall run on all platforms.
Communication Interfaces
The system shall be a standalone product that does not require any communication interfaces.

18
Item Entry
• Customer first name
• Customer last name
• Customer address
• Customer phone number
• Number of occupants
• Product name
• Rate description
• Guaranteed room (yes/no)
• Customer feedback
• Payment received (yes/no)
• Payment type
• Total Bill

19
 CONSTRAINS

1. In the case of any type of problem in students’ verification no functionality is

defined in the system to correct it or inter communication among users are also not
available.

2. The fees is taken manually, as there is not any module for online payments.

3. The total marks is get by the students only after some time of exam, because in case
of subjective paper, t h e exam dept will dept will evaluate the answers the answers
and declare the result
.
User Section:

It consist the navigation bar which consist options as home, Login , register , Examination,
Test results and logout .

1. Home – Home page of Sports Shop Management.

2. Login – User can login.

3. Register – From this page new customers can register for test.

4. Logout – User logged out from software.

20
 SYSTEM ANALYSIS
Software Requirement Specification (SRS) What is SRS?

Software Requirement Specification (SRS) is the starting point of the software developing

activity. As system grew more complex, it became evident that the goal of the entire system

cannot be easily comprehended. Hence the need for the requirement phase arose. The software

project us initiated by the client needs. The SRS is the means of translating the ideas of the minds

of clients (the input) into a formal document (the output of the requirement phase.)

The SRS phase consists of two basic activities:

1) Problem/Requirement Analysis:

The process is order and more nebulous of the two, deals with understand the problem, the goal

and constraints.

2) Requirement Specification:

Here, the focus is on specifying what has been found giving analysis such as representation,

specification languages and tools, and checking the specifications are addressed during this

activity.

The requirement phase terminates with the production of the validate SRS document. Producing

the SRS document is the basic goal of this phase.

Role of SRS

The purpose of the Software Requirement Specification is to reduce the communication gap

21
between the clients and the developers. Software Requirement Specification is the medium

through which the client and user needs are accurately specified. It forms the basis of software

development. A good SRS should satisfy all the parties involved in the system.

Purpose

The purpose of this document is to describe all external requirements for mobile task manager.

It also describes the interfaces for the system.

Existing System

The existing system for Shops Management System activities uses open source standard

& technologies. It had been developed on WINDOWS 2000 PROFESSIONAL platform with

„POSTGRESQL‟ database. All the shops of the power distribution company limited are made

through the open source standards & technologies. The user interaction is in GUI (Graphical

User Interface) mode.

Shops are required for the following purposes.

1. Capital works

2. Operation and Maintenances Works

3. Other Commercial activities like hiring equipment etc.

The „Shops Management System package‟ is targeted to automate the almost all of the processes

mentioned above to reduce the clerical labour of the staff working in Shops both technical and

as well as Accounts departments using the software Industry’s latest technologies and cost

effective tools there by providing the better control to the management by avoiding manual errors

etc...,

22
 Feasibility Study

According to this feasibility study this report is integrated with some important points. Those
points are,
• Definition/purpose of a feasibility study.
• Who conducts the feasibility study?
• Components of a feasibility study for a Shop Reservation system.

This report has written for a Shop Reservation system. The main object of preparing this
document is to give the clear ideas about changes and modifications of their new system for user.

Definition/Purpose of a Feasibility Study

A feasibility study is defined as an estimate or analysis of the possible impact of a proposed
system. In the other hand we can say that whether decision makers can implement the project
according to customer’s requirements or not. The feasibility study will include wide data
associated to financial and operational impact. It also consisted with advantages of new system
and drawbacks of current system.
The feasibility study is conducted to support the decision-makers in creating the decisions,
1. What will be the great importance of the Shop reservation system?
2. Whatever the decision that they take it should improve the quality of developing system

Technical Feasibility

In technical feasibility study, one has to test whether the proposed system can be developed using

existing technology or not. It is planned to implement the proposed system using Windows 2000

Professional, JSP and Apache Tomcat Wed Server. The Organization already possesses

Windows 2000 Professional Operating System. It is evident that the necessary hardware and

software are available for the development and implementation of the proposed system. Hence

the solution is technically feasible.

Economic Feasibility:

As part of this, the costs and benefits associated with the proposed system are to be compared

23
and the project is economically feasible only if benefits outweigh costs. The Organization has

already its own satellite link, and a host of SUN FIRE 6800 servers. So it need not invest newly

for the internet connection and also the organization initiated to use Open Source in project

development, hence there is 0 additional cost incurred for the tools that will be used.

Operational Feasibility:

This test of feasibility checks if the system works with least difficulties when it is developed and

installed. The technical staff has sufficient knowledge of the tools being

used and the users need just to know how to access and run the programs in the Apache Web

Sever. Hence it is concluded that the system is operationally feasible.

24
 SCREEN SHOTS

DATA BASE TABLES

• Database Design

25
26
27
INTERFACE DESIGN

28
29
30
31
32
33
34
 CODING
import [Link].*;
import [Link].*;
import [Link];

/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/

/*
* [Link]
*
* Created on Mar 18, 2010, [Link] PM
*/

/**
*
* @author gagan
*/
public class CustListUI extends [Link] {

/** Creates new form CustListUI */

public CustListUI() {
initComponents();
}

/** This method is called from within the constructor to

* initialize the form.
* WARNING: Do NOT modify this code. The content of this method is
* always regenerated by the Form Editor.
*/
@SuppressWarnings("unchecked")
// <editor-fold defaultstate="collapsed" desc="Generated Code">//GEN-
BEGIN:initComponents
private void initComponents() {

jButton1 = new [Link]();

jButton2 = new [Link]();
jScrollPane1 = new [Link]();
jTable1 = new [Link]();

setDefaultCloseOperation([Link].EXIT_ON_CLOSE);
setTitle("Customers list");

[Link](new [Link]("Tahoma", 1, 12)); // NOI18N

35
 [Link]("Display/Query");
[Link](new [Link]() {
public void actionPerformed([Link] evt) {
jButton1ActionPerformed(evt);
}
});

[Link]("Back to Menu");
[Link](new [Link]() {
public void actionPerformed([Link] evt) {
jButton2ActionPerformed(evt);
}
});

[Link](new [Link](
new Object [][] {
{null, null, null, null, null},
{null, null, null, null, null},
{null, null, null, null, null},
{null, null, null, null, null}
},
new String [] {
"Customer ID", "Name", "Address", "City", "Phone"
}
));
[Link](jTable1);

[Link] layout = new [Link](getContentPane());

getContentPane().setLayout(layout);
[Link](
[Link]([Link])
.addGroup([Link]()

.addGroup([Link]([Link])
.addGroup([Link]()
.addContainerGap()
.addComponent(jScrollPane1, [Link].DEFAULT_SIZE,
587, Short.MAX_VALUE))
.addGroup([Link]()
.addGap(171, 171, 171)
.addComponent(jButton1)
.addGap(38, 38, 38)
.addComponent(jButton2)))
.addContainerGap())
);
[Link](
[Link]([Link])
36
 .addGroup([Link]()
.addComponent(jScrollPane1, [Link].PREFERRED_SIZE, 172,
[Link].PREFERRED_SIZE)
.addGap(35, 35, 35)

.addGroup([Link]([Link])
.addComponent(jButton1)
.addComponent(jButton2))
.addContainerGap(19, Short.MAX_VALUE))
);

pack();
}// </editor-fold>//GEN-END:initComponents

private void jButton1ActionPerformed([Link] evt) {//GEN-

FIRST:event_jButton1ActionPerformed
// Before writting the followng line, you should import the line:
// import [Link].*; at the top of your application
DefaultTableModel model = (DefaultTableModel) [Link]();
// Clear the existing table
int rows = [Link]();
if (rows > 0) {
for (int i = 0; i < rows; i++) {
[Link](0);
}
}
// SQL Query
String query = "SELECT * FROM shopkeeper";
try {
// Connect to MySQL database
[Link]("[Link]").newInstance();
Connection con = (Connection)
[Link]("jdbc:mysql://localhost:8080/shop","root","");
// Create SQL statement and execute query.
Statement stmt = [Link]();
ResultSet rs = [Link](query);

// Iterate through the result and display on screen

while ([Link]()) {
String Sid = [Link]("Shopper_id");
String SName = [Link]("Name");
String SAddress = [Link]("Address");
String SCity = [Link]("City");
String SPhone = [Link]("Phone");
[Link](Sid + "|" + SName + "|" + SAddress + "|" + SCity + "|" +
SPhone);
[Link](new Object[] {Sid, SName, SAddress, SCity, SPhone});
37
 }
} catch (Exception e) {
[Link](this, [Link]());
}
}//GEN-LAST:event_jButton1ActionPerformed

private void jButton2ActionPerformed([Link] evt) {//GEN-

FIRST:event_jButton2ActionPerformed
[Link](false);
new MainMenuUI().setVisible(true);
}//GEN-LAST:event_jButton2ActionPerformed

/**
* @param args the command line arguments
*/
public static void main(String args[]) {
[Link](new Runnable() {
public void run() {
new CustListUI().setVisible(true);
}
});
}

// Variables declaration - do not modify//GEN-BEGIN:variables

private [Link] jButton1;
private [Link] jButton2;
private [Link] jScrollPane1;
private [Link] jTable1;
// End of variables declaration//GEN-END:variables

38
39
*/

/*
* [Link]
*
* Created on Mar 18, 2010, [Link] PM
*/

/**
*
* @author gagan
*/
public class ItemListUI extends [Link] {

/** Creates new form ItemListUI */

public ItemListUI() {
initComponents();
}

/** This method is called from within the constructor to

* initialize the form.
* WARNING: Do NOT modify this code. The content of this method is
* always regenerated by the Form Editor.
*/
@SuppressWarnings("unchecked")
// <editor-fold defaultstate="collapsed" desc="Generated Code">
private void initComponents() {

jButton2 = new [Link]();

jButton1 = new [Link]();
jScrollPane1 = new [Link]();
jTable1 = new [Link]();

setDefaultCloseOperation([Link].EXIT_ON_CLOSE);
setTitle("List of items in shop");

[Link]("Back to Menu");
[Link](new [Link]() {
public void actionPerformed([Link] evt) {
jButton2ActionPerformed(evt);
40
 }
});

[Link](new [Link]("Tahoma", 1, 12));

[Link]("Display/Query");
[Link](new [Link]() {
public void actionPerformed([Link] evt) {
jButton1ActionPerformed(evt);
}
});

[Link](new [Link](
new Object [][] {
{null, null, null, null},
{null, null, null, null},
{null, null, null, null},
{null, null, null, null}
},
new String [] {
"Item ID", "Name", "Description", "Price"
}
));
[Link](jTable1);

[Link] layout = new [Link](getContentPane());

getContentPane().setLayout(layout);
[Link](
[Link]([Link])
.addGroup([Link]()
.addGroup([Link]([Link])
.addGroup([Link]()
.addContainerGap()
.addComponent(jScrollPane1, [Link].DEFAULT_SIZE, 564,
Short.MAX_VALUE))
.addGroup([Link]()
.addGap(171, 171, 171)
.addComponent(jButton1)
.addGap(38, 38, 38)
.addComponent(jButton2)))
.addContainerGap())
41
 );
[Link](
[Link]([Link])
.addGroup([Link]()
.addComponent(jScrollPane1, [Link].PREFERRED_SIZE, 172,
[Link].PREFERRED_SIZE)
.addGap(35, 35, 35)
.addGroup([Link]([Link])
.addComponent(jButton1)
.addComponent(jButton2))
.addContainerGap([Link].DEFAULT_SIZE, Short.MAX_VALUE))
);

pack();
}// </editor-fold>

private void jButton2ActionPerformed([Link] evt) {

[Link](false);
new MainMenuUI().setVisible(true);
}

private void jButton1ActionPerformed([Link] evt) {

// Before writting the followng line, you should import the line:
// import [Link].*; at the top of your application
DefaultTableModel model = (DefaultTableModel) [Link]();
// Clear the existing table
int rows = [Link]();
if (rows > 0) {
for (int i = 0; i < rows; i++) {
[Link](0);
}
}
// SQL Query
String query = "SELECT * FROM Item";
try {
// Connect to MySQL database
[Link]("[Link]").newInstance();
Connection con = (Connection)
[Link]("jdbc:mysql://localhost:3306/shopkeeper","root","kvuc");
// Create SQL statement and execute query.
42
Statement stmt = [Link]();
ResultSet rs = [Link](query);

// Iterate through the result and display on screen

while ([Link]()) {
String ITid = [Link]("Item_id");
String IName = [Link]("Item_Name");
String IDesc = [Link]("Description");
String IPrice = [Link]("Price");

43
 TESTING
Testing techniques and Testing strategies Software testing is a critical element of software

quality assurance and represents the ultimate review of specification, design and coding. In fact,

testing is the one step in the software engineering process that could be viewed as destructive

rather than constructive.

A strategy for software testing integrates software test case design methods into a well-planned

series of steps that result in the successful construction of software. Testing is the set of activities

that can be planned in advance and conducted systematically. The underlying motivation of

program testing is to affirm software quality with methods that can economically and effectively

applied to both strategic to both large and small-scale systems

44
 STRATEGIC APPROACH TO SOFTWARE TESTING
The software engineering process can be viewed as a spiral. Initially, system engineering defines

the role of software and leads to software requirement analysis where the information domain,

functions, behavior, performance, constraints and validation criteria for software are established.

Moving inward along the spiral, we come to design and finally to coding. To develop computer

software we spiral in along streamlines that decrease the level of abstraction on each turn.

A strategy for software testing may also be viewed in the context of the spiral. Unit testing begins

at the vertex of the spiral and concentrates on each unit of the software as implemented in source

code. Testing progresses by moving outward along the spiral to integration testing, where the

focus is on the design and the construction of the software architecture. Taking another turn on

outward on the spiral we encounter validation testing where requirements established as part of

software requirements analysis are validated against the software that has been constructed.

Finally, we arrive at system testing, where the software and other system elements are tested as

a whole.

Table Given below outlines the tests that were performed on the system to ensure correctness

and unearth errors, which were subsequently debugged.

45
 SCOPE OF THE PROJECT
The Software Requirements Specification (SRS) will provide a detailed description of the

requirements for the Shop Reservation System (HRS). This SRS will allow for a complete

understanding of what is to be expected of the SSS to be constructed. The clear understanding

of the SSS and its’ functionality will allow for the correct software to be developed for the end

user and will be used for the development of the future stages of the project. This SRS will

provide the foundation for the project. From this SRS, the HRS can be designed, constructed,

and finally tested.

This SRS will be used by us for constructing the SSS and the Shop end users. We will use the

SRS to fully understand the expectations of this HRS to construct the appropriate software. The

Shop end users will be able to use this SRS as a “test” to see if the constructed system is up to

their expectations. If it is not to their expectations the end users can specify how it is not to their

liking and the SRS will be changed to fit the end users’ needs.

46
 CONCLUSION

The project is identified by the merits of the system offered to the user. The merits of this project
are as follows: -
• It’s a web-enabled project.
• This project offers user to enter the data through simple and interactive forms. This is very
helpful for the client to enter the desired information through so much simplicity.
• The user is mainly more concerned about the validity of the data, whatever he is entering.
There are checks on every stages of any new creation, data entry or update so that the user
cannot enter the invalid data, which can create problems at later date.
• Sometimes the user finds in the later stages of using project that he needs to update some of
the information that he entered earlier. There are options for him by which he can update the
records. Moreover there is restriction for his that he cannot change the primary data field.
This keeps the validity of the data to longer extent.

47
 REFERENCES

YOUTUBE: -
[Link]
JavaTpoint: -
[Link] [Link]/j ava-tutorial
W3Schools: -
[Link]

48