Chapter 1: Introduction:

1.1 Background:
Sales and inventory management is the new rising topic all around our country Nepal
as it is a highly developing country in comparison to other countries. In day to day
market it is very hard to keep records of the number of items sold and the transactions
made while selling those goods. It is specially the need of market and business
companies to keep records of large sales made on separate industries in day to day basis
for long lasting time.

Limitation of the Existing System

 Existing system was manual.

 Time consuming as data entry which include calculations took lot of time.
 Searching was very complex as there could be 100’s of entry every year.
 The proposed system is expected to be faster than the existing system.

1.2 Objectives:
The basic goal of this project is to design the system that manages the daily as well as
long term sales record.

1.2.1 Project (Specific)Objectives:

The basic objective of the project is:
 To build a simple sales and inventory management system according
to market requirement using Integrated Development Environment
(IDE) in visual studio.

1.2.2 Academic (General) Objectives:

In terms of academic level this project helps us to learn the various
terminologies and technology in the field of computational technology. The
major academic objective of the project has the following credentials:

 To help us get an insight into concept of user interface design and

database configuration.
 To understand the basic of Interface Development Environment.
 To help us analyse the various types of recent requirement.
 To learn technics of interface design and database management.

1
1.3 Features:
Inventory management software is made up of several key components, all working
together to create a cohesive inventory for many organizations' systems. These features
include:

 Single Login Panel

Single type of users in TSRM
# Admin
Above Admin users can able to login by the same login panel.

 Supplier of Product management

Should inventory reach a specific threshold, a company's inventory
management system can be programmed to tell managers to reorder that
product. This helps companies avoid running out of products or tying up too
much capital in inventory.

 Service Management
Companies that are primarily service-oriented rather than product-oriented can
use inventory management software to track the cost of the materials they use
to provide services, such as cleaning supplies. This way, they can attach prices
to their services that reflect the total cost of performing them

 Update Data
Up-to-date, real-time data on inventory conditions and levels is another
advantage inventory management software gives companies. Company
executives can usually access the software through a laptop or PC to check
current inventory numbers. This automatic updating of inventory records allows
businesses to make informed decisions.

 Inventory Control
Improve inventory control through automatically updated stock levels whenever
sales and purchases are made.

 Sales Report
Access accurate sales reports that offer insights for better business decisions, all
in real time.

 Inventory Optimization
Inventory allows you to have the right amount of stock at the right time: Never
over stock or under stock your inventory again.

 Purchasing
Create purchase orders that update inventory levels automatically while
ensuring data accuracy.

 Expiration Date
Assign expiration dates to items during or immediately after receiving items and
more.

2
  Multi-level Categories
Adding as many categories as you require, categories just as easily, providing
additional inventory item sorting capabilities.

 Report
Common reports come pre-configured and ready to go as standard. Including
interactive reports for business analysis. Sales, Purchase Report, Purchase
Stocks etc.

 Print Report
Once a report is generated it can be printed or saved to pdf formats ready.

 Supplier Information
Easy to add supplier and Company details for purchase product.

 Customer Information
Add Customer with Company for Sales product.

 Stock Notification
If stock products available less than 10%, then it notify to admin for purchase
of this product.

 Stock availability
Show how many product are available in stock with product name.

8.2 Benefits:
Benefit of a good Inventory Management System:
 A good inventory management strategy improves the accuracy of inventory
orders.
 A good inventory management strategy leads to a more organized inventory.
 A good inventory management strategy helps save time and money.
 A good inventory management strategy increases efficiency and productivity.
 A good inventory management strategy keeps your customers coming back.
 Inventory management is primarily about specifying the shape and percentage
of stocked goods.
 Inventory management leads to optimal inventory levels.
 Inventory management can also help companies improve cash flows.
 Management of the inventories, with the primary objective of determining stock
levels within the physical distribution system, functions to balance the need for
product availability against the need for minimizing stock holding and handling
costs.

3
 Chapter 2:Technologies And Literature Review:
2.1 Literature Review:
Sales And Inventory management software (SIMS) is a computer-based system for
tracking inventory levels, orders, sales and deliveries. It can also be used in
the manufacturing industry to create a work order, bill of materials and other
production-related documents. Companies use inventory management software to
avoid product overstock and outages. It is a tool for organizing inventory data that
before was generally stored in hard-copy form or in spreadsheets. A good Inventory are
needed the following area:

 Inventory is the raw materials, component parts, work-in-process, or finished

products that are held at a location in the supply chain.
 Replacement parts, tools, & supplies, Goods-in-transit to warehouses or
customers.
 Ensure inventory processes are in compliance with decision.
 Define and apply appropriate procedures for collecting, processing,
communicating, and archiving inventory data & information.
 Coordinate with relevant ministries, agencies, and other organizations.
 Provide inventory reports regularly.
 Ensure the quality of inventory data.
 Make arrangements to collect data from statistical agencies, companies,
industry associations, etc.
 A key category is one that is prioritized within the inventory system.
 A key category may also be determined through a qualitative assessment.
 Make inventory information available to stakeholders and respond to
information requests.
 Archive all documentation and results.
 Continuous improvement feedback.

4
2.2 About Technologies Used:
Sales And Inventory Management System Application: As our Application is an
offline online Windows form Application, so we have used offline technologies for the
development of both front end and back end. Below listing the technologies:

2.2.1 Visual Studio (IDE):

Visual Studio .NET is a Microsoft-integrated development environment (IDE) that can
be used for developing consoles, graphical user interfaces (GUIs), Windows Forms,
Web services and Web applications.

Visual Studio is used to write native code and managed code supported by Microsoft
Windows, Windows Mobile, Windows CE, .NET Framework, .NET Compact
Framework and Microsoft Silverlight. Visual Studio .NET’s code editor supports
IntelliSense and code refactoring, while the Visual Studio .NET integrated debugger
supports both source and machine-level debugging. Visual Studio .NET includes other
built-in tools, like a form designer, which is useful when building GUI applications; a
Web designer that creates dynamic Web pages; a class designer that is used to create
custom libraries, and a schema designer for database support.

2.2.2 CSharp (C#):

C#.Net is a Integrated Development Environment used for various software
development. C# links with different database server and uses it as back end developing
environment for software development. C# is multiplatform developing tool.

2.2.3 MSSQL:
MSSQL is a standard query language used as server to link database engine with other
application software as well as create database, queries etc.

2.2.4 Crystal Reports:

Crystal reports are report generation software which can be used for report generation
individually as well as can be linked to other integrated development environment
software. For example, Visual Studio, ASP.

5
 Chapter 3: Methodologies:
3.1 The Chosen Methodology:
Iterative and Incremental Model of software development model been used while
development SIMS, that is because I wish to develop this system by problem solving
mode and deliver solution as per requirement. Nowadays, Iterative and incremental is
the most popular Methodology for Software development.

Figure 3.0: Iterative and incremental Process

There are many differences in iterative and incremental development model when
compared to traditional models:

 The iterative and incremental model emphasizes on the fact that entire team
should be a tightly integrated unit. This includes the developers, quality
assurance, project management, and the customer.
 Frequent communication is one of the key factors that makes this integration
possible. Therefore, daily meetings are held in order to determine the day's work
and dependencies.
 Deliveries are short-term. Usually a delivery cycle ranges from one week to four
weeks. These are commonly known as sprints.
 Iterative and incremental project teams follow open communication techniques
and tools which enable the team members (including the customer) to express
their views and feedback openly and quickly.
 These comments are then taken into consideration when shaping the
requirements and implementation of the software.

6
3.2 The Iterative and incremental Methodologies:
Iterative and incremental software development refers to a group of software
development methodologies based on iterative development, where requirements and
solutions evolve via collaboration between self-organizing cross-functional teams. The
term was coined in the year 2016 when the Iterative and incremental Manifesto started
to get mostly used for software development.

Iterative and incremental software development uses iterative development as a basis

but advocates a lighter and more people-centric viewpoint than traditional approaches.
Iterative and incremental processes fundamentally incorporate iteration and the
continuous feedback that it provides to successively refine and deliver a software
system.

There are many iterative and incremental methodologies, including:

 Dynamic systems development method (DSDM)

7
3.3 Project Plan & Management:

3.3.1 Project Timeline:

Figure 3.1: Gantt Chart showing project timeline:

3.3.2 Roles and Responsibilities:

Role Responsibility Team Member
Feasibility Analysis & Maheshwor Shrestha,
Requirement Gathering Niraj Chandi,
Project Development Analysis & Design Sujita Sapkota,
Implementation Anupam Pandey

Testing Maheshwor Shrestha,

Project Report & Documentation Niraj Chandi,
Testing User Manual Sujita Sapkota,
Anupam Pandey

8
 Chapter 4. System Study And Analysis:
4.1 System Analysis :
System Analysis refers into the process of examining a situation with the intent of
improving it through better procedures and methods. System Analysis is the process of
planning a new System to either replace or complement an existing system. But before
any planning is done the old system must be thoroughly understood and the
requirements determined. System Analysis, is therefore, the process of gathering and
interpreting facts, diagnosing problems and using the information to re-comment
improvements in the System. Or in other words, System Analysis means a detailed
explanation or description. Before computerized a system under consideration, it has to
be analyzed. We need to study how it functions currently, what are the problems, and
what are the requirements that the system should meet.

System Analysis have 4 important aspects.

1. Scope
2. Cost
3. Time
4. Quality

Figure 4.1: Analysis Aspect

9
System Analysis is conducted with the following objectives in mind:

 Identify the customer’s need.

 Evaluate the system concept for feasibility.
 Perform economic and technical analysis.
 Allocate functions to hardware, software people, database and other system
elements.
 Establish cost and schedule constraints.
 Create a system definition that forms the foundation for all the subsequent
engineering work.

4.2 Feasibility Study:

All projects are feasible given unlimited resources and infinite time. Unfortunately, the
development of computer-based system in many cases is more likely to be plagued by
scarcity of resources and delivery date. Hence, we have made use the concept of
reusability that is what Object Oriented Programming (OOPS) is all about.

The feasibility report of the project holds the advantages and flexibility of the project.
This is divided into three sections:

 Economic Feasibility
 Technical Feasibility
 Behavoral Feasibility

4.2.3 Economic Feasibility:

Economic analysis is the most frequently used method for evaluating the
effectiveness of the candidate system. More commonly known as cost/benefit
analysis, the procedure is to be determining the benefits and savings that are
expected from a candidate and compare them with costs. If benefits outweigh
costs, then the decision is made to design and implement the system.

A systems financial benefit must exceed the cost of developing that system. i.e. a
new system being developed should be a good investment for the organization.
Economic feasibility considers the following

 The cost to conduct a full system investigation.

 The cost of hardware and software for the class of application.
 The benefits in the form of reduced cost or fewer costly errors.
 The cost if nothing changes (i.e. The proposed system is not developed).

10
The “SALES ANDINVENTORY MANAGMENT” is economically feasible
because:

 The system requires very less time factors.

 The system will provide fast and efficient automated environment instead
of slow and error prone manual system, thus reducing both time and man
power spent in running the system.
 The system will have GUI interface and very less user-training is required
to learn it.
 The system will provide service to view various information for proper
managerial decision making.

4.2.2 Technical Feasibility:

Technical feasibility centers around the existing computer system (Hardware
and Software) and to what extend it support the proposed addition. For example,
if the current computer is operating at 80 percent capacity - an arbitrary ceiling
- then running another application could overload the system or require
additional Hardware. This involves financial considerations to accommodate
technical enhancements. If the budget is a serious constraint, then the project is
judged not feasible. In this project, all the necessary cautions have been taken
care to make it technically feasible. Using key the display of text/object is very
fast. Also, the tools, operating system and programming language used in this
localization process is compatible with the existing one.

4.2.3 Behavioral Feasibility:

People are inherently resistant to change, and computers have been known to
facilitate change. An estimate should be made of how strong a reaction the user
staff is likely to have toward the development of a computerized system.
Therefore, it is understandable that the introduction of a candidate system
requires special efforts to educate and train the staff. The software that is being
developed is user friendly and easy to learn. In this way, the developed software
is truly efficient and can work on any circumstances, tradition, locales.

Behavioral study strives on ensuring that the equilibrium of the organization

and status quo in the organization are nor disturbed and changes are readily
accepted by the users.

4.2.4 Schedule feasibility :

This project “Devanagari Character Recognition” takes a lot of time and
practices. Typically, this means estimating how long the system will take to
develop. Schedule feasibility is a measure of how reasonable the project
timetable is. Based on the technical expertise and it is assumed to complete
within estimated deadline and finally it is completed in estimated schedule.

11
4.3 Requirement Analysis:

4.3.1 Problem Identification:

After long term research about the problems that the users and the recent market
has been facing regarding the maintenance of sales and inventory we have come
up with list of some problems:

 The manual system used today is very time consuming and tangling.
 The calculation of huge amount of sales on inventory is a very hard thing
to do.
 Some software does calculate it, but can’t facilitate the user with the
facility of storing the data including sale and inventory for long term.
 Even if some software might store the data but its retrieval is very hard.
 Not only retrieval but the modification of the data once stored is not also
possible in the current system.
 Large number of errors occur if the work is man handled.
 Maintaining large amount of data manually can cause many errors.
 Recent system available are not totally protected so, data loss can be
major problem.

4.3.2 Performance requirements:

The following performance characteristics should be taken care of while
developing the system:

 User friendliness: The system should be easy to learn and understand

so that new user can also use the system effectively, without any
difficulty.
 User satisfaction: The system should meet user expectations.
 Response time: The response time of all the operations should be low.
This can be made possible by careful programming.
 Error handling: Response to user errors and the undesired situations
should be taken care of to ensure that the system operates without
halting.
 Safety: The system should be able to avoid or tackle catastrophic
behavior.
 Robustness: The system should recover from undesired events without
human intervention.

12
4.3.3 System Requirements:

4.3.3.1 Software development requirement:

• Visual Studio 2012
• C# .NET framework
• Adobe Photoshop
• MSSQL
• SQL sever management studio

4.3.3.2 Hardware requirement:

• Pentium III processor
• 256 MB RAM
• 20GB HARD DISK

4.3.4 Acceptance criteria:

The following acceptance criteria were established for the evaluation of the new
system:

 User friendliness:- The system should meet user needs and should be
easy to learn and use.
 Modularity:- The system should have relatively independent and single
function parts .
 Maintainability:- The system should be such that future maintenance
and enhancements times and efforts are reduced.
 Timeliness:- The system should operate well under normal, peak and
recovery conditions.
 The system developed should be accurate and hence reliable i.e. The
error rate should be minimized and the outputs should be consistent and
correct.
 Both the execution time and response time should be negligibly low.
 The system should be efficient i.e. the resources utilization should be
optimal.
 The system should have scope to force modifications and enhancements
i.e. it should be able to cope with the changes in future technology.

13
 Chapter 5: System Design:
5.1 SIMS Design
Systems design is the process of defining the architecture, components, modules,
interfaces, and data for a system to satisfy specified requirements. Systems design could
be seen as the application of systems theory to product development. There is some
overlap with the disciplines of systems analysis, systems architecture and systems
engineering.

5.1.1 Design goals:

The following goals were kept in mind while designing the system:
 Make system user-friendly. This was necessary so that system could
be used efficiently and system could act as catalyst in achieving
objectives.
 Make system compatible i.e. It should fit in the total integrated system.
Future maintenance and enhancement must be less.
 Make the system compatible so that it could integrate other modules
of system into itself.
 Make the system reliable, understandable and cost-effective

14
5.1.2 SIMS System Architecture:
Sales And Inventory Management System (SIMS) architecture model:

Figure5.1.2 : SIMS Architecture

15
5.2 Database Design
Database design is the process of producing a detailed data model of a database. This
logical data model contains all the needed logical and physical design choices and
physical storage parameters needed to generate a design in a data definition language,
which can then be used to create a database. A fully attributed data model contains
detailed attributes for each entity.

5.2.1 SIMS List of DataTable:

 registration
 units
 purchase_name
 purchase_master
 order_item
 order_user
 stock
 delear_info

16
5.2.2 SIMS ER Diagram

Figure 5.2.2: SIMS ER Diagram:

17
5.2.3 SIMS Use Case Diagram:

Figure 5.2.3: SIMS Use Case Diagram:

18
5.2.4 SIMS Data Flow Diagram:

Figure 5.2.4: SIMS Data Flow Diagram:

19
 Chapter 6: Testing and Debugging:
6.1 Testing:
Software testing is a critical element of the ultimate review of specification design and
coding. Testing of software leads to the uncovering of errors in the software functional
and performance requirements are met. Testing also provides a good indication of
software reliability and software quality as a whole. The result of different phases of
testing are evaluated and then compared with the expected results. If the errors are
uncovered they are debugged and corrected. A strategy approach to software testing
has the generic characteristics:
 Testing begins at the module level and works “outwards” towards the
integration of the entire computer based system.
 Different testing techniques are appropriate at different points of time.
 Testing and debugging are different activities, but debugging must be
accommodated in the testing strategy.

6.1.1 Goals and Objectives:

“Testing is a process of executing a program with the intent of finding an error”.
A good test case is one that has a probability of finding an as yet undiscovered
error. A successful test is one that uncovers an as yet undiscovered error. Our
Objective is to design test processes that systematically uncover different classes
of errors and do so with minimum amount of time and effort.

6.1.2 Statement of scope:

A description of the scope of the software testing is developed. All the features to
be tested are noted as follows. The basic principles that guides software testing
are:

 All test cases should be traceable top customer requirements. The most
severe defects from the customer’s point of view are those that cause the
program to fail to meet its requirements.
 Test case should be planned long before testing begins. Testing plan can
begin as soon as the requirement model is complete. Detailed definition of
the test cases can begin as soon as the design is solidified. Therefore, the
entire test can be planned before any code has been generated.
 Testing should begin “in the small” and progress towards “in the large”.
The first test planned and executed generally focus on the individual
modules. As testing progresses testing shifts focus in an attempt to find
errors in integrating clusters of modules and ultimately in the entire system

20
 6.1.3 Types of testing:
Some of the basic types of testing are as follows:

 Unit Testing:
 Functional Test:
 Stress Test:
 Structure Test:
 Integration Testing:

Among all these different types of testing the method that are followed in our
project are integration testing and unit testing.

6.1.3.1 Integration Testing:

“If they all work individually, they should work when we put them together.”
The problem of course is “putting them together “. This can be done in two
ways:

6.1.3.1.1 Top down integration:

Modules are integrated by moving downwards through the control hierarchy,
beginning with main control module are incorporated into the structure in either
a depth first or breadth first manner.

6.1.3.1.2 Bottom up integration:

It begins with construction and testing with atomic modules i.e. modules at the
lowest level of the program structure. Because modules are integrated from the
bottom up, processing required for the modules subordinate to a given level is
always available and the need of stubs is eliminated.

6.2 Debugging:
Debugging occurs as a consequence of successful testing i.e. when a test case uncovers
an error, debugging is the process that results in identifying the location of error and
the removal of error. The poorly understood mental process that connects a symptom
to cause is debugging.

This process will always have one of the two outcomes:

 The cause will be found, corrected and then removed.
 The cause will not be found. In the latter case the person performing debugging
may suspect a cause, design a test case to help validate his suspicion, and then
work towards the correction of errors in the interactive fashion.

Following three approaches of debugging were used:

 Debugging by Induction
 Debugging by Deduction
 Backtracking

21
 Chapter 7: Conclusion:
7.1 Limitation:
Following are some minor limitations we have faced:
 Single User panel.
 If sale any product at first add customer for sale Product.
 If purchase any stock at first add supplier for purchase stock.
 The Sales And Inventory Management System (SIMS) software is offline
based.
 Only Cash on Delivery.

7.2 Future work

Will fix all limitation. Then make the system stable and bug free.SIMS has inspired us
to do something by own that’s why we will try to do something commercial work like
as SIMS. We will try to expose IMS every inventory for solve the problem between
admin and supplier with customers.

Now SIMS lunched with very minimum requirement but we will improve the feature
day by day and make an idea software for Sales And Inventory Management System.

7.3 Conclusion:
After the study, we can came to a conclusion that, effectiveness of inventory
management should improve in all the aspects, hence the industry can still strengthen
its position by looking into the following:
 The inventory should be fast moving so that inventory cost can be reduced.
 The finished goods have to be dispatched in feasible time as soon as
manufacturing is completed.
 Optimum order quantity should be maintained, hence cost can be minimized.
 Proper inventory control techniques are employed by the inventory control
organization within the framework of one of the basic models.

Inventory management is the practice of planning directing and controlling of inventory

so that it contributes to the business profitability. Inventory management can help
business be more profitable by lowering their costs of goods sold by increasing sales.
Inventory managers have to provide for stocks, when needed, utilize available storage
space efficiencies so that stocks do not exceed the storage space available.
Some minor functional problem may occur during operation, but it will not have any
minimum effect on kernel part of the system. If anyone report us that bug then we will
fixed the bug as soon as possible.

22
 Chapter 8: References:
8.1 References
8.1.1 Websites
 https://en.wikipedia.org/wiki/Inventory_management_software
 http://www.tutorialspoint.com/
 http://www.w3schools.com/
 http://stackoverflow.com/

8.1.2 Books:
 Programming with JAVA
E Balagurusamy
 Software Engineering
Ian Sommerville

23
 Chapter 9: Output Screenshots:
9.1: Running the program:
9.1.1: Login Form:

This is the first screen that appears while we run the program where user should
give correct user name and address to get into another form.

24
9.1.2: Main Form:

This is the main(Parent) form of the whole software which only occurs after the
user gives correct set of user name and password among the ones in the
database.

25
 9.1.3: User Entry:

This window occurs when the user clicks on the user data logo in the main form.

26
9.1.4: Product Units:

Here the user(admin) can update the units of the products. Any units suitable
for each products can easily be inserted here.

27
9.1.5 Add Products Name:

Here, the user can insert the desired list of products and select the units suitable for
those products.

28
9.1.6 Dealers:

Here, the user can insert the details of the dealers from where the products are
imported.

29
9.1.7 Purchase Product:

Here the details of the purchased product from the dealers is inserted and the
stock is updated automatically.

30
CHAPTER 1: INTRODUCTION: ........................................................................................................ 1
1.1 BACKGROUND: ............................................................................................................................... 1
1.2 OBJECTIVES: ................................................................................................................................... 1
1.2.1 Project (Specific)Objectives: ................................................................................................. 1
1.2.2 Academic (General) Objectives: ............................................................................................ 1
1.3 FEATURES:...................................................................................................................................... 2
8.2 BENEFITS: ....................................................................................................................................... 3
CHAPTER 2:TECHNOLOGIES AND LITERATURE REVIEW: .................................................. 4
2.1 LITERATURE REVIEW: .................................................................................................................... 4
2.2 ABOUT TECHNOLOGIES USED: ....................................................................................................... 5
2.2.1 Visual Studio (IDE): .............................................................................................................. 5
2.2.2 CSharp (C#): ......................................................................................................................... 5
2.2.3 MSSQL:.................................................................................................................................. 5
2.2.4 Crystal Reports: ..................................................................................................................... 5
CHAPTER 3: METHODOLOGIES: ................................................................................................... 6
3.1 THE CHOSEN METHODOLOGY: ....................................................................................................... 6
3.2 THE ITERATIVE AND INCREMENTAL METHODOLOGIES: .................................................................. 7
3.3 PROJECT PLAN & MANAGEMENT: .................................................................................................. 8
3.3.1 Project Timeline: ................................................................................................................... 8
3.3.2 Roles and Responsibilities: .................................................................................................... 8
CHAPTER 4. SYSTEM STUDY AND ANALYSIS: ........................................................................... 9
4.1 SYSTEM ANALYSIS : ....................................................................................................................... 9
4.2 FEASIBILITY STUDY:..................................................................................................................... 10
4.2.3 Economic Feasibility: .......................................................................................................... 10
4.2.2 Technical Feasibility: .......................................................................................................... 11
4.2.3 Behavioral Feasibility: ........................................................................................................ 11
4.2.4 Schedule feasibility : ............................................................................................................ 11
4.3 REQUIREMENT ANALYSIS: ............................................................................................................ 12
4.3.1 Problem Identification: ........................................................................................................ 12
4.3.2 Performance requirements: ................................................................................................. 12
4.3.3 System Requirements: .......................................................................................................... 13
4.3.4 Acceptance criteria: ............................................................................................................. 13
CHAPTER 5: SYSTEM DESIGN: ..................................................................................................... 14
5.1 SIMS DESIGN ............................................................................................................................... 14
5.1.1 Design goals: ....................................................................................................................... 14
5.1.2 SIMS System Architecture: .................................................................................................. 15
5.2 DATABASE DESIGN .................................................................................................................... 16
5.2.1 SIMS List of DataTable: ...................................................................................................... 16
5.2.2 SIMS ER Diagram ............................................................................................................... 17
5.2.3 SIMS Use Case Diagram: .................................................................................................... 18
5.2.4 SIMS Data Flow Diagram: .................................................................................................. 19
CHAPTER 6: TESTING AND DEBUGGING: ................................................................................. 20
6.1 TESTING: ...................................................................................................................................... 20
6.1.1 Goals and Objectives: .......................................................................................................... 20
6.1.2 Statement of scope: .............................................................................................................. 20
6.1.3 Types of testing: ................................................................................................................... 21
6.2 DEBUGGING: ................................................................................................................................. 21
CHAPTER 7: CONCLUSION: ........................................................................................................... 22
7.1 LIMITATION: ................................................................................................................................. 22
7.2 FUTURE WORK .............................................................................................................................. 22
7.3 CONCLUSION: ............................................................................................................................... 22
CHAPTER 8: REFERENCES: ........................................................................................................... 23

31
 8.1 REFERENCES................................................................................................................................. 23
8.1.1 Websites ............................................................................................................................... 23
8.1.2 Books: .................................................................................................................................. 23
CHAPTER 9: OUTPUT SCREENSHOTS: ....................................................................................... 24
9.1: RUNNING THE PROGRAM: ............................................................................................................ 24
9.1.1: Login Form: ....................................................................................................................... 24
9.1.2: Main Form: ........................................................................................................................ 25
9.1.3: User Entry: ......................................................................................................................... 26
9.1.4: Product Units: .................................................................................................................... 27
9.1.5 Add Products Name: ............................................................................................................ 28
9.1.6 Dealers: ............................................................................................................................... 29
9.1.7 Purchase Product: ............................................................................................................... 30

32