"Sales and Inventory Management System": Mr/Ms.
"Sales and Inventory Management System": Mr/Ms.
PROJECT REPORT
ON
For
Semester V
Submitted by
Mr/Ms.______________
Guided by
Prof. ______________
Submitted to
Computer Department
Vadgaon (Bk)
Date:
CERTIFICATE
This is to certify that Ms. ______has successfully completed her project work
entitled “SALES AND INVENTORY MANAGEMENT SYSTEM” in partial fulfillment of
Masters of Computer Applications program for the year 2009 – 2010. She has
worked under our guidance and direction.
___________________ __________________
I would like to take this opportunity to express my gratitude towards all the people
who have in various ways, helped in the successful completion of my project.
I must convey my gratitude to Prof. Navnath Shete for giving me the constant source
of inspiration and help in preparing the project, personally correcting my work and
providing encouragement throughout the project.
I also thank all my faculty members for steering me through the tough as well as
easy phases of the project in a result oriented manner with concern attention.
Thanking You,
________________
DECLARATION
____________________
Introduction
System Introduction
For optimal sales and inventory management processes, you need robust
functionality for managing your logistics facilities. Support for inventory
management helps you record and track materials on the basis of both quantity
and value.
Using this software we can reduce costs for warehousing, transportation, order
fulfillment, and material handling – while improving customer service.
You can significantly improve inventory turns, optimize the flow of goods, and
shorten routes within your warehouse or distribution center. Additional benefits of
inventory management include improved cash flow, visibility, and decision making.
Employees can plan, enter, and document warehouse and internal stock
movements by managing goods receipts, goods issues, storage, picking and
packing, physical stock transfers, and transfer postings.
Problems In existing system
As we know manual system are quite tedious ,time consuming and less efficient
and accurate in comparison to the computerized system.
1. Time consuming
2. Less accurate
3. Less efficient
The scope of this system is to provide user efficient working environment and more
output can be generated through this. This system provides user friendly interface
resulting in knowing each and every usability features of the system.
This system helps in tracking records so that past records can be verified through
them and one can make decisions based on the past records. This system
completes the work in a very less time resulting in less time consumption and high
level of efficiency.
This system is developed in such a way that even a naïve user can also operate the
system easily. The calculations are made very quickly and the records are directly
saved into databases and the databases can be maintained for a longer period of
time. Each record can be retrieved and can be verified for the future transactions.
Also this system provides high level of security for data leaking as only admin
people can access the database no changes can be made in it until it verifies the
user login id and password.
We also have operator login through which operator can take orders but can’t
make changes in the database. Limited access is available to the operator.
Feasibility Study
As we know each and every project needs to have a feasibility study for the
complete understandability of the project. We will consider 3 types of feasibility
study they are technical feasibility, operational feasibility and economical
feasibility.
Technical Feasibility:
This new system requires 6 fully trained people to run the system perfectly.
1 admin person to maintain database n other 5 to handle the system interface and
order making things.
With the above details our system is technically feasible as after investing 14 Lacs
in a year, the company is still saving Rs 15 Lacs PA.
Operational Feasibility:
The new solution is feasible in all sense but operationally it is not. The new
system demands the expulsion of at least 15 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.
Economic Feasibility:
With the manual system the operating cost of the system is about 60 Lacks
P.A. This cost comprises salary of 25 people, stationary, building rent, electricity,
water, telephone etc. But with the new system this reoccurring cost comes out to
be about 20 Lacks P.A. Hence the new system is economically feasible.
Operating Environment – Hardware and Software
HARDWARE REQUIREMENTS
Processor: intel i3
RAM: Recommended 256MB
Hard Disk: Minimum 20GB
SOFTWARE REQUIREMENTS
It support for inventory management helps you record and track materials
on the basis of both quantity and value.
For warehouse management, you can track quantity and value of all your
materials, perform physical inventory, and optimize your warehouse
resources
User Requirements
FUNCTIONAL REQUIREMENTS
A. INPUT/OUTPUT
B. PROCESSING
2. System should inform the pending order and make changes if the order is
dispatched.
C. ERROR HANDLING
1. Should report any errors on duplicate primary keys.
3. Should report any data type mismatches any field on the forms.
NON-FUNCTIONAL REQUIREMENTS
ER Diagram
Use case Diagram for Supplier
Checks Inventories
Tracks Order
Customer
Dispatch
Sendsorder on time
Invoice
Supplier
Updates Records
Use Case Diagram for Customer
Studies
Requirements
Invoice
Customer
Send GRN
Class Diagram for a customer order
Customer Order
Cust_Id Order_no
Name Ordercredate
Addr1 Order_status
Addr2 Shipment_date
Cust_city Challan
Pincode
Getinvoice()
Ordetdetail Material
Orderno
Materialqty Materialcode
Materialvalue Plantcode
Stckqty
Type Bankname
Expirydate Bankid
validating validating
GRN
Recivedqty
Damaged
Rejected
Description()
Log In
Validate
Tracks order
Places order
Makes Payment
Dispatch Order
Send order details
Log Out
Send GNR
Request Material
Get
Materials
Ship Order
Tracks Order
Input Screen
Login Form
Main Form
Category Form
Product Form
Supplier Form
Search Form
Customer Order Form
After insufficient stock form
Supplier order form
Table specifications
UID_PASS (Login Table)
Column Name Data Type Size Description
Category
Product table
Testing principles
Before applying methods to design effective test cases, a software engineer must
understand the basic principle that guide software testing:
Testing should being “in the small” and progress toward testing “in the
large”.
A rich variety of test case design methods have evolved for software. These
methods provide the developer with a systematic approach to testing. More
important, methods provide a mechanism that can help to ensure the
completeness of tests and provide the highest likelihood for uncovering errors in
software.
Any engineered product (and most other things) can be tested in one of
two ways:
Knowing the specified function that a product has been designed to perform,
tests can be conducted that demonstrate each function is fully operational
While at the same time searching for errors in each function; (2) knowing the
internal
UNIT TESTING
INTEGRATION TESTING
DATABASE TESTING
RECOVERY TESTING
FUNCTIONALITY TESTING
SMOKE TEST
SANITY TEST
COMPATIBILITY TESTING
LOAD TESTING
SYSTEM TESTING
PERFORMANCE TESTING
USER ACCEPTANCE TESTING
White box testing
Sometimes called glass-box testing is a test case design method that uses the
control structure of the procedural design to derive test cases. Using white-box
testing methods, the software engineer can derive test cases that (1) guarantee
that all independent paths within a module have been exercised at least once, (2)
exercise all logical decisions on their true and false sides, (3) execute all loops at
their boundaries and within their operational bounds, and (4) exercise internal data
structures to ensure their validity.
White-box testing of software is predicated on close examination of procedural
detail. Providing test cases that exercise specific sets of conditions and/or loops
tests logical paths through the software. The “status of the program” may be
examined at various points to determine if the expected or asserted status
corresponds to the actual status. Basis path testing is a white-box testing technique
first proposed by Tom McCabe. The basis path method enables the test case
designer to derive a logical complexity measure of a procedural design and use this
measure as a guide for defining a basis set of execution paths. Test cases derived
to exercise the basis set are guaranteed to execute every statement in the program
at least one time during testing.
In this system, the system was tested for the calculation matters were the
data provided for giving the right output or not. If wrong data was provided then
what it is throwing error or accepting.
Black box testing
Properly accepted and output is correctly produced and that the integrity of
external information is maintained. A black-box test examines some fundamental
aspect of a system with a little regard for the internal logical structure of the
software. Black-box testing attempts to find errors in the following categories:
Black box testing for this system was done to check the internal testing i.e,
the system is working properly in each case or no. What kind of errors are there in
database design.
Testing Process
The testing process can be shown as:
Test Case
Specification
Yes
Test Case
Execution
No
Test Report
Menu Tree
Main Page
Calcula
tor
Transaction Toolbar System
Screen Customer Requirements
About
Reports
Status Notepad
Bar Plant
Project Code
report
Exit
Material
State
Admin authority
2. So all customer databases and material database and all master tables are to
be handled by the admin person only.
3. These screens are detailed screens so no specific description is needed for the
same.
Proposed
Enhancements
Future Scope:
The scope of the project includes that what all future enhancements can be done
in this system to make it more feasible to use
Manages contacts
Manages accounts
Manages opportunities
3. Graphs could have been added in order to get the records more clearly.
Conclusion
While developing the system a conscious effort has been made to create and
develop a software package, making use of available tools, techniques and
resources – that would generate a proper System
While making the system, an eye has been kept on making it as user-friendly,
as cost-effective and as flexible as possible. As such one may hope that the system
will be acceptable to any user and will adequately meet his/her needs.
BOOKS REFERRED
By Gary J. Bronson
WEB LINK
http://www.dreamincode.net
http://www.a1vbcode.com
Code design
Login
Test Cases