JEWELLERY MANAGEMENT SYSTEM PROJECT REPORT
PROJECT REPORT
ABSTRACT
Jewellery shops sells various
types of Jewellery items and it is very difficult to categorize these items on
the basis of their manufacturing dates, type of gold used to manufacture it
such as either using 24K or 22K. Which items comes under the category of ISI
Gold Mark and which items are of local brand. It is also very difficult to
analyze the overall transaction for a particular period of time and which
ornaments are not available in the shop. To solve these problems this system has
been developed. This system will follow the steps
and rules to meet user requirements on demand and on time. Apart from this it
will remove the difficulties faced by the admin to manage their shop and can be
easily handled by the admin without any technical knowledge of the platform
used and about the system. Through this system employees working under a
particular shop can be easily managed and overall transactions of particular
date and time can easily be viewed.
The current system does not
provide the method to back up the database which is very important for any
business transactions. Current system provides the details of overall business
transactions but they do not provide information on sells/purchase in and
sells/purchase out. By using this technique shop manager can use their business
strategy such as cost cutting method for their business process to gain maximum
profit.
Through this new Jewellery
management system, shop managers can easily handle their shop and business
transactions by accessing a single window. This system will have Utilities,
Transactions and Report generations menus. Utilities section will deal with
backing up databases either on daily basis, timely basis, monthly basis etc as
set by the admin, adding new employee, deleting new employee, managing existing
employee details, adding new customer, adding and deletions of new supplier,
changing the password, categorize different Jewellery items etc.
Transaction will deal with
financial accounting part of this business scenario. It will provide
information on sales, purchase, Cash In and Cash Out associated with this
business process.
Generating report by accessing
information stored in database is another important feature of this system.
This system will able to generate as per user requirement in user friendly
manner. User does not require any technical details to generate reports. They
have to submit their requirements by using different options available. This
section will able to generate reports on sales, purchase, Cash In and Cash Out
between a given time interval. If the date option will not be used, it will
generate report from the starting date of business to the current date. However
user can refine their query by using any specific date and time. But
maintaining the same quality or upgrading the present one is not an easy task
because quality is the ultimate picture of the entire business. Good quality of
a product depends on many factors e.g. sound infrastructure, better management
control, etc. So to obtain the optimum quality, jewellers have to upgrade those
ingredients by which the quality is affected. To upgrade those ingredients the
jewellers have to depend on some types of data. So, if the decision making
person of the business wants to have a grip on the total business, he/she will
have to have a knowledge of the entire flow of data and information within the
organisation .It cannot be done without the help of a Business Related
Software.
Jewellery management system is developed in Asp.Net, which can keep track
of all your business activity in a jewellery shop from small segments to large
and very large segments.As we all know the jewellery trade can
be divided into three major categories i.e.
1)
Retail
2)
Wholesale
3)
Export
Main Features Of Jewellery Management System:
Creation of unlimited types
of purity
Each purity can be divided into 50 grades depending on percentage of alloys.
Each purity can be divided into 50 grades depending on percentage of alloys.
Every single information regarding the artisan/dealer can be stored here e.g. name & address of the artisan, making charge of an ornament etc.
Every single information regarding the customer can be stored here e.g. name & address of the customer etc.
There are many types of stones in the business which are categorised according to:
1) Diamond : It can be divided into many categories e.g. round, square, Marquise etc.
2) Colour Stones : Ruby, Pearl, Emerald, etc.
Module:
User
My
Account
Product
Details
Category
Order
PrintOrderForm
Admin
OrderCustomerDetails
OrderProductDetails
Category
OrderProcessed
OrderCancelled
Special
Product
Product
Reports
Technologies Used in Project
1. VB.Net as front end.
2. My SQL Server as back end.
Platform Used in Jewellery Management Shop
1. .NET
Software Used
1. Windows 7.
2. Visual studio 2008.
3. My SQL Server.
Hardware Requirements
· Processor – Pentium III or higher version.
· Ram – 250 MB.
· Hard Disk – 500 MB.
· Monitor.
· Keyboard.
CHAPTER 2
2.
SYSTEM REQUIREMENTS
As a Result of careful analysis of the requirements of developing
this project and as per the needs of the project, the requirements are
determined to the company. The Requirements are being classified as Hardware
and Software Requirements respectively.
They are summarized in the form of tables as follows:
2.1 HARDWARE REQUIREMENTS:
Hardware interface describe the
logical and physical characteristics of each interface between the software
product and the hardware components of the system.
PROCESSOR : Dual core
HARD DISK : 40GB
RAM : 512MB
MONITOR : 15”SVGA Digital Color Monitor
PEN DRIVE : 512 MB
CD-ROM DRIVE : 52X
MODEM : D Link 56Kbps
KEY BOARD : 104
keys
MOUSE : Optical Mouse
2.2 SOFTWARE REQUIREMENTS:
Software interface describe the
connections between this product and other specific software components (name
and version), including databases, operating systems, tools, libraries and
integrated commercial components. It describes the services needed and the
nature of communications.
Front-End Design : Asp.Net with C# 2008
Back-End
Database : Sql Server 2005
Operating System : Windows XP, Vista, Windows 7
CHAPTER 4
SYSTEM
ANALYSIS -
EXISTING SYSTEM
At present all the activities in
transaction are handled manually. Manual data processing system, whole
providing economy, flexibility and adaptability at low data volumes become more
complex when the volume of data becomes large. As an organization expands in
size and function, a stage is reached when manual procedures become inadequate
and inefficient. No matter how many clerks are employed a stage is reached then
it becomes impossible to systemize such a large amount of information. What is
required then is an upgrading in the class of information processing
technology.
The present system is not sufficient
to hold all the information that is necessary for the processing. So the
library is in need of new computerized system, which is very flexible,
user-friendly and capable of holding the system in a robust manner.
LIMITATIONS OF EXISTING SYSTEM
There
were a lot of reasons for the introduction of the new system. They are mainly
due to the drawbacks and efficiency of the existing system.
v
Physical volume of the data is very large.
v
The delay in information search and retrieval.
v
Problems in updating and backup.
v
Damage of papers containing the information.
v
Considerable time taken for report generation.
v
Accuracy of data is very lower in manual system.
PROPOSED SYSTEM
The system study phase studies the
problem, identifies alternate solution, evaluates these solutions and finally
recommends best solution. The system gives the structure and function of the
system. A detailed system study is essential for developing an efficient
system. The proposed system provides a better user interface. The system is a
menu driven program.
ADVANTAGES OF PROPOSED
SYSTEM
v The proposed system can be
utilized for easy documenting and accessing various data carriers such as
forms, reports, records etc.
v Automation makes the
system to be user-friendly and hastily in manipulation and generation of
valuable reports providing menu driven facilities.
v Accuracy and security of
data will be more comfortable for the organization.
v Computerization will avoids human
errors due to inexperience in data entry, manipulation etc.
v The paper work occurred in the
manual system can be completely avoided.
FEASIBILITY STUDY -
During system analysis, a feasibility
study of the proposed system is carried out to see whether it is beneficial to
the organization.
The integration unit is currently
manual. To get the detailed information on production, bagging etc large
bundles of files have to be looked into. It is very time consuming affair. An
operator has to keep in mind or search a file for the details of department for
the data. So working with the existing system is quite tedious. Whereas
considering the merits of the new system it is very beneficial. The results of
the feasibility study are given below:
TECHNICAL FEASIBILITY STUDY
It is a study of resource availability
that may affect the availability to achieve an acceptable system. It is
essential that the process of analysis and definition be conducted in parallel
with an assessment of technical feasibility.
It centers on the existing computer
system and to what extent it can support the proposed system. Though
information in manual system is enormous, it is easily handled by the Access
(which is a RDBMS software). It is easy to find and buy a system, which support
this software. So it is technically feasible.
ECONOMIC FEASIBILITY STUDY
Tremendous is the range of changes
that accompanies the new technology. Introduction of a computerized system has
some merits and demerits can lead to monetary gains. The cost to buy a computer
system for running this software is quite cheap. We get benefit because we
serve more borrowers quickly and easily. So this system is economically
feasible.
BEHAVIORAL FEASIBILITY STUDY
The hierarchy of the new system is
much better than the old. The new system is very much user friendly and the
operational cost is bearable. The maintenance and working of the new system
needs less human effort.
CHAPTER 5
OBJECT ORIENTED ANALYSIS - JEWELLERY MANAGEMENT SYSTEM PROJECT
LOGICAL DESIGN:
The logical flow of a system and define the boundaries of a system. It includes
the following steps:
Reviews the current physical system - its data
flows, file content, volumes , frequencies etc.
Prepares output specifications - that is,
determines the format, content and frequency of
reports.
Prepares input specifications -
format, content and most of the input functions.
Prepares edit, security and control
specifications.
Specifies the implementation plan.
Prepares a logical design walk through of the information flow, output,
input, controls and
implementation plan.
Reviews benefits, costs, target dates and system constraints.
PHYSICAL DESIGN:
Physical system produces the working
systems by define the design specifications that tell the programmers exactly
what the candidate system must do. It includes the following steps.
Design the physical system.
Specify input and output media.
Design the database and specify
backup procedures.
Design physical information flow
through the system and a physical design Walk through.
Plan system implementation.
Prepare a conversion schedule and target date.
Determine training procedures, courses and
timetable.
Devise a test and implementation
plan and specify any new hardware/software.
Update benefits , costs , conversion date and
system constraints
Design/Specification activities:
Concept formulation.
Problem understanding.
High level requirements proposals.
Feasibility study.
Requirements engineering.
Architectural design.
MODULE DESIGN -
ADMIN
The Administrator logs in using the admin login. In this module two operations
are done. During login the Login and Password is verified with that in the
database
INPUT DESIGN
The design of input focuses on controlling the amount of input required,
controlling the errors, avoiding delay, avoiding extra steps and keeping the
process simple. The input is designed in such a way so that it provides
security and ease of use with retaining the privacy. Input Design considered
the following things:
o What data should be given as input
o How the data should be arranged or coded
o The dialog to guide the operating personnel in providing input.
o Methods for preparing input validations and steps to follow when error occur.
OBJECTIVES
Input Design is the process of converting a user-oriented description of the input into a computer-based system. This design is important to avoid errors in the data input process and show the correct direction to the management for getting correct information from the computerized system.
It is achieved by creating user-friendly screens for the data entry to handle
large volume of data. The goal of designing input is to make data entry easier
and to be free from errors. The data entry screen is designed in such a way
that all the data manipulates can be performed. It also provides record viewing
facilities.
When the data is entered it will check for its validity. Data can be entered
with the help of screens. Appropriate messages are provided as when needed so
that the user will not be in a maize of instant. Thus the objective of input
design is to create an input layout that is easy to follow
OUTPUT DESIGN
A quality output is one, which meets the requirements of the end user and presents the information clearly. In output design it is determined how the information is to be displaced for immediate need and also the hard copy output. It is the most important and direct source information to the user. Efficient and intelligent output design improves the system's relationship to help user decision-making.
Designing computer output should proceed in an organized, well thought out
manner; the right output must be developed while ensuring that each output
element is designed so that people will find the system can use easily and
effectively. When analysis design computer output, they should :
Identify the specific output that is needed to meet the requirements.
Select methods for presenting information.
Create document, report, or other formats that contain information produced by
the system.
Analysis is the process of extracting
the needs of the system and what the system must do to satisfy user’s
requirements. Object Oriented Analysis is made to develop a series of solution
models that describes computer software, which works to satisfy the users. The
goal of Object Oriented Analysis is first to understand the domain of the
problem and the system responsibilities by understanding hoe the users use or
will use the system. This is accomplished by constructing several models of the
system. OOA process consists of the following steps:
1. Identify the actors.
2. Develop a simple business process model using UML
activity diagram.
3. Develop a Use Case.
4. Develop interaction diagrams
5. Identify classes.
4.1 USE CASES AND USE CASE DIAGRAMS: JEWELLERY MANAGEMENT SYSTEM PROJECT
A use-case is a UML modeling element
that describes how a user of the proposed system will interact with the system to
perform a discrete unit of work. It describes and signifies a single interact
with the system to perform a discrete unit of work. It describes and signifies
a single interaction over time that has meaning for the end user (person,
machine or other system), and is required to leave the system in a complete
state: either the interaction completed or was rolled back to the initial
state.
·
A use case typically has requirements and constraints that describe the
essential features and rules under which it operates.
·
A use case may have an associated Sequence diagram illustrating behavior
over time – who does what and to whom, when.
·
A use case typically has scenarios associated with it that describe the
work flow over time that produces the end result. Alternate work flows (to
capture exceptions, etc.) are also allowed.
A use case diagram captures
use cases and actor interactions. It describes the functional requirements of
the system, the manner that outside things (actors) interact at the system
boundary and the response of the system.
4.2 SEQUENCE
DIAGRAM:
A sequence diagram is a structures
representation of behavior as a series of sequential steps over time. It is
used to depict work flow, message passing and how elements in general cooperate
over time to achieve results.
A sequence diagram models a dynamic view of
the interactions between model elements at runtime. Sequence diagrams are
commonly used as explanatory models for use case scenarios.
o
Each sequence element is arranged in a horizontal sequence, with
messages passing back and forward between elements.
o
An actor element may be used to represent the user initiating the flow
of events.
o
Stereotyped elements, such as boundary, control and entity, may be used
to illustrate screens, controllers and database items respectively.
o
Each element has a dashed stem called a lifeline, where that element
that exists and potentially takes part in the illustrations.
Sequence diagram in UML, indicates
how events cause transitions from object to object. Once examining a use-case
has identified events, the modeler creates a sequence diagram- a representation
of how events cause flow from one object to another as a function of time. The
sequence diagram is a shorthand version of the use-case. It represents key
classes and the events that cause behavior to flow from class to class.
4.3 ACTIVITY DIAGRAM:
The
UML activity diagram is used to indicate the flow of the interaction within a
specific scenario by means of graphical representation. An activity diagram
uses rounded rectangles to imply a specific system function, arrow to represent
flow through the system, decision diamonds to deflect a branching decision and
solid horizontal lines to indicate that parallel activities are occurring.
Some
of the elements of Activity diagrams as follows
·
Activity: an activity organizes and specifies the participation of subordinate
behaviors, such as sub-activities or actions, to reflect the control and data
flow of a process.
·
Initial Node: The initial element is used by the Activity and State Machine diagrams.
In Activity diagrams, it defines the start of flow when an activity is invoked.
·
Final Node: There are two nodes used to define a final state in an activity. The
final element indicates the completion of an activity diagram is aborted. The
other type of final node, flow final, depicts an exit from the system but has
no effect on other executing flows in the activity.
·
Decision Nodes: A decision is an element of an activity diagram that indicates a point
of conditional progression: if a condition is true, then processing continues
one way, if not, then another. This can also be used as a merge node in that
multiple alternate flows can be merged (but not synchronized) to form one flow.
The following are examples of these modes of decision element.
·
Fork: The fork/join elements have different modes of use. They are as
follows:
1. To fork or split the flow into number of concurrent
flows.
2. To join the flow of number of concurrent flows.
3. To both join and fork a number of incoming flows to
a number of outgoing flows.
5.4 DATA
DESIGN:
Data design creates a
model of data and information that is represented at a high level of
abstraction. The structure of data has always been an important part of
software design. Data design plays a vital role at the program component level,
application level and business level.
In program component
level, the design of data structures and algorithms are manipulated. At the
application level, the data model is translated into a database and at the
business level, the collection of information in the database are recognized
into “data warehouse”.
In this project, “Jewellery management system”, the tables and database creation are carried out
in designing model phase according to the data elements. All the tables that
have been used in Estate Builder are described in Appendix-A.
CHAPTER 6
SYSTEM IMPLEMENTATION - JEWELLERY MANAGEMENT SYSTEM PROJECT
Implementation
includes all those activities that take place to convert from the old system to
the new. The old system consists of manual operations, which is operated in a
very different manner from the proposed new system. A proper implementation is
essential to provide a reliable system to meet the requirements of the
organizations. An improper installation may affect the success of the
computerized system.
IMPLEMENTATION METHODS:
There are several methods for
handling the implementation and the consequent conversion from the old to the new
computerized system.
The most secure method for conversion
from the old system to the new system is to run the old and new system in
parallel. In this approach, a person may operate in the manual older processing
system as well as start operating the new computerized system. This method
offers high security, because even if there is a flaw in the computerized
system, we can depend upon the manual system. However, the cost for maintaining
two systems in parallel is very high. This outweighs its benefits.
Another commonly method is a direct
cut over from the existing manual system to the computerized system. The change
may be with in a week or with in a day. There are no parallel activities.
However, there is no remedy in case of a problem. This strategy requires
careful planning.
A working version of the system can
also be implemented in one part of the organization and the personnel will be
piloting the system and changes can be made as and when required. But this
method is less preferable due to the loss of entirety of the system.
IMPLEMENTATION PLAN:
The implementation plan includes a description of
all the activities that must occur to implement the new system and to put it
into operation. It identifies the personnel responsible for the activities and
prepares a time chart for implementing the system. The implementation plan
consists of the following steps.
v List all files required
for implementation.
v Identify all data
required to build new files during the implementation.
v List all new documents
and procedures that go into the new system.
The implementation plan should
anticipate possible problems and must be able to deal with them. The usual
problems may be missing documents; mixed data formats between current and
files, errors in data translation, missing data etc.
POST IMPLEMENTATION REVIEW:
After the system is implemented, a
review should be conducted to determine whether the system is meeting
expectations and where improvements are needed. System quality, user confidence
and operating systems statistics are accessed through such technique event
logging, impact evaluation and attitude surveys. The review not only assesses
how well the proposed system is designed and implemented, but also is a
valuable source of information that can be applied to a critical evaluation of
the system.
The
reviews are conducted by the operating personals as well as the software
developers in order to determine how well the system is working, how it has
been accepted and whether adjustments are needed. The review of the system is
highly essential to determine the future enhancements required by the system.
The system can be considered successful only if information system has met it
objectives. The review analyses the opinion of the employees and identifies the
attitudes towards the new computerized system. Only when the merits and
demerits of the implemented system are known, one can determine what all
additional features it requires are. The following are the issues to be
considered in the evaluation of the system.
v The
change in the cost of operation after the installation of the computerized
system.
v The
basic change that has been effected after the introduction of the system.
v The
improvement in the accuracy of the computations.
v The
acceptance of the new system by the staff and the convenience it brought to
them.
v The
change in the effectiveness caused by the implementation of the new system.
A study of the system has revealed that
the employees due to the user friendliness have accepted the system, reduced
the number of errors, increased accuracy and decreased cost of operations. The
system also pays for efficient and speedy execution of operations compared to
the earlier system.
CHAPTER
7
TESTING - JEWELLERY MANAGEMENT SYSTEM PROJECT
7.1 INTRODUCTION:
Testing is the set of
activities that can be planned in advanced and s conducted systematically.
Testing requires that the developer discard preconceived notions of the
“correctness” of the software just developed and overcome a conflict of
interest that occurs when errors are encounterd.Testing principles are
·
All tests should be traceable to customer requirements
·
Testing should be planned long before the testing begins
·
Testing should begin “in the small” and progress towards testing “in the
large”.
·
Exhaustive testing is not possible
·
To be most effective, testing should be conducted by an independent
third party.
Testing objective are
·
Testing is the process of executing a program within the intent of
finding an error.
·
A good test case is one that has high probability of finding an
as-yet-undiscovered error.
·
A successful test is one that un covers an as yet-undiscovered error
There
are various testing strategies available to accommodate from low-level testing
to high-level testing as discussed below.
7.2 TEST PLAN
Testing is the major quality control measure employed during software
development. In the project, the first test considered is the unit testing. In
this unit testing, each modules of the system are tested separately. This is carried
out during programming stage itself. Each module should work satisfactory as
regard from the module.
After the entire module are checked independently and completed then the
integration testing is performed to check whether there is any interface
errors. Then those errors are verified and corrected.
And
also the security test is performed to allow only authorized persons to this
system. Finally, the validation testing is performed to validate whether the
customer requirements are stratified are not.
7.3 UNIT TESTING
The unit testing is carried out on coding. Here different modules
are tested against the specifications produced during design for the modules.
Unit testing mainly focused first in the smallest and low level modules,
proceeding one at a time. Each module was tested against required functionally
and test cases were developed to test the boundary values.
Unit testing focuses verification effort on the smallest unit of
software design the software component or module. The unit test focuses on the
internal processing logic and data structures within the boundary of the
component. This type of testing can be conducted in parallel for multiple
components.
7.4 INTEGRATION TESTING:
Integration testing is a systematic technique for consulting the
software architecture while at the same time conducting test to uncover errors
associated with interfacing. The objective is to take unit tested components
and build a program structure that has been dictated by design.
7.5 VALIDATION TESTING:
Validation testing is that validation succeeds when software functions
in a manner that can be reasonably expected by the user. Validation testing
begins after the culmination of integration testing, software is completely
assembled as a package; interfacing errors have been uncovered and corrected.
The
error detecting during this testing is
·
Incorrect Function
·
Input Condition Errors
·
Database Error
·
Performance Error
·
Initialization and Interface Error
7.6 SECURITY TESTING:
Security testing verifies that protection mechanisms built into a system
will, in fact, protect it from improper penetration. The system security must,
of course, be tested for invulnerability from flank or rear attack.
Test case
·
The system provides authentication by means of validating the username
and password. It won’t allow the user gives the exact password and username.
CHAPTER
8
Future Enhancement - JEWELLERY MANAGEMENT SYSTEM PROJECT
This system is developed such a way
that additional enhancement can be done
without much difficulty. The renovation of the project would increase the
flexibility of the system. Also the features are provided in such a way that
the system can also be made better and efficient functionality The programs
were coded in an easier and more structured manner so that may further
modifications may be incorporated easily. The processing time in this system is very lesser compared to existing
system. This system has good flexibility of accommodating any more
changes that might arise in the future also. In this system, data integrity is
maintained and data redundancy is avoided and it increase system efficiency. The database is
designed in such a way that it will be also helpful for enhancement of the system
CHAPTER
9
Conclusion - JEWELLERY MANAGEMENT SYSTEM PROJECT
The system “Jewellery Management system” deals with purchase
and sales processing of a Jewellery shop. This system has been developed
to satisfy all the proposed requirements. The process of recording details
about supplier, item, Billing and customers is more simple and easy. The system
reduces the possibility of errors to a great extent and maintains the data in an
efficient manner. User friendliness is the unique feature of this system. The
system generates the reports as and when required. The system is highly
interactive and flexible for further enhancement.The coding is done in a simplified and easy to understandable manner so
that other team trying to enhance the project can do so without facing much
difficulty. The documentation will also assist in the process as it has
also been carried out in a simplified and concise way.
1 comment:
Helped me alot thanks 😊
Post a Comment