Select Photo Images of Projects Work from among 822 Total Projects

BANKING SOFTWARE
 Presentation On

By The Students Of

Department of Bachelor Of Computer Application

Mahatma Phule Mahavidyalaya , Pimprigaon , Pune -17.
 CONTENTS

 INTRODUCTION
 OBJECTIVE
 EXISTING AND PROPOSED SYSTEM
 ADMINISTRATIVE MODULE
 USER MODULE
 ERD DIAGRAM
 CLASS AND SEQUENCE DIAGRAM
 COMPONENT AND DEPLOYMENT DIAGRAM
 DATA FLOW DIAGRAM
 UML DIAGRAM
 TABLE STRUCTURE
 Login form and other forms related to project
 CONCLUSION
INTRODUCTION
• The project entitled “BANKING SOFTWARE” which keep the day to
day tally records as a complete banking system. It can keep the
information of bank employee, transaction, loan solution, ATM
information and account information. The exciting part of this
project is; it displays the employee details, payment details, loan
details and transaction details
• AIM
In the existing system the transaction are done only manually but
in proposed system we have to computerize all the banking
transaction using the software “BANKING SOFTWARE”
• To study the functions of Banking software.
• To explore the challenges being faced by the
manual system.
• To make a s/w fast in processing , with good user
interface.
• To ensure accurate statistics of product item.
• For easy record of Account Holders and proper
identification.
Existing System
 The existing system is very paper based .
 Relevant and irrelevant information are entere.
 Requirement of manpower is more.
 The data entry , transaction , and retrieval
procedure is very ineffecient.
 There are chances of data misplacement and
wrong data entry.
 This System is insecure.
 It is also inflexible to adapt to user requirements
Proposed system
 The proposed system is reliable , fast ,user-
friendly , and informative.
 Less paper work .
 Requirement of manpower is less.
 Using the application , one can add , modify ,
delete , save , update and print details.
 The system will Display all Account details.
ADMINISTRATIVE MODULE

This module is the main module which performs all the main
operations in the system. The major operations in the system
are:
Admin login
Add/Delete/Update Employee
Withdrawal/deposit/payment Transaction
Creating new Account/Loan account/Fixed Deposit
Searching account information/Transaction information
E-Solution ATM information saving
Report generation
Settings
Change Password
USER MODULE

This module is also a main module which performs all the

main operations in the system. The major operations in the
system are:

User login
Creating New Account/Loan Account/Fixed Deposit
Searching Account Information/Transaction Information
E-Solution ATM information saving
Report generation
Change password
ERD OF BANKING SOFTWARE
Class and Sequence Diagram OF BANKING
SOFTWARE
Component and Deployment Diagram OF
BANKING SOFTWARE
Data Flow Diagram Of Banking software
 Customer Management Generate Customer Report

Generate Employees
Employees Management Report

Accounts Management Generate Accounts Report

Banking
Software
Fixed Deposit Management Generate Fixed Deposit
Management

Saving Account Check Saving Account

Management Details

Current Account Generate Current Account

Management Report

First Level DFD –Banking Software

 Login Check
roles
Manage store details
Admin to
System of
access
Manage customer details

Forgot
passwo Manage Purchasing Details
-rd Manage
Check
Module
Creden Manage Sales Details
s
-tials

Send Manage Payment Details

email
to User Manage Products Profiles

Manage Login Report

Manage User Permission

Manage Roles of User

Manage System Admins

Second Level DFD – Super Market Mgt

System
UML Diagram Of Banking software
Table Structure Of Banking software
 LOGIN FORM

Component and Deployment Diagram

HOME SCREEN
ADD EMPLOYEE
UPDATE MEMBER
TRANSACTION
DEPOSIT
PAYMENT
ACCOUNT INFORMATION
LONE APPLICATION
FIXED DEPOSIT INFORMATION
ACCOUNT INFORMAYON
TRANSACTION LOG
The proposed Banking software is very useful
for all banks.
It manages their inventories , staffs, and
records of Loan payment and transaction .
New features and modules can be easily added
into the system.
This project is very flexible and can adapt to
the requirements of the supermarket and its
users.
THANK YOU
 Presentation On

By The Students Of

Department of Bachelor Of Computer Application

Mahatma Phule Mahavidyalaya , Pimprigaon , Pune -17.
 Introduction .
 Objectives .
 Existing system and Proposed System.
 Problem Of Statement .
 E-R Diagram ,Data Flow Diagram( L-0, L-1, L-2) ,
UML Diagram, Sequence diagram, Component Diagram ,
Class Diagram, Deployment Diagram .
 Login Page & other forms related to project .
 Merits & Demerits.
 Scope & Conclusion .
 The project ‘Supermarket Management
System’ is targeted mainly for big
supermarkets and particularly aims the
automation of supermarket.
 The users will consume less time in
calculation.
 Sales activity will be completed within
minutes unlike manual system.
• To study the functions of Supermarket
management system.
• To explore the challenges being faced by the
manual system.
• To make a s/w fast in processing , with good user
interface.
• To ensure accurate statistics of product item.
• For easy record of goods in store and proper
identification.
 The existing system is very paper based .
 Relevant and irrelevant information are entered and
stored in the same place , this process is very clumsy
and untidy.
 Requirement of manpower is more.
 The data entry , storing , and retrieval procedure is
very ineffecient.
 There are chances of data misplacement and wrong
data entry.
 This System is insecure.
 It is also inflexible to adapt to user requirements
• Time Consumption: The business owner must keep track of sales on daily
basis i.e updating the system manually at the end of the day.
• Poor Communication: A manual Supermarket requires employees and
managers to write down each time an item is removed . If one employee
forgets to mention that the last coffee product has been removed , manager
expects the item to still be available. i.e manual system does not help the
communication in the workplace.
• Physical Counts :One of the difficulties of running a manual Supermarket
system is that physical Supermarket counts must be performed frequently to
control the items in the Supermarket. That is time consuming and hectic.
• Daily Purchases: A manual Supermarket system requires the employees to
write down the items sold during a single work day. This can be a difficult task,
as one employee may lose the list of items sold or another may forget to write
down a sale.
 The proposed system is reliable , fast ,
user-friendly , and informative.
 Less paper work .
 Requirement of manpower is less.
 Increases the productivity of the supermarket.
 Using the application , one can add , modify ,
delete , save , update and print details.
 There’s also a search feature to find products
available in the supermarket.
 The system will display all the items whose name
start with the letter selected by the user.
 D_id work E_id
d_name E_name

Department Employee
D_location E_addr
S_name
has
S_id E_phn
no.
S_addr

has Store

has C_id
P_id
C_name

P_name include
Product Customer C_addr

P_price has
Pays C_phn
partof for no
Payment

Sales P_id P_date Purchase Pu_receipt

S_id
S_time
P_type Pu_cou
P_amount
S_prod S_limit Pu_id nt
 Stores Management

Products Customer
Management management
Super
Market
Management
System

Payment Purchasing
Management Management

Sales Management

Zero Level DFD – Super Market Mgt System

 Stores Management Generate Stores Report

Customer Management Generate Customer Report

Purchasing Management Super Generate Purchasing Report

Market
Mgt
Sales Management System Generate Sales Management

Payment Management Check Payment Details

Generate Product
Products Management Management

First Level DFD - SMMS

 Login Check Manage store details
Admin to roles of
System access
Manage customer details

Forgot
passwo Manage Purchasing Details
-rd
Check Manage
Creden- Modules Manage Sales Details
tials

Send Manage Payment Details

email
to User Manage Products Profiles

Manage Login Report

Manage User Permission

Manage Roles of User

Manage System Admins

Second Level DFD – Super Market Mgt System

 Order Goods

By Product
Arranging Goods

By price
Retailer Selling Goods

Preparing Bill

Buying Items
By cash
Making Payment
Customer
By Credit

Supplying Goods

Supplier
UML Diagram for Supermarket Management System
Admin

Add Admin Information

Admin Id
Customer Login
You Have logged out
successfully..
 Data standardization and accuracy.
 Quick & accurate transactions.
 Reduced missing products and shrinkage.
 Better products management .
 In-stock information of products .
 Scan and Go feature .
 Cost saving due to decrease in manpower .
 Tracking inventory so reordering of products can
be timely.
 DEMERITS OF SUPERMARKET MANAGEMENT SYSTEM

 System Crash .
 Malacious Attacks/hacks.
 Power outage.
 Corrupt Harddrive – can result in the loss
of data .
 Other Technical issues .
 Costly/ Expensive – to maintain the system
This research work covers stock control,
management and tends to correct anomalies in
Supermarket business.
It analyses opening of new stocks, stock updates
and ability to view existing ones.
It provides quick way of operation by capturing
the manual process and automating them.
This project is helpful to computerize the item
transaction, sales activity record keeping which is a
very huge task and maintaining the stock.
The proposed supermarket management
system is very useful for bug supermarket as
well as small ones .
It manages their inventories , staffs, and
records of purchases and sales.
New features and modules can be easily
added into the system.
This project is very flexible and can adapt to
the requirements of the supermarket and its
users.
 PROJECT REPORT ON
“ JEWELLERY SHOP MANAGEMENT SYSTEM”

Submitted to the SavitribaiPhule Pune University, Pune In partial

fulfillment of the requirements for the award of degree
Bachelor of Business Administration

In

COMPUTER APPLICATION By

MR. Radhika Sahadev Pachbole. SEAT NO:16488

UNDER THE GUIDANCE OF Prof.Priti Nevse
(Head of the Department)

DEPARTMENT OF BACHELOR OF BUSINESS

ADMINISTRATIION

COMPUTER APPLICATION
Mahatma Phule Mahavidyalaya Pimpri, Pune-411017
Academic year
2020-2021
 RAYAT SHIKSHAN SANSTHA

CERTIFICATE
This is to certify that a project entitled

“JEWELLERY SHOP MANAGEMENT SYSTEM”

Submitted by

Mss.RADHIKA PACHBOLE SEAT NO: 16488

Is a bonafite work carried out by her under the supervision of

Prof. PritiNevse. And Prof. PritiNevseit is
submitted towards the partial fulfillment of the requirement of Savitribai Phule
Pune University, Pune for the award of the degree of Bachelor of Business
Administration(Computer Application).

Prof. Dnyaneshwar Narwate (Project Guide)

 ACKNOWLEDGMENT

I am very much delighted to present my project work on “JEWELLERY

SHOP MANAGEMENT SYSTEM”.
The words are not enough to express my thanks to Prof. PRITI NEWASE for

providing me with the opportunity to avail the excellent facilities and

infrastructure of the institute.

It is my proud privilege to express my profound gratitude to Prof. PRITI

NEWASE (HOD) BBA(CA) Department, for her astute guidance, constant

encouragement and sincere support throughout my academic course.

I thanks to my honest gratitude to Prof.PRITI NEWASE for her

inspiration, constructive suggestions and affectionate guidance in my project

work completion.

Last but not the least, I express my sincere thanks to all my dear friends and
family members for their constant motivation, moral support and invariable
direction throughout my life.

SENCEEARLY

RADHIKA PACHBOLE.

T.Y.BCA
 INDEX
Sr.No. Content Page No.
1 Introduction 1
2 Scope of System 2
3 Feasibility Study 3
4 Proposed System 4
5 Fact Finding Technique 5

6 Hardware and Software Requirement 6

7 Design Specification

7.1 ER Diagram
7
7.2 Data Flow Diagram

8 Table Design 8

9 Sample Input & Output Screen 9

10 Limitations 10

11 Future Enhancement 11

12 Conclusion 12

13 Bibliography 13
 Introduction
Jewellery Shop Management System is for managing
Product,Customer

, Billing , Payment ,Sales, Quality record of any Jewellery Shop

Management System

They have to maintain all records manually which involves

Record keeping of Product , Customer,Billing

,Payment,Sales,Quality .

. This new system will replace entire manual

Task with computer based system.

 Scope of System

This project deals with the various functioning

In Jewellery Shop Management System. The main idea is

to

Implement a proper process to system.

In our existing system contains a many

operations

Production , Sales,Customers ,Quality, Billing, etc.

To provide a data records of a customer. It helps

To searching details easily.

 Feasibility Study

Feasibility study is made to see if the project on

completion will serve the purpose of the organization for the
amount of work, effort and the time that spend on it.
The document provide the of the project that is
being designed and lists various areas that were considered very
carefully during the feasibility study of this project such as
technical, Economic and Oprational feasibilities.
 Proposed System
The aim of proposed system is to develop a system of
improved facilities. The proposed system can overcome all the
limitations of the existing system. The system provides proper
security and reduces the manual work.

 To computerize the system.

 To reduce data redundancy.
 To eliminate the delays in report generation.
 To facilitate faster searching of information.
 Thus reducing time, energy and cost.
 To give Assurance To the customers About
Maintaining data privacy and security.
Hardware/Software Required

 Windows x/10 operation system.

 Dot Net
 Microsoft office Access.
 Processor: Intel Pentium
 RAM: 4 GB.
 Internal memory : 500 GB.
 System Design:-
1.ER Diagram:-
Process

Username Login Password

Product_Name Billing Manage

Customer Cust_Id

Quantity
Cust_Name
Price Cust_Add

Customer_Name Product Cust_Phone

Item_Id

Has It_Qty
It_Name
It_Cat It_Price

It_type
Product
Total

Product_Price Quantity

Product_Id
 Data Flow Diagram:-
1.Zeroth Level Diagram:-

Product
Management
Customer
Management

Jewellery
Payment
Billing Shop Management
Management Management
System

Sales
Management

Quality
Management
 2.First Level Diagram:-

Product
Management

Customer
Management

Billing Jewellery
Management
Management Billing
Report
System
Payment
Management

Quality
Management

Sales
Management
3)Secound Level Diagram:-

Login
Admin To
System

Cancel

Check

Credentials

Manage
Product
Details
Process

Manage
Customer
Details

Manage
Billing
Details

Manage
Payments
Details

Manage
Quality
Details

Manage
Sales
Details
Class Diagram:-
Product Class Customer Class
+ It_Id: int
+It_Name: String +Cust_Id: int
+It_Cat: String 1 1 +Cust_Name: String
+It_Type: String +Cust_Phone : int
+It_Price: int +Cust_Add : String
+It_Qty: int
+SaveCustomer()
+ SaveProduct() +UpdateCustomer()
+UpdateProduct() +DeleteCustomer()
+DeleteProduct() +ResetCustomer()
+ResetProduct()
1

Billing Class

+Id : int
+Product : String
+Price : int
+Quantity: int
+Total : int

+AddBilling()
+PrintBilling()
 Component Diagram :-

Prouct

Data Access

Encryption

Customer
Security
Jewellery
Shop Billing A
Management
Access Control
System
Encryption
Payments
Persistence

Access Control
Quality

Sales
Database Connector

Database
 Table Design
1 .Product Information :-

2.Customer Information :-
3. Billing Information :-
Input Screens :-
1)Processing :-

2)Login :-
3)Product:-

4) Customer:-
5)Billing :-
Limitations :-

Reports are supposed to be seen managerial level person,but

it is not secured by password so any other person can see the
reports who is operating the system.
If the password of system changed by the wrong person
They no 1 else can access the system until the password is
known.
Single User Interface.

Future Enhancement :-

The System may be further update or modified

At will owing to its simple structure.
Depending on future requirements more changes
Can be made owing to the shop Owner’s need.
 Conclusion :-

To conclude , Project Data Grid works like

a component which can access all the databases and
picks up different functions.

It overcomes the many limitations incorporated

in the attendance.

Bibliography :-

 Visual Basic[Black Book]

 Visual Basic 6.0[The Complete Reference]-By
 Noel Jerke

Online References :-

 www.tutorialpoint.com

 www.w3school.com

 www.google.com

 www.youtube.com
 PROJECT REPORT ON
“ IMS INSTITUTE MANAGEMENT SYSTEM”

Submitted to the SavitribaiPhule Pune University, Pune In partial

fulfillment of the requirements for the award of degree
Bachelor of Business Administration

In

COMPUTER APPLICATION By

MR. Radhika Sahadev Pachbole. SEAT NO:16557

UNDER THE GUIDANCE OF Prof.Priti Nevse
(Head of the Department)

DEPARTMENT OF BACHELOR OF BUSINESS

ADMINISTRATIION

COMPUTER APPLICATION
Mahatma Phule Mahavidyalaya Pimpri, Pune-411017
Academic year
2020-2021
 RAYAT SHIKSHAN SANSTHA

CERTIFICATE
This is to certify that a project entitled

“IMS INSTITUTE MANAGEMENT SYSTEM”

Submitted by

Mss.RADHIKA PACHBOLE SEAT NO: 16557

Is a bonafite work carried out by her under the supervision of

Prof. PritiNevse. And Prof. PritiNevseit is
submitted towards the partial fulfillment of the requirement of Savitribai Phule
Pune University, Pune for the award of the degree of Bachelor of Business
Administration(Computer Application).

Prof. Pallavi Suryawanshi (Project Guide)

 ACKNOWLEDGMENT

I am very much delighted to present my project work on “INSTITUTE

MANAGEMENT SYSTEM”.
The words are not enough to express my thanks to Prof. PRITI NEWASE for

providing me with the opportunity to avail the excellent facilities and

infrastructure of the institute.

It is my proud privilege to express my profound gratitude to Prof. PRITI

NEWASE (HOD) BBA(CA) Department, for her astute guidance, constant

encouragement and sincere support throughout my academic course.

I thanks to my honest gratitude to Prof.PRITI NEWASE for her

inspiration, constructive suggestions and affectionate guidance in my project

work completion.

Last but not the least, I express my sincere thanks to all my dear friends and
family members for their constant motivation, moral support and invariable
direction throughout my life.

SENCEEARLY

RADHIKA PACHBOLE.

T.Y.BCA
INDEX
Sr.No. Content Page No.
1 Introduction 1
2 Scope of System 2
3 Feasibility Study 3
4 Proposed System 4
5 Fact Finding Technique 5

6 Hardware and Software Requirement 6

7 Design Specification

7.1 ER Diagram
7
7.2 Data Flow Diagram

8 Table Design 8

9 Sample Input & Output Screen 9

10 Limitations 10

11 Future Enhancement 11

12 Conclusion 12

13 Bibliography 13
 Introduction
Institute Management System is for managing staff ,

Students, library record of any Institute Management System

They have to maintain all records manually which involves

Record keeping of student , employee , courses ,employee

Salary and attendance and their transaction.

This new system will replace entire manual

Task with computer based system.

 Scope of System

This project deals with the various functioning

In Institute Management System. The main idea is to

Implement a proper process to system.

In our existing system contains a many

operations

Registration , student search , fees , attendance ,performance of

the student , followups etc.

To provide a data records of a customer. It helps

To searching details easily.

 Feasibility Study

Feasibility study is made to see if the project on

completion will serve the purpose of the organization for the
amount of work, effort and the time that spend on it.
The document provide the of the project that is
being designed and lists various areas that were considered very
carefully during the feasibility study of this project such as
technical, Economic and Oprational feasibilities.
 Proposed System
The aim of proposed system is to develop a system of
improved facilities. The proposed system can overcome all the
limitations of the existing system. The system provides proper
security and reduces the manual work.

 To computerize the system.

 To reduce data redundancy.
 To eliminate the delays in report generation.
 To facilitate faster searching of information.
 Thus reducing time, energy and cost.
 To give Assurance To the customers About
Maintaining data privacy and security.
Hardware/Software Required

 Windows x/10 operation system.

 Microsoft visual basic 6.0.
 Microsoft office Access.
 Processor: Intel Pentium
 RAM: 4 GB.
 Internal memory : 500 GB.
 System Design:-
1.ER Diagram:-

Username Login Password

Progressbar

Enquiry Followups

Fees Students

Dashboard
Courses Expenses

Minimize
Logout

About us

Mobile
Stud ID Student Information

Address
Admission
Name Courses

DOB Duration

Gender Faculty

Fees
 Data Flow Diagram:-
1.Zeroth Level Diagram:-

Courses
Management
Student
Management

Institute
Enquiry
Fees Management Management
Management
System

Followups
Management

Expenses
Management
 Data Flow Diagram:-
2.First Level Diagram:-

Student
Management

Courses
Management Enquiry
Report

Followups Institute
Management
Management Followups
Report
System
Fees
Management Students
Report
Enquiry
Management

Expenses
Management
Data Flow Diagram:-
3)Secound Level Diagram:-

Login
Admin To
System

Process

Cancel

Check

Credentials

Manage
Dashboard Enquiry
Details

Manage
Followups
Details

Manage
Students
Details

Manage
Courses
Details

Manage
Fees
Details

Manage
Expenses
Details
 Table Design
1 .Enquiry Information :-

2.Students Information :-
3. Courses Information :-

4.Fees Information :-

5 . Expenses Information :-
Input Screens
Limitations :-

Reports are supposed to be seen managerial level person,but

it is not secured by password so any other person can see the
reports who is operating the system.
If the password of system changed by the wrong person
They no 1 else can access the system until the password is
known.
Single User Interface.

Future Enhancement :-

The System may be further update or modified

At will owing to its simple structure.
Depending on future requirements more changes
Can be made owing to the shop Owner’s need.
 Conclusion :-

To conclude , Project Data Grid works like

a component which can access all the databases and
picks up different functions.

It overcomes the many limitations incorporated

in the attendance.

Bibliography :-

 Visual Basic[Black Book]

 Visual Basic 6.0[The Complete Reference]-By
 Noel Jerke

Online References :-

 www.tutorialpoint.com

 www.w3school.com

 www.google.com

 www.youtube.com