Inventory Managment a final year projet for ug

1. INVENTORY SYSTEM
A Project Report
Submitted in partial fulfillment for the degree of
B.Sc., (Computer Science)
By
B.SAI PRAKASH
[Reg.No:2888834]
Under the guidance of
Mrs. M.CHANDRAKALA, M.C.A., M.Phil,
(Head of the Department of Computer Science)
Sri Aravindar Arts and Science College
DEPARTMENT OF COMPUTER SCIENCE
SRI ARAVINDAR ARTS AND SCIENCE COLLEGE
AKASAMPET, VANUR T.K, VILLUPURAM – 605111
MARCH 2011

2. ACKNOWLEDGEMENT
We wish to express our profound gratitude to
Dr.R.Ramalingam M.Sc, M.Phil, Ph.d, B.Ed Principal, Sri Aravindar Arts & Science
College, Sedarapet for his kind consent to carry out this project. We would also like to
thank our Vice Principal Mr.J.Arokianathan M.Sc, M.Phil for his co-operation and
support.
We are thankful to Mrs.M.Chandrakala M.C.A, M.Phil, Head of the Department
Computer Science, Sri Aravindar Arts & Science College, Sedarapet, who is also our
project guide for her encouragement and valuable suggestions throughout study phase,
implementation phase and preparation phase.
We also thank the teaching staff of the department of Computer Science, of Sri
Aravindar Arts & Science, Sedarapet who have been instrumental in shaping our careers
in computer science.
We express our deep sense of gratitude to Mr. Anandane, Senior manager of
E.D.P, Pondicherry who provided a chance to expose our knowledge in the field of
Computer Science by offering the project titled “INVENTORY SYSTEM “in their
organization. We also thank Mrs. Jayalakshmi.B, assisstant programmer for providing
us the technical assistance and also the necessary information to do this project.
Finally, we would like to thank our parents and those who have contributed directly
and indirectly for successful completion of this project.
B.SAIPRAKASH

3. BONAFIDE CERTIFICATE
This is to certify that the Project entitled
INVENTORY SYSTEM MANAGEMENT
Being Submitted to the Thiruvalluvar University, Vellore
By
B.SAI PRAKASH
[Reg.No:2888834]
For The Partial fulfillment for the award of Degree of
B.Sc., (Computer Science)
Is a bonafide record of Work Carried out by them
Under My Guidance and Supervision
Head of the Department Internal Guide
Submitted for the Viva-voce Examination held on………………
Examiners:
1.
2.

4. CONTENTS
CHAPTER PAGE
1. INTRODUCTION
1.1About the Organization 1
1.2 Problem Definition 2
1.3 System Justification 3
2. SYSTEM STUDY AND ANALYSIS
2.1 Existing System 4
2.2 Drawbacks of Existing System 5
2.3 Proposed System 5
2.4 Requirement Specification 6
3 SYSTEM DESIGN
3.1 Architectural Design 12
3.1.1 Data Flow Diagram 13
3.1.2 System Flow Chart 15
3.2 Detailed Design
3.2.1 Output Design 16
3.2.2 Input Design 17
3.2.3 Database Design 17
3.2.4 Program Design 18
4. SYSTEM IMPLEMENTATION AND TESTING
4.1 Implementation 19
4.1.1 Change Over 19
4.1.2 Parallel running 19
4.2 Sample Coding 20
4.3 System Testing 22
4.3.1 Black Box Testing 22
4.3.2 White Box Testing 22
5. CONCLUSION 26

5. CHAPTER PAGE
BIBLIOGRAPHY 27
APPENDICES
A. File Structures 28
B. Screenshots

6. INTRODUCTION

7. SYNOPSIS
The project Inventory Management System is developed for Anglo French Textiles,
Pondicherry.This project will take care of all related activities in the departments of
Cotton, Weaving and Spinning. Cotton is the main raw material involved. Nearly 30% of
the expenditure is spent for the purchase of raw material. The project enables to reduce
manpower and provides a clear picture of the Raw material stock available. The project
gives a detailed report of the total stock maintained of cotton and yarn. It also provides a
detailed report of the day to day usage of cotton.
The project involves two major modules:
 Cotton Inventory
 Yarn Inventory.
The Cotton Inventory module involves four sub modules:
 Purchase
 Add New Item
 Issues
 Daily Expenses.
 View
These sub modules enable to maintain the cotton day book and cotton consumption. It
also enables to generate periodical and monthly statement regarding
Yarn inventory Management:
This module enables the stock maintains of yarn. Yarn day book is maintained
which is used for the purpose of computing Financial accounting statement which
provides a detailed picture of the company’s financial status. The existing system
involves manual maintenance of accounting. The proposed system enables to maintain
accuracy and enables easy generation of reports.

8. ABOUT THE ORGANISATION:
The Anglo-French Textiles (AFT) was started in 1898 at Pondicherry and
from then on a Saga of excellence in cotton fabrics and their export began. At a time a
time when India was exporting textiles, Anglo-French textiles (AFT) had begun to make
its presence felt internationally as exports. Rapid strides were made. Millions and
millions of meters of cotton fabrics were exported to customers in UK, France, Germany,
Italy, Switzerland, Denmark, Dubai, Oman and countries of Africa, Honk Kong and
South Korea.
Anglo-French Textiles is divided into three units such as A, B and C units,
which were started in1878, 1970 and 1974 respectively. The ‘A’ and ‘B’ units are
situated are situated in Mudailarpet the heart of the town and’C’ unit is situated in
Iyyankutipalayam,10 Km from the town.’A’unit is also termed as “Old Mill”,’B’and ‘C’
units as” New Mill” and “Canvas Mill” respectively.
There are approximately 5000 workers, 700 labourers and 560 staff working in
this mill.
The raw material used to produce cloth is cotton. The sequence of operation
carried out to produce cloth is a carding, spinning, weaving preparation, weaving,
warehouse, processing and godown.

9. 1.2 PROBLEM DEFINITION:
“INVENTORY SYSTEM” for Anglo French Textiles is an application program to
implement the proceedings that are undertaken during production stage.
The administrator is the only person authorized to use the application. The project
enables to provide complete details regarding the raw materials used in the factory.
Cotton and yarn are the main raw materials used in the factory. Raw material details such
as name of the supplier, address of the supplier, quality of material, quantity bought and
amount due. The administrator can also maintain the sales details such as customer name,
addresss, quantity, item name and amount. The view module enables the administrator to
have a clear idea of stock in hand. It gives the administrator clear picture of the daily
expenditure of stock (i.e.) how much of stock has been taken for production and the
remaining stock in hand.
The project also enables the administrator to know when to reorder materials. The reorder
module gives a detailed report of the materials to be reordered. This enables to maintain a
balance between stock and production. The project relieves the user from physical
inspection of stock. It gives a detailed report regarding raw material along with the
quality details of the material and quantity available.

10. 1.3 SYSTEM JUSTIFICATION
The aim of this system is to computerize the Inventory system carried out in the Textile
industry. All details regarding the customers as well as the material details are stored. It
also aims in providing computer billing.
The system is designed in such a way it provides faster access, more efficiency, cost
effective and effortless. It satisfies user needs and occupies less storage thus helping
faster transaction.

11. SYSTEM STUDY AND
ANALYSIS

12. 2. SYSTEM STUDY AND ANALYSIS
This phase is a detailed appraisal of the existing system. The appraisal includes
finding out how the system works and what it does. It also includes finding out in detail
what are the problems faced by the system.
The first step towards developing a system is to study the existing system carefully
diagnose the problem, analyze and design the model of the system.
2.1 EXISTING SYSTEM:
In the existing system the details about the Inventory System like material details,
customer details are maintained in FoxPro and also it takes much time for preparing
reports like Daily Expense, Purchase details.
In the existing system accuracy, efficiency and speed cannot be expected. It is very
difficult to furnish the reports required by the management immediately. It is not easy to
calculate the total contracts for the particular period. Maintaining the records are very
difficult, the existing system does not permit online validation and updating. Since there
is no GUI, there is a less user system interaction and also it is very difficult to novice
users.
The new system is designed to overcome all difficulties of an existing system.
The new system has been proposed to have efficiency, accuracy and speed. Quick and
timely services are also provided. The reports required by the managements are also
furnished immediately. Hence the present system provides online validation and
updating.

13. 2.2 DRAWBACKS OF THE EXISTING SYSTEM:
1. Consumes more time and effort for updating
2. Reports are not in attractive manner
3. Efficiency and accuracy cannot be expected
4. Quick and timely services are not provided
5. Slow processing speed
6. Readymade data retrieval is difficult.
2.3 PROPOSED SYSTEM:
To overcome the above mentioned problems in the existing system and to create a
user-friendly system with advanced manipulation techniques, it has been proposed to
develop a new system.
The proposed system should be developed keeping in view the factors like
efficiency, accuracy, speed and to furnish the reports easily. The proposed system should
provide online validation and updation.It should also be capable of storing large amount
of data for many years. The proposed system must be menu oriented and should provide
user-friendly environment by including GUI tools.

14. 2.4 SYSTEM REQUIREMENT SPECIFICATION
HARDWARE SPECIFICATION:
Processor : Pentium IV
Memory size : 512MB RAM
Storage : 80 GB Hard Disk
Display : EGA/VGA Color Monitor
600x800 Pixels Resolution
High Color (16bit)
Key Board : Logitech ASCII keyboard
Mouse : Logitech scroll mouse
SOFTWARE SPECIFICATION:
Operating System : Windows XP
Development Tools : Visual Basic 6.0
Database : Oracle 9i

15. Front End Tool: Visual Basic 6.0
Visual Basic:
Microsoft Visual Basic is the quickest and easiest way to create applications for the
Ms-Windows environment. It allows creation of applications that fully exploit the
graphical user interface (GUI).It makes use of GUI for creating robust and powerful
applications. The GUI suggests user illustrations to text that enables user to interact with
an application. This feature makes it easier to comprehend things in a quicker and easier
way.
Visual Basic makes things more productive by providing tools for the different areas
of GUI developement.One creates the graphical user interface for the application by
drawing objects in a graphical way, and then sets properties on this object to refine their
behavior and appearance. Then this interface is made to react the user by writing code
that responds to events occurring in the interface.
Visual Basic 6.0 in addition to the family of Visual products. It allows to quickly
and easily creating windows applications for PC without being expert in C++ or other
programming language.
Visual Basic 6.0 is specifically designed to utilize the internet. It comes with
several controls that allow creating web-based applications called ActiveX executable.
These will work just like stand alone visual basic application, but they are accessed
through the Microsoft Internet Explorer 3.1 web browser. This allows revising
applications and distributing through the internet.

16. Visual basic comes in 3 flavors
1. The Basic learning edition
The Visual Basic Learning Edition is the introductory edition that leads to
create windows application easily. It comes with all the tools used to built mainstream
windows application.
2. The Visual Basic Professional Edition
The Visual Basic Professional Edition is for computer professional and
includes advance features such as tools to develop ActiveX, Internet control in Data
report writer.
3. The Visual Basic Enterprise Edition
The Visual Basic Enterprise Edition is the most advanced edition and is
aimed to programmers who built all distribution application in the team environment.
It includes features of the professional edition plus. Tools such as visual source sage
(a version control system) and the automation and component manager.
VISUAL BASIC DEVELOPMENT ENVIRONMENT
The form is the central unit in vb.It is a window, initially blank, on which
controls are placed to create the screen. Each form is saved on the disk as a separate
file with an .frm extension.

17. Controls:
Controls are the object, which can be pasted onto a form, and their
properties and the event they can handle vary to suit their nature.
Module:
Code that is attached to a form is accessible from any were on the form and a
marked a .bas extension.
Project:
The project holds together various forms and modules that make up a
program and are marked by a .vbp extension.
Tool Bar:
The tool bar provides quick access to commonly use commands in
programming environment. One can click an icon on the tool bar to carry out an
action referred by that icon.
Tool Box:
The Tool Box provides a set of tools that one can use at design time to place
controls on the form.

18. CONTROLS OF VISUAL BASIC
Label:
Used for text that you don’t want the user to change such as caption.
Frame:
Used to create a graphical or functional grouping for controls .To group controls,
draw the frame first and then draw controls inside the frame.
Text Box:
Used to hold text that the user can either enter or change the text.
List Box:
Used to display a list of items from which the users can choose one. The list
can be scrolled using scroll bars and it has more items that can be displayed at one
time.
Combo Box:
Used to display a list of items, which a text box is attached. The user can
select and place them in the box present in combo.
Check Box:
Used to create a box that the use4r can easily choose to indicate if something is
true or to display multiple choice when the user choose more than one.
Dtpicker: We can place selected year, month, date we specify.

19. OPTION BUTTON:
Used group of option button to display multiple choices from which the user
can choose only. When an event procedure is created for the first time, visible basic
displays an empty event procedure in the code windows.
COMMAND:
Used to crate a button the user can choose to carry out a command.
MS CHART CONTROL:
A chart is that graphically displays data.
The MS chart controls support to the following features:
 True three-dimensional representation
 Supports for all major chart types
 Data grid populations via random data and data arrays.
BACK END TOOL
Oracle 9i
The Back-end used in this project is Oracle. It allows building and maintaining powerful
databases efficiently and effectively
Oracle is a RDBMS (Relational database management system) concept that we can use to
store and manipulated large amount of information. Because its tools are user friendly
and because it is a powerful development environment. Access can be used to:

20.  Store and manage various types of inventories such as recaps, stamps, baseball
cards or other collections.
 Develop order entry-entry systems.
 Create an application that manages survey results.
 Establish help-desk applications
 Manage front ends for enterprise-wide database such as sql server.
 Produce any other database application that departments in their organization
might need
The main element of Oracle:
Oracle is an object oriented program; that is everything in oracle is an object,
including the application itself. Each object has properties that define how it looks and
performs. The main parts are Database window, Tables, Queries, Forms, Report, Macros
and Modules e

21. SYSTEM DESIGN

22. 3. SYSTEM DESIGN
Design is essentially the bridge between requirement specification and final solution for
satisfying the requirements. System design is essentially a blue print or a plan for a
solution to the system.
Properties of System design are
• Verifiability
• Completeness
• Consistency
• Efficiency
• Trace ability
• Simplicity/Understandability
The equipment’s needed to implement the new system is chosen. At this stage, it is kept
in mind that the proposed system is aimed at removing the shortcomings of the old
system. The proposed system should be designed in such a way that it overcomes the
limitations in the existing system
The design phase comprises of the
 Architectural design
 Detailed design
3.1 ARCHITECTURAL DESIGN
 Here a conceptual layout of data structures and data bases is looking at in more
detail.
 The important inputs and outputs along with the function to be provided are
provided are defined in this phase.
 Parts of the proposed system that are to be automated are clearly designed.

23.  Interconnections among modules and data structures are the main goal.
3.1.1 DATA FLOW DIAGRAM
Data Flow Diagram (DFD) or a bubble chart is graphical tool for structured analysis,
it was De Macro (1978) and Gane and Sarson (1979) who introduced DFD.DFD models
a system by using external entities from which data flow to a process, which transforms
the data and creates, output-data-flow which go to other process or external entities of the
file. Data in files may also flows to process as inputs.
There are various symbols in a DFD.Bubbles represents the processes. Named arrow
indicates the data flow. External entities are represented by rectangle and are outside the
system such as vendors or customers with whom the system interacts. They either supply
or consume data. Entities supplying data are known as source and those that consume
data are called sinks. Data are stored in a data store by the process in the system. Each
component in a DFD is labeled with descriptive name. Process names are further
identifier with a number.
DFD’s can be hierarchically organized, which help in partitioning and analyzing
large system. As a first step, one Data Flow Diagram can depict a level 0 DFD from the
context diagram to those giving more details is known as leveling of DFD.Thus a top
down approach is used starting with an overview and then working out the details.

24. 3.1.1 DATA FLOW DIAGRAM
LoginAdministrator User log
Add
new
Item
Purchase View Issue
Daily
exp Make
new bill
Item Purchase
Sale Daily Bill

26. 3.1.2 SYSTEM FLO
Add New
Item
Purchase
Item
Sale Item Daily
Expense
Login
Start
View
Details
Print
Bill
Item
Stock
Sale
Stock
Purchase
PurchaseItem
Sale
Exp
False
True
Bill

27. W CHART
3.2.1 DETAILED DESIGN
In this phase, the database and program modules are designed. They are detailed under program
program and documented. This interface between user and computer is also designed.
The objective of detailed design in as follows:
 To reduce redundancy
 To improve program performance
 To improve integrity and security of data
3.2.2 OUTPUT DESIGN
The main objective of any system is the generation of reports for the user. The output
document depends on the inputs.
The reports generated are
 Add New Item
 Issue Item
 Purchase Item
 Daily Expense
 Make a New Bill
 View Details
• Item Stock Detail
• Sale Detail
• Purchase Detail
Expense
Detail
Stop
Logout

28. • Reorder Level
3.2.2 INPUT DESIGN:
In put design is the process of converting the user-oriented input to a computer
based format it will help the data entry easier and error free. The “Inventory System” is
developed in such a manner that the validation is made for each and every data that is
entered.
The accuracy, economy, validation, reliability, efficiency and timelessness are
considered during design. The timelessness is the most essential factor. If the data is not
entered in time then processing them to time delay.
3.2.3 DATABASE DESIGN:
Database is a collection of tables. A table store data in row and column wise.
Primary source of data, meant to be shared by many users for a variety of application.
The heart of the database is DBMS (Database Management System).
Database ensures data dependence, data integrity, security, backup and recovery.
The designed system maintaining all the properties and a normalized database has been
prepared. The database contains the following tables.
Userlog: This table stores the username and password of users who are authorized to use
the application.
Item Master: It stores information regarding the nature of raw material received. the
information about raw material quality and quantity is stored here.
Purchase: This table stores information about the supplier of raw material, address,
quantity received and amount due.
Sale: It stores information regarding the buyer of semi finished goods. Complete details
of the customer are stored here.
Expense: It stores information regarding the daily usage of raw material.

29. Bill: This table stores customer details.
3.2.4 PROGRAM DESIGN:
The project computerizes the “Inventory System” of Anglo French Textiles (AFT).
The project is divided in to six modules
 Add New Item
 Issue Item
 Purchase Item
 Daily Expense View Details
 Make a New Bill
Add New Item: This module enables to add new items to the stock. It maintains
complete details regarding the nature of stock received.
Purchase Item: This module enables to store information about the supplier, quantity of
goods supplied and other details
Issue Item: The issue module enables to store customer information as to whom semi
finished products have been sold.
Daily Expense: This module maintains information regarding daily stock. The quantity
of raw material taken is maintained which enables to know stock status.
View: This module generates report of Item stock, Sales stock, Purchase stock and
expenses detail
Make a New Bill: This module enables printing of customer details maintained in Issue
Item module.

30. IMPLEMENTATION AND
TESTING

31. 4. SYSTEM IMPLEMENTATION AND TESING
4.1 IMPLEMENTATION
Implementation of software refers to the final installation of the package in its real
environment, to the satisfaction of the intended users and the operation of the system. In
many organizations someone who will not be operating it will commission the software
development project, the people who are not sure that the system is meant to make their
job easier. In the initial stage they doubt about the software but to make sure that the
resistance does not built up, as one has to make up that.
• The active users must be aware of the benefits of using the system
• Their confidence in the software is built up
• Proper guidance is imparted to the user so that he is comfortable in using the
application in the server. If the server object is not running on the server the actual
process does not take place.
4.1.1 CHANGE OVER:
Change over is the stage of moving from old manual system to new computer
based system. In to do that the clerical files has to be converted to computer files. This is
very difficult task to achieve quickly and accurately if the files are in regular use, but the
accuracy of conversion is very important. The change over can be achieved by using
parallel running.
4.1.2 PARALLEL RUNNING:
Parallel running or operation means processing current data in both old and new
system to cross check the results. Its main attraction is that the old system is kept alive
and operational until the new system has been proved for a least one-system cycle. It

32. allows the result of the new system to be compared with the old system before acceptance
by the user.
4.2 SAMPLE CODING:
Dim cn As New ADODB.Connection
Dim rs As New ADODB.Recordset
Dim ars As New ADODB.Recordset
Private Sub cmdRefresh_Click()
txtdate.Text = Date
txtamount.Text = ""
Txtdetail.Text = ""
End Sub
Private Sub cmdSubmitEnquiry_Click()
If txtdate.Text = "" Then
lblMessage.Caption = "The field age cannot be left empty. Please enter the age"
Exit Sub
End If
If txtamount.Text = "" Then
lblMessage.Caption = "The Course Description not given."
Exit Sub
End If
If Txtdetail.Text = "" Then
lblMessage.Caption = "Please Enter the Counceller Name"
Exit Sub
End If
Dim rs2 As New ADODB.Recordset
rs2.Open "select * from EXPENSE ", cn, adOpenDynamic, adLockPessimistic
rs2.AddNew

33. 4.2 SAMPLE CODING:
Dim cn As New ADODB.Connection
Dim rs As New ADODB.Recordset
Dim ars As New ADODB.Recordset
Private Sub cmdRefresh_Click()
txtdate.Text = Date
txtamount.Text = ""
Txtdetail.Text = ""
End Sub
Private Sub cmdSubmitEnquiry_Click()
If txtdate.Text = "" Then
lblMessage.Caption = "The field age cannot be left empty. Please enter the age"
Exit Sub
End If
If txtamount.Text = "" Then
lblMessage.Caption = "The Course Description not given."
Exit Sub
End If
If Txtdetail.Text = "" Then
lblMessage.Caption = "Please Enter the Counceller Name"
Exit Sub
End If
Dim rs2 As New ADODB.Recordset
rs2.Open "select * from EXPENSE ", cn, adOpenDynamic, adLockPessimistic
rs2.AddNew
rs2!edate = txtdate.Text
rs2!detail = Txtdetail.Text

34. rs2!amount = Val(txtamount.Text)
rs2.Update
txtdate.Text = Date
txtamount.Text = ""
Txtdetail.Text = ""
lblMessage.Caption = "The Expense Detail has submitted. Press Escape to exit."
End Sub
Private Sub Command1_Click()
Unload Me
End Sub
Private Sub Form_Activate()
txtdate.SetFocus
End Sub
Private Sub Form_Load()
Dim i As Integer, j As Integer
cn.ConnectionString = "provider=microsoft.jet.oledb.4.0;" & "data source=" & App.Path
& "/Database.mdb"
cn.Open
txtdate.Text = Date
End Sub
Private Sub Form_QueryUnload (Cancel As Integer, UnloadMode As Integer)
cn.Close
End Sub
Private Sub txtDATE_GotFocus ()
lblMessage.Caption = "Please Enter the DATE"
End Sub
Private Sub txtAMOUNT_GotFocus ()
lblMessage.Caption = "Please Enter the AMOUNT IN RS"
End Sub
Private Sub txtDETAIL_GotFocus ()

35. lblMessage.Caption = "Please Enter the EXPENSE DETIAL"
End Sub
4.3 SYSTEM TESTING
The system testing is the stage of implementation, which is aimed at ensuring that the
system works efficiently and accurately before live operation commences. System testing
requires a test plan that consists of several key activities and steps for program, system
and user acceptance testing. Testing is vital to the success of the system. Inadequate
testing or non-testing leads to errors that may not appear until months later. A small
system error can explode into a much larger problem.
4.3.1 WHITE BOX TESTING
In this approach, tests are made with the internal working of the product. All the
independent paths within a module have been exercised once, executing all the logical
decisions, executing all the loops within their bounds. This approach takes long time for
testing.
4.3.2 BLACK BOX TESTING
Black box testing is not an alternative approach to white box testing. It is rather a
complementary approach. The main focus of this approach is on the information domain
rather than on the logical testing. This test ensures that the input is properly accepted and
the desired output is been produced. This approach has a very little regards for the
internal logical structure of the software. This approach saves the time and energy.
TESTING TECHNIQUE
Computer software considers two types of test cases as one to test the specific
Function of the product called as black box testing and the other to test the internal
working of the product called as white box testing. Black box testing examines some
functional aspects of a system with little regard for the internal logical structure of the
software. It enables the Software engineer to derive sets of input conditions that will fully

36. exercise all functional Requirements for a program. It attempts to find errors in categories
as incorrect or missing Function; interface errors, errors in data structures or external data
base functions, Performance errors and initialization / termination errors. Black box
testing is applied during the later stages of testing, since it disregards control structure
and focus on information Domain. White box tests focus on program control structure.
Test cases are derived to ensure that all statements in the program have been
executed at least once during testing and that all Logical condition has been exercised.
White box testing uses the control structure of the procedural design to drive test cases. It
can drive test cases that guarantee those all-independent paths with in a module Have
been exercised at once, exercise all logical decisions on their true and false sides, and
execute all loops at their boundaries and within their operational bounds and exercise
internal data structure to assure their validity.
TESTING PRINCIPLES
All tests should be traceable to customer requirements. The focus of testing will
shift progressively from programs, to individual modules and finally to the entire project.
Exhaustive testing is not possible.
LEVELS OF TESTING
The details of the software functionality tests are given below:
• UNIT TESTING
• INTEGRATION TESTING
• VALIDATION TESTING
• SYSTEM TESTING

37. UNIT TESTING
Unit testing is carried out to verify and uncover errors within the boundary
of the Smallest unit or modules. In this testing step, each module was found to be
working Satisfactory as per the expected output of the module. Unit testing exercise
specific paths in the Modules control structure to ensure complete coverage and
maximum error detection.
Initially low volumes of data, often refereed to as modules were evaluated using
the test data. This constitutes the unit testing. This focuses on individual modules
independently, to locate for the errors.
INTEGRATION TESTING:
Integration testing is a systematic technique for constructing the program
structure while contacting test to uncover errors associated with interfacing .The
objective is to take unit tested modules and build a program structure that has been
dictated by design.
Then the volume was increased gradually, i.e., the individual modules were
linked together, and until the maximum level for each transaction type was reached. This
constitutes the integration testing.
VALIDATION TESTING
It is a final series of software testing. Validation succeeds when software
functions in a manner that can be reasonably expected by the customer. It is achieved
through a series of Black box test that demonstrate conformity with requirements.
The test plan and test procedure are designed to ensure that all the functional
Requirements are satisfied, all performance requirements are achieved, and
documentation is Correct and other requirements are met.

38. SYSTEM TESTING
System testing is actually a series of different tests whose primary purpose is to
fully Exercise the computer-based system. Although each test has a different purpose all
work to Verify that all system element have been properly integrated and perform
allocated functions.
The total system was tested for recovery to ensure that no data were lost during
emergency. Then the system was finally tested with the data were lost during emergency.
Then the system was finally tested with data of the old system for that particular
period and verified with the data of old system for the particular period and verified with
the old reports.
The actual idea was to compare program values against desk-calculated values to
isolate the problem site. The comprehensive test report was then produced. Developer did
these entire tests.

39. CONCLUSION

40. 5. CONCLUSION:
The system was mainly designed to reduce the manual work of updating and
tracking and also make it easier for the user. It also provides flexible and powerful reports
regarding customer details, issue details and stock details. Thus inventory system was
implemented successfully.
5.1 Future Enhancement:
There is always a room for improvement in any software package, however good
and efficient it may be. But the improvement thing is that the system should be flexible
enough for further modifications. Considering this important factor, the system is
designed in such a way that provisions can be given for further enhancement without
affecting the system presently developed.

41. BIBLIOGRAPHY

42. REFERENCES
1. SOFTWARE ENGINEERING
Richard Farley, Tata McGraw Hill Companies Inc.,
Fifth Reprint, 1997
2. COMPUTER DATABASE MANAGEMENT SYSTEM
James Martin, Eastern Economy Edition,
Prentice Hall of India Private Limited,
Second Edition1999
3. VISUAL BASIC 6.0 FROM THE GROUND UP
Gary Cornell, Tata Mc Graw Hill Publishing Company Limited,
Second Edition, 1999.

43. APPENDICES

44. FILE STRUCTURE:
* specifies Primary Key
1. Table Name: Userlog
Field Name Data Type
Username Text
Password Text
2. Table Name: Purchase
Field Name Data Type
Pdate Date
Dealer Name Text
Item Group Text
Item name Text
Item size Number
Price Number
Qty Number
Total amount Number

45. 3. Table Name: Sale
Field Name Data Type
Sdate Date
Cname Text
Caddress Text
Item group Text
Item name Text
Item size Number
Price Number
Qty Number
Amount Number

46. 4. Table Name: Item master
Field Name Data Type
Serial no* Number
Itemname Text
Groupnam
e
Text
Codeno Number
Itemsize Number
Trash Number
Staple Length Number
Mixing Number
GTex Number
Qty Number

47. 5. Table Name: Expense
Field Name Data Type
Edate Date
Detail Text
Amount Number
6. Table Name: Bill
Field Name Data Type
Sdate Date
Cname Text
Caddress Text
Itemgroup Text
Itemname Text
Itemsize Number

48. Price Number
Qty Number
Amount Number
SAMPLE OUTPUT

49. SAMPLE OUTPUT