Jewellery Management System - Project
Jewellery Management System - Project
Project Report on
By
NIKITA BORKAR & SHRUTIKA RAUT
Through
Alandi(D), Pune
Alandi(D), Pune
CERTIFICATE
I, NIKITA BORKAR & SHRUTIKA RAUT ,hereby declare that this project work
entitled JEWELLERY MANAGEMENT SYSTEM submitted at MIT, Arts Commerce
and Science College, Alandi(D), (Affiliated to Savitribai Phule Pune University) is
a record of original work done by me under the supervision and guidance of
Prof.NISHIGHANDHA BHALEKAR, Department of Computer Application.
Signature :
Date :
INDEX
Sr No Content Page No
1 INTRODUCTION :- 1
• Introduction to System 2
• Motivation 3
• Problem Statement 4
• Goals/Purpose/Objective 5
• Literature Survey 6
2 SYSTEM ANALYSIS :- 8
• Existing System 9
• Scope and Limitations of Existing System 10
• Stack Holders 12
• Requirement Analysis 13
1. Functional Requirement 13
2. Security Requirement 14
3 SYSTEM DESIGN :- 15
• Data Model 16
• System Model 19
1. Context Level Diagram (CLD) 19
2. Data Flow Diagram (DFD) 20
3. Entity Relationship Diagram (ERD) 21
4 IMPLEMENTATION DETAILS :- 22
• Software/Hardware Requirements 23
CONCLUSION :- 24
FUTURE SCOPE :- 25
BIBLIOGRAPHY AND REFERENCES 26
INTRODUCTION
INTRODUCATION TO
SYSTEM
• Jewellery Management System shops sells various
jewellery items and it is very difficult to categorize these
items on the basis of their manufacturing dates, type
gold of used to manufacture it such as either using 24k
or 22k.
• Jewellery Management System Project is a user friendly
application software which is used by the jewellery
vendors to record the sales and stock of readymade,
ordered ornaments purchased by the customer.
• This project handles the complete automation regarding
the transaction. It also enables us to add records
regarding new customer new ornaments.
MOTIVATION
• The motivation behind a Jewellery Management System
stems from the need for efficient organization, tracking
and management of various aspects of the jewellery
business, including inventory, sales, customer inventory,
customer information and financial transactions.
• Such a system can streamline operations reduce errors,
enhance customer service, and ultimately improve
profitability for jewellery retailers and wholesalers.
PROBLEM STATEMENT
• The problem Statement for a Jewellery Management
System involves addressing the challenges faced by
jewellery businesses in efficiently managing their
inventory, sales. Customer data, and financial transactions.
Specifically, the system aims to:
1. Stream lime inventory management
2. Enhance sales management
3. Improve customer relationship management
4. Facilitate reporting and analytics.
OBJECTIVE OF THE SYSTEM
ANALYSIS
EXISTING SYSTEM
• The existing system is very much time consuming.
• As the existing system is manual it has more chances of
human errors.
• More manpower is required to maintain the system.
• Removing error from an insert could be very time
consuming.
SCOPE OF SYSTEM
• The system covers following scope:
1. Scope of the project is the system on which the
software is installed is project is developed
application and it will work for a particular institute
2. In short, this system is using for both customer as well
as the manager or admin.
3. All the manual work should be converted into
computerized so that the load of employees should
decrease.
4. The database should be stored in computer rather
than in register manually.
5. No need to do paperwork.
PROJECT PERSPECTIVE
• From a project perspective, features of a Jewellery
Management System should align with the goals and
requirements of the project stakeholders. Here are some
key features to consider:
1) Requirements Gathering and Analysis
2) Project Planning and Management
3) User Interface Design and Prototyping
4) Inventory Management Module
5) Sales and Order Management Module
6) Customer Relationship Management
7) Supplier Management Module
8) Reporting and Analytics Module
9) Security and Access Control
10) Investors
REQUIREMENT ANALYSIS
FUNCTIONAL REQUIREMENTS
• Functional requirements for a Jewellery management
System typically included features and capabilities that
enables efficient management of various aspects of a
Jewellery business.
1) Inventory management
2) Sales and order management
3) Customer management
4) Pricing and Discount management
5) Supplier management
6) Repair and maintenance Tracking
7) Security and Access control
8) Integration and scalability
9) Integration and mailability
• Access control
• Authentication and Authorization
• Data Encryption
• Regular Auditing and monitoring
• Secure software Development Practices
• Physical Security
• Vendors security
• Employee Training and Awareness.
SYSTEM
DESIGN
DATA MODEL
1. CONTEXT LEVEL DIAGRAM
• It is a graphical representation of system as a whole
consisting only one process.
• It represents flow of data throughout the system.
• It aims to show how entire system works.
• There is only one process in the system and all data flows
either in or out process.
• CLD demonstrates the interactions between process and
external entity.
• CLD do not contain data source or data store.
• CLD is also called 0th level diagram.
• CLD shows three things:-
I. All external entities.
II. A single process labelled 0 that represents entire
system.
III. A major information flows that is data flows between
external entity and process
2. DATA FLOW DIAGRAM
• Components of DFD:-
1) Process:- Process is a word perform on or in response
to incoming dataflows. Process name is identified by
numbers. Process has “verb, phrases label” in DFD.
2) External Entity:-External Entities are source or
destinations or sinks that is outside that system which
may have people organization student, patient,
supplier, customer and so on. External Entity has
“noun, phrases label”.
3) Data Flow:- Data flow represents an input of data to
process or output of data from a process. Data Flow
has only one direction of a flow between symbols.
Data Flow has “noun, phrases label” it shows
movement of data.
4) Data Store:-Data is kept in data store file. Data is
stored for later use. Data cannot move directly from
one data stored to another data store; data must be
moved by process.
3 . ENTITY RELATIONSHIP DIAGRAM
• An Entity Relationship Diagram is a type of flowchart that
illustrates how “entities” such as people, objects or
concepts relate to each other within a system.
• ER diagrams are most often used to design or debug
relational databases in the fields of software engineering,
business information systems, education and research.
• ER diagrams are related to data structure diagrams which
focus on the relationships of elements within entities
instead of relationships between entities themselves.
• Common symbols:-
1. Entities
2. Relationships
3. Attributes
4. Connecting lines
5. Cardinality
SYSTEM MODEL
CONTEXT LEVEL DIAGRAM(CLD)
Admin
Admin
JEWELLERY
Registration Details Ordered Details
MANAGEMENT
Bill Details Payment Details
SYSTEM
Employee Employee
Employee Details Jewellery Details
Personal Details
Jewellery Details
Jewellery Details
Customer Customer
Requirement details
Payment / Bill details
DATA FLOW DIAGRAM
Bill Login
Login Database
Admin
1.0 Customer
Admin Login
Registration
Registration
Customer Customer
2.0
Requirement
Jewellery Price
Order
Jewellery Price
Order
Order details
Customer
Receipt Details
Customer
3.0
Jewellery Details
Bill Generation
Jewellery Details
Bill Details
Order Process
Bills
ENTITY RELATIONSHIP DIAGRAM
cname
c_no
date
1 M
Admin Report c_id
Generate
p_id
1
M
Has For
Payment
p_no
p_name Generate Bill
M
M c_no
1 M
price date
Product Has Purchase vat
Order M
c_no
Is
date
cname
Places Pays
Silver Gold
Diamond
1 1
Customer
c_no
B] SOFTWARE REQUIREMENT
1)PHP
2)SQL
3)XML,AJAX
4)Operating System-Window 7 ultimate
CONCLUSION
• www.google.com
• www.studentproject.com