Business Management System

Department of Computer Science and Engineering

BANGLADESH UNIVERSITY OF BUSINESS AND

TECHNOLOGY(BUBT)

March, 2022
 Business Management System

A Project Report

Md. Shafiul Hasan 18192203055

Anowara Naznin 18192203054
Aklima Akter Akhi 18192203069
Rafsana Roshid 18192203058
Minhajul Ariefn 18192203065

A Project
Submitted to the department of Computer Science and Engineering
in partial fulfillment of the requirements
for the degree of
Bachelor of Science in Computer Science and Engineering

i
Abstract

Generally, for any business company supplying raw materials from countryside and
outside the country, processes them, and sells them in different parts of the country or
outside of the country. This company are called processing company. Mondol Traders is
one of processing company that we worked for our project. All the activities of Mondol
Traders are done in Microsoft Excel and Paper which has to deal with a lot of files and
papers and it is very difficult to get the report out. There are also many limitations in
the work.

So, Mondol Traders wants a system where they can easily get buyer and seller infor-
mation including purchase, sale, stock, bank statement, ledger book, employee report,
etc. in less paper and time.

We have tried to solve the problem using web based system by converting all the
activities of Mondol Traders to paperless system through Business Management System.

ii
Declaration

We hereby declare that the project entitled ”Business Management System” submitted
in partial fulfillment of the requirements for the degree of Bachelor of Science in Com-
puter Science and Engineering in the Faculty of Computer Science and Engineering of
Bangladesh University of Business and Technology, is our own work and that it contains
no material which has been accepted for the award to the candidate(s) of any other degree
or diploma, except where due reference is made in the text of the project. To the best
of our knowledge, it contains no materials previously published or written by any other
person except where due reference is made in the project.

Signature Signature Signature Signature Signature

Md.Shafiul Hasan Anowara Naznin Aklima Akter Akhi Rafsana Roshid Minhajul Ariefn
ID: 18192203055 ID: 18192203054 ID: 18192203069 ID: 18192203058 ID: 18192203065

iii
Certificate

This is to certify that Md. Shafiul Hasan, Anowara Naznin, Aklima Akter Akhi, Raf-
sana Roshid & Minhajul Ariefn of B.Sc. in CSE has completed their project work titled
”Business Management System” in partial fulfillment for the requirement of B.Sc. in CSE
(Evening) in Bangladesh University of Business and Technology in the year 2022.

P rojectSupervisor
M r.SudiptoChaki
Lecturer

Department of Computer Science and Engineering (CSE)

Bangladesh University of Business and Technology (BUBT)

iv
Acknowledgment

Whenever a module of work is completed successfully, a source of inspiration and

guidance is always there for the student. we, hereby take the opportunity to thank those
entire people who helped our in many different ways.

First and foremost, we are grateful to our project guide Course Instructor/ Mr.
Sudipto Chaki Bangladesh University of Business and Technology, for showing faith in
our capability and providing able guidance and his generosity and advice extended to our
throughout in project.

Last, but least we would like to thank all our faculty and our friends for helping our
in all measure of life and for their kind cooperation and moral support.

Md. Shafiul Hasan (18192203055)

Anowara Naznin (18192203054)
Aklima Akter Akhi (18192203069)
Rafsana Roshid (18192203058)
Minhajul Ariefn (18192203065)

v
Dedication

Dedicated to our parents, teachers, friends, relatives and all who loved us for all their
love and inspirations.

vi
Contents
Abstract ii

Declaration iii

Certificate iv

Acknowledgment v

Dedication vi

List of Figures ix

1 Introduction 1
1.1 Project overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Why this is chosen? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.4 Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.5 User Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.5.1 Entry Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.5.2 Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Analysis of the organization 5

2.1 Analysis of the organization . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 Existing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3 New System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.4 Brief description of Data Flow Diagram . . . . . . . . . . . . . . . . . . . . 5
2.5 ER diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 Requirement Specification 7
3.1 Introduction: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2 Hardware Requirement: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3 Software Requirement: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4 Feasibility Analysis 8
4.1 Evaluation of solution: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.2 Technical Feasibility: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.3 Operational Feasibility: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.4 Economic Feasibility: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

5 Graphical User Interface: 9

5.1 Login: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.2 Dashboard: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.3 Sales input: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.4 Invoice: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.5 Sales report: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.6 Stock report: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

vii
CONTENTS viii

5.7 Sales return input: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

5.8 Sales return report: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.9 Ledger book: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.10 Cash book: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.11 Production report: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.12 Customer report: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.13 Employee report: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.14 Head office expense report: . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

6 Conclusion and Scope of Future Work 17

6.1 Conclusion: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.2 Scope of future Work: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

7 Reference 18
List of Figures
2.1 ER diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

5.1 Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.2 Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.3 Sales input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.4 Invoice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.5 Sales report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.6 Stock report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.7 Sales return input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.8 Sales return report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.9 Ledger book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.10 Cash book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.11 Production report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.12 Customer report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.13 Employee report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.14 Head office expense report . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

ix
1 Introduction
1.1 Project overview
We are working with Mondol Traders. The Mondol Traders keeps track of all the sales,
purchase, payment and received of all the customer and supplier. All the activities and
reports of Mondol Traders are kept in notebooks and as a result the report cannot be
prepared and stored properly.

We have designed the system more than just Agro Companies can manage this system
but it is also possible to manage any company through this software. Especially those
who buy products, process them and resell them will be able to use this software of all
the companies.

1.2 Why this is chosen?

All the activities of the The Mondol are paper-based which makes it very difficult to store
all the information of the sales, purchase and extract it in time.

We have chosen this project to solve all these problems in order to make the The
Mondol more efficient and dynamic and to make all the work very easy to preserve and
to make it easier to do get report where necessary.

1.3 Problem
The current system of “The Mondol” depends on manually recording, searching, reporting
and maintaining the data. The resources required by this manual system are: papers,large
storage space and people. This leads to more overheads in maintaining daily transaction.
Maintaining the current system is highly tedious for the staff because each transaction
and edit needs to be checked thoroughly so as to avoid errors. This process also required
more time which slows down the overall system. There are many drawbacks to the current
system.

1. Paper-based processes: Current system is paper-based

2. Lack of immediate information storage: Data cannot be saved quickly

3. Error prone manual calculation: Due to manual calculations, there is a possi-

bility of incorrect calculation.

4. Preparation of accurate and prompt reports: It is not possible to prepare a

report accurately and quickly

5. Sales purchase monitoring: Buying and selling cannot be properly accounted

for

1
CHAPTER 1. INTRODUCTION 2

6. Revenue management: Selling the right product to the right client at the right
moment at the right price via the right distribution channel with the best cost
efficiency

7. Reputational damage: The company’s reputation is tarnished by miscalculations

8. Heightened compliance risk: compliance risks involve illegal practices and in-
clude fraud, theft, bribery, money laundering and embezzlement.

9. Lack of immediate information search: Information cannot be searched quickly

10. Errors: Since the system here is maintained manually by staff, it is common for
errors to occur. Errors can affect the club financially, legally and affect its goodwill.

11. Time: The current system required a lot of time to enter the data because the
staff has to write it down on the paper. Apart from that, the staff has to check it
properly while writing so that there are no errors.

12. Search: To search for any information from the files, the staff has to go to the
storage room and search for the file manually. This is a tedious and time consuming
work. The workers as well as the members of the club will not be satisfied with the
slow process of searching data.

13. Information Theft: Information theft and information leak can happen in the
club because the staff has access to the files as there is no login system to only allow
certain people to view documents.

14. Disaster Security: In the current system, the data is stored in a storage facility
in the files. In-case of any disaster like: fire, flood etc., the data will be permanently
lost. This will prove fatal for the company because they will loose member, staff and
critical business information. The club will not be able to evaluate the information
of anything and hence will go into financial loses very quickly.

1.4 Objective
All activities of Mondol Traders such as Purchase Sales and Statement Ledger Book Cus-
tomer Report etc. were paper based.

We have been able to web-base all these activities through the design of our system
and all types of report buying-selling customer report laser book trust bank statement ev-
erything can be easily extracted and printed very easily. The design of this system makes
it easy to calculate how much money is in the hands of the company, how much money
an employee is selling in which month, etc. and all these data can be easily researched

We want to make this system accessible so that all company information can be eas-
ily entered, traced, stored securely, data edited and deleted, all employee information,
cashbook accounts, bank accounts can be easily managed.

1. Report: Generating an invoice, ledger book, bank statement, customer report,

sales report, employee report, stock report etc
CHAPTER 1. INTRODUCTION 3

2. Accounts: Account management such as received, payment, cash book etc

3. Buy and sell: All types of sales can be accounted for

4. Stock: Keep track of product stock

5. Centralized Database: A centralized database will ensure security of the data

stored on the system and also ensure that privileges are only given to authorized
people.

6. Disaster Security: All the data stored in the database will remain completely
secure since it is centralized and can be recovered.

7. No Financial Theft: There will be no chance of an insider stealing money because

an IT system has logs, login date, time etc.. The person doing theft will be easily
caught.

8. Faster Search: User can search their information themselves at anytime and any-
where. The staff can search any information by few clicks.

9. Cost: Increase efficiencies and reduce costs.

10. Information: Recording information about the customer, supplier, and employee

1.5 User Requirements

1.5.1 Entry Option
1. Admin user name.

2. Customer name.

3. Supplier name.

4. Employee name.

5. Bank account list.

6. Factory name.

7. Store name.

8. Bulk purchase product name.

9. Bulk purchase product pack size.

10. Bulk purchase.

11. Bulk sales.

12. Product name.

13. Product pack size.

14. Product sales.

CHAPTER 1. INTRODUCTION 4

15. Product return

16. Payment

17. Collection

18. Reinvoice

19. Cancel invoice

1.5.2 Report
1. Bulk sales invoice and challan

2. Bulk purchase invoice and challan

3. Bulk stock

4. Sales invoice and challan

5. Sales return invoice and challan

6. Sales report

7. Sales return report

8. Customer ledger book

9. Author ledger book

10. Customer report

11. Employee report

12. Cash book

13. Bank statement

14. Expense report

15. Income report

16. Product stock

17. Invoice creation sms

18. Payment alert sms

19. Payment confirm sms

2 Analysis of the organization
2.1 Analysis of the organization
There are two types of analysis system.they are:

1. Existing System.

2. New System.

2.2 Existing System

• The system was analog.

• It’s doesn’t have any digital system like online and apps.

• Require more physical work and man power.

• All the manual entry and editing will take more time.

• No level of clearance for the different level of employees.

• Safety of paper documents from the disaster.

• No backup of the information.

2.3 New System

• User login

• Admin login

• Employee

• Add/delete/update information

• Report generate

2.4 Brief description of Data Flow Diagram

A data flow diagram (DFD) maps out the flow of information for any process or system. It
uses defined symbols like rectangles,circles and arrows,plus short text labels,to show data
inputs,outputs, storage points and the routes between each destination. Data flowcharts
can range from simple, even hand-drawn process overviews, to in-depth, multilevel DFDs
that dig progressively deeper into how the data is handled. They can be used to analyze
an existing system or model a new one. Like all the best diagrams and charts, a DFD can
often visually say things that would be hard to explain in words, and they work for both
technical and nontechnical audiences, from developer to CEO. That’s why DFDs remain

5
CHAPTER 2. ANALYSIS OF THE ORGANIZATION 6

so popular after all these years. While they work well for data flow software and systems,
they are less applicable nowadays to visualizing interactive, real-time or database-oriented
software or systems.

2.5 ER diagrams
An entity relationship diagram (ERD), also known as an entity relationship model, is a
graphical representation that depicts relationships among people, objects, places, concepts
or events within an information technology (IT) system.

Figure 2.1: ER diagrams

3 Requirement Specification
3.1 Introduction:
To be used efficiently, all computer software needs certain hardware components or the
other software resources to be present on a computer. These pre-requisites are known
as(computer)system requirements and are often used as a guideline as opposed to an
absolute rule. Most software defines two sets of system requirements: minimum and rec-
ommended. With increasing demand for higher processing power and resources in newer
versions of software, system requirements tend to increase over time. Industry analysts
suggest that this trend plays a bigger part in driving upgrades to existing computer sys-
tems than technological advancements.

3.2 Hardware Requirement:

The most common set of requirements defined by any operating system or software ap-
plication is the physical computer resources, also known as hardware. A hardware re-
quirements list is often accompanied by a hardware compatibility list (HCL), especially
in case of operating systems. An HCL lists tested, compatibility and sometimes incom-
patible hardware devices for a particular operating system or application. The following
sub-sections discuss the various aspects-of hardware requirements.

Hardware Requirement for This Project

• Processor: Intel dual Core, i3
• RAM: 2 GB
• Hard disk: 80 GB

3.3 Software Requirement:

Software Requirements deal with defining software resource requirements and pre-requisites
that need to be installed on a computer to provide optimal functioning of an application.
These requirements or pre-requisites are generally not included in the software installation
package and need to be installed separately before the software is installed.

Software Requirement for This Project

• Operating system: Windows 7/10/11, Linux, Mac OS
• Browser: Any web browser
• Local server: xamp, wamp
• Programming language: Php
• Database: Mysql

7
4 Feasibility Analysis
4.1 Evaluation of solution:
Determine feasibility’s of each solution. The feasibility study is carried out under the
following three areas: (a) Technical Feasibility, (b) Operational Feasibility, (c) Economic
Feasibility.

4.2 Technical Feasibility:

The new system requires only 3 trained person to work with the system. So we will
identify 3 best people from existing system and train them. As our existing system is
purely digital, so we need a one time investment of 3.5 Laks for the purchase of 3 computers
, AC and networking etc. It requires 2Lacks as a operating cost. With the above details
our system is technically feasible as after investing 5.5 Lacks in a year, the company is
still saving 10 Lacks.

4.3 Operational Feasibility:

The new solution is feasible in all sence. The new system demands the expulsion of at
least 1 people from the company. It creates an environment of joblessness and fear among
the employees. It can lead to an indefinite strike in the company also. So the management
must take corrective actions prior in advance in order to start the further proceedings.

4.4 Economic Feasibility:

With the manual system the operating cost of the system is about 15 Lacks.. This cost
comprises salary of 15 people, stationary,electricity, water, telephone etc. But with the
new system this reoccurring cost comes out to be about 5.5 Lacks. Hence the new system
is economically feasible.

8
5 Graphical User Interface:
5.1 Login:

Figure 5.1: Login

9
CHAPTER 5. GRAPHICAL USER INTERFACE: 10

5.2 Dashboard:

Figure 5.2: Dashboard

5.3 Sales input:

Figure 5.3: Sales input

CHAPTER 5. GRAPHICAL USER INTERFACE: 11

5.4 Invoice:

Figure 5.4: Invoice

CHAPTER 5. GRAPHICAL USER INTERFACE: 12

5.5 Sales report:

Figure 5.5: Sales report

5.6 Stock report:

Figure 5.6: Stock report

CHAPTER 5. GRAPHICAL USER INTERFACE: 13

5.7 Sales return input:

Figure 5.7: Sales return input

5.8 Sales return report:

Figure 5.8: Sales return report

CHAPTER 5. GRAPHICAL USER INTERFACE: 14

5.9 Ledger book:

Figure 5.9: Ledger book

5.10 Cash book:

Figure 5.10: Cash book

CHAPTER 5. GRAPHICAL USER INTERFACE: 15

5.11 Production report:

Figure 5.11: Production report

5.12 Customer report:

Figure 5.12: Customer report

CHAPTER 5. GRAPHICAL USER INTERFACE: 16

5.13 Employee report:

Figure 5.13: Employee report

5.14 Head office expense report:

Figure 5.14: Head office expense report

6 Conclusion and Scope of Future Work
6.1 Conclusion:
The project ’Business Management System’ is for computerizing the working in a com-
pany. The software takes care of all the requirements of an average company and is
capable to provide easy and effective storage of information related to sales purchase. It
is great improvement over the manual system has speed up the process. The Business
Management System managing system thoroughly checked and tested with the data and
thus is found reliable. The software takes care of all the requirement of an average com-
pany.

6.2 Scope of future Work:

In our future works we will improve this imperfection and add some functions which are
given below

• Online payment system

• Employee salary management

17
7 Reference
[1] w3schools
https://www.w3schools.com/

[2] php
https://www.php.net/

[3] laravel
https://laravel.com/

[4] javascript
https://www.javascript.com/

[5] jquery
https://jquery.com/

[6] stackoverflow
https://stackoverflow.com/

18