FINAL PROJECT DOCUMENTATION

(General Inventory Management System)

General Inventory Management System

DEVELOPED BY:

FAHAD SHAHZAD Roll No: N447143

SYED MURTAZA Roll No: N447144
INAM ULLAH Roll No: N447147

Students of BS (CS) Final Semester

Supervised By: Mr. Asif Sohail

Department Of Computer Science
Allama Iqbal Open University,
H-8, Islamabad
 Year 2007

Declaration

We hereby declare that this software, neither as a whole nor as a part thereof
as been copied out from any source. It is further declared that we developed
this software and this report entirely on the basis of our personal efforts
made under the sincere guidance of our project supervisor.

If any part of this software probed to be copied or found to be a report of

some other, we shall standby the consequences.

No portion of the work presented in this report has been submitted in

support of any application for any other degree or qualification of this or any
other University or institute of learning.

We further declare that this software and all associated documents, reports,
and records are submitted as partial requirement for the degree of BS (CS).

We understand and transfer copyrights for these materials to Allama Iqbal

Open University, Islamabad.

We shall not sale this software and documents and shall not get any
Financial gains from these.

STUDENT NAMES: SIGNATURES:

INAM ULLAH Signature: ____________

FAHAD SHAHZAD Signature: _____________

SYED MURTAZA Signature: _____________

PROJECT SUPERVISOR: SIGNATURE: ____________

Final Approval

This is to certify that we have read the project report titled as (General
Inventory Management System) submitted by students as mentioned below.
It is our judgment that this report is of sufficient standard to warrant its
acceptance by Allama Iqbal Open University, Islamabad, for BS (CS)
degree.

Examination committee

1. Internal Supervisor

Designation

Study Center Computer People 2000, Sialkot

2. Internal Examiner

Designation

Study Center Computer People 2000, Sialkot

3. External Examiner ……………………………….

Designation ……………………………….

Study Center/Organization ……………………………….

 Acknowledgment

All thanks and praise to ALLAH the Almighty who blessed us with
Knowledge and courage to accomplish this job.

We are thankful to our parents whose prayers helped in every problem

pf life and the provision of necessary resource to facilitate us.

We are thankful to our teachers who helped us to carry out this job
and provide us guidance to complete this project specially Mr. ASIF,
project supervisor and the teachers who taught us were excellent in their
fields and they gave us new ideas and meanings to the problem related to our
academic and regular life.

We are especially thankful to the administration of organizations for

providing us all the necessary information about the organization required
for completing the project.

Especially we are thankful to Mr. AJMAL, Mr. MUHAMMAD

JAWAD and Mr. MUHAMMAD FAISAL who helped us a lot and proved
to be an excellent resource person along with the excellent guiding skills and
friendly nature.

In the end we want to thank all our sincere friends and class fellows
who stood by us in every situation. We pray for all to be a useful and sincere
beneficent asset for themselves and for their country.
 Project In Brief

Project Title: GENERAL INVENTORY MANAGEMENT SYSTEM

Organization: GENERAL (ANY ORGANIZATION CAN USE IT)

Objectives: Atomize the Manual Inventory system

Developed By: 1) INAM ULLAH (N447147)

2) FAHAD SHAHZAD (N447143)

3) SYED MURTAZA (N447144)

Supervised By: Mr. Asif Sohail

Tools Used:
 Ms Visual Basic 6 ®
 Ms Office XP 2003®
 Ms SQL Server 2000 ®
 Crystal Report
 Erwin 4

Operating System: Windows XP Professional®

System Used: Pentium 4 (1.8 GHZ or Greater)

Abstract

Need:
Mostly organization use Manual System to manage all their records .Their

manual system works very slowly and management of records becomes

difficult. The growth of any organization and its outlets require an efficient

computerized system which is faster than the manual system and to keep

their records efficiently in the ongoing system.

Objectives & Scope Of Work:

Our goal is to provide a computerized Inventory

Management System for organizations to manage their records efficiently.

Features:
1- Perpetual:

The system provided will be perpetual i.e. the record will be updated

along with the transaction.

2- Flexibility:

The system will provide the user flexibility of adding or

removing any category or attributes of the Database.
Method Of Studying:

a) Direct meetings with the resource person to understand their

requirements.

b) Studying the working methodology of the organization.

c) Observing the working criteria of the Existing system used in

organization and draw backs in it.

Major Finding:

Inflexible:
Manual record keeping system was not much efficient.

Concluding Remarks:

 This is just the beginning for us but now it will step toward progress.

 The inventory system must be refined according to modern values.

 The system should be easy to use.

 It will save lots of time, complexities and minimize the administrative

overhead.
 TABLE OF CONTENTS
CHAPTER # 1 INTRODUCTION

1.1 BRIEF INTRODUCTION OF THE ORGANIZATION

1.2 PROBLEM DEFINITION
1.3 SCOPE OF THE PROJECT
1.4 BROAD BASED OBJECTIVES
1.5 SPECIFIC OBJECTIVES
1.6 FEASIBILTY REPORT

CHAPTER # 2 EXISTING SYSTEM ANALYSIS

2.1 INTRODUCTION
2.2 DETAIL STUDY OF EXISTING SYSTEM
2.3 DRAW BACKS IN EXISTING SYSTEM
2.4 MAIN ANALYSIS DIAGRAM

CHAPTER # 3 PROPOSED SYSTEMS

3.1 OBJECTIVES
3.2 SYSTEM PROPOSAL
3.3 MAIN SYSTEM DIAGRAM
3.4 BENEFITS/MAIN FEATURES OF THE PROPOSED
SYSTEM

CHAPTER # 4 SYSTEM DESIGN

4.1 INPUT DESIGN

4.2 OUTPUT DESIGN
4.3 CODE DESIGN
4.4 USER INTERFACE DESIGN
4.5 DATABASE DESIGN
CHAPTER # 5 SYSTEM IMPLEMENTATIONS

5.1 INTRODUCTION
5.2 METHOD USED FOR IMPLEMENTATION

CHAPTER # 6 SYSTEM TESTING & EVALUATION

6.1 TESTING STRATEGIES

6.2 CODE TESTING
6.3 PROJECT TESTING REPORT
6.4 USER TRAINING
6.5 CONCLUSIONS

CHAPTER # 7 FUTURE EXTENSIONS

7.1 INTRODUCTION

CHAPTER # 8 USER GUIDE

8.1 INTRODUCTION

REFERENCES

Books and materials referenced to with author, title, publishing

company, year of publication, page number

APPENDICES
1) ER- Model
2) Sample input screens
3) Sample output screen
 CHAPTER

1 INTRODUCTION

CONTENTS:

⇒ BRIEF INTRODUCTION OF THE

ORGANIZATION

⇒ PROBLEM DEFINITION

⇒ SCOPE OF THE PROJECT

⇒ BROAD BASED OBJECTIVES

⇒ SPECIFIC OBJECTIVES

⇒ FEASIBILTY REPORT
 BRIEF INTRODUCTION OF THE
ORGANIZATION

Any organization like factory or departmental store which

deals with

the selling, purchasing & ordering of different items can use

this

application because it is general inventory management

system.

This system can be used in many situations where inventory

of items

are expected. This system can deal with items like

 Mobile phones;

 Accessories of any items,

 Chemicals used in factory,

 Household things, raw material used in factories,

 Garments,

 Cosmetics,

 Stationary,
Etc.
PROBLEM DEFINITION
Mostly organizations use manual systems for their stock &
storing

data. By using manual system, management needs a lot of

times for

checking the stock of any product. It is also difficult for

management

to note the daily sale in the register at end of any day and
collect the

sale of all the days at the end of every month. By calculating

or

knowing about the profit & loss. But still loss or profit isn’t
known

exact. Management can’t know at any time about the exact

performance of any organization or departmental store.

SCOPE OF THE PROJECT

Scope of the project is to provide a computerized inventory

management system. If any organization or departmental

store use
system then following tasks can be performed:

 Minimize resource consumption,

 Maximize utilization of the resources,

 Provide help to management to know about every thing

or matter about the organization or departmental store,

 Helps management in decision making to increase the

performance of any organization,

 Information can be obtained easily.

BROAD BASED OBJECTIVES

Broad based objectives are those essential tasks which are

added in

Software. Following are the Broad based objectives:

♦ Reduce human efforts,

♦ Reduce the paper work,

♦ Reduce repetitions,

♦ Easy approach to obtain information,

♦ Improve the performance of the management,

 ♦ Computerize the stock, customers & location’s
information & records,

SPECIFIC OBJECTIVES

Some of the specific objectives are under as:

o To make the design of system interactive,

o To run software quickly & efficiently,

o To help management to know about the different

records & reports,

o To store data easily,

o To delete the unnecessary information,

o Obtain the stock information & reports on single click.

 FEASIBILITY REPORTS

The main purpose of feasibility study is to consider the

proposed

system with a view to decide weather the developed of the

proposed

system is feasible for the organization in the underlying

circumstance.

It is considered that whether the proposed system will meet

all the

requirements of the organization with lesser cost and with

improved efficiency that the exciting if exists.

Feasibility of the project can be measured by following

points:

 Operational Feasibility Report

 Technical Feasibility Report
 Economic Feasibility Report

1- Operational Feasibility Report:

Operational Report gives
us the

information how to operate the project. It tells us that which

tools we

will need and use for successful Accomplishment of our

project.

2- Technical Feasibility Report:

Technical report gives us the
following information:
 • Is a project technically feasible?

• Can defects be reduced to a level matching the

application’s need?

Technical report is state of the art. It depicts the technical

complexities for the project.

3- Economical Feasibility Report:

Economical report gives us
the

information, can development be completed at a cost the

software

organization its client or the market can afford it.

It is a measure of cost effectiveness of a project or

solution. It

tells us cost of a project.

SUMMARY REPORT

After performing these tests we conclude that the

project is feasible, that is the solution is acceptable to
the all concerned, from the point of view of performance
improvement.

The project is technically feasible as the solution can

have the capacity to work in a practical situation.
The project is also schedule feasible as we have a
substantial amount of time available to complete the
project according to university recommendations.

The economic feasibility is not determined for the time

being as we are not developing a project for commercial
purposes, and only as a coursework recommended by
the university.

However, in every project the cost effectiveness factor is

also considered to determine the cost for developing a
system and the benefits of the system. The cost may
include the technical staff required, the software tools,
the equipments, the methods and above all budgetary
details. If a project, however requires high cost but
provides low benefits is not feasible. If a project,
however, requires high costs and provides high benefits
is technically feasible but not economically.
CHAPTER

2
ANALYSIS
EXISTING SYSTEM

CONTENTS:
⇒ INTRODUCTION

⇒ DETAIL STUDY OF EXISTING SYSTEM

⇒ DRAW BACKS IN EXISTING SYSTEM

⇒ MAIN ANALYSIS DIAGRAM

 INTRODUCTION
This step involves the analysis of the whole system. Nothing
can be

Done without full analysis of the problem. In every field of

life, one

has to take a brief look at the problem 1st then tries to

remove the

drawbacks. Any example you take from the real world

involves this

step of analysis & then proposing the solution of that

problem. A

doctor before prescribing any medicine to the patient

analyze her/him

with the help of tests taken & his own analysis, an engineer
would

never build any thing before analyzing the environment.

Similarly, a system analyst needs to study the system deeply

&

properly for the further actions. It is the most important step

in

developing a new system, the base of the whole system

depend upon

the understanding of the analysis of the existing system

because this
analysis will help to reduce the flaws in the existing system
will

overcomes all the drawbacks.

Program or system study can be responsive only if the

problem is

Properly understood. Error in understanding leads to design

error.

Through study of existing system is necessary to design a

new

system which is more efficient, flawless & reliable.

DETAIL STUDY OF EXISTING SYSTEM

Existing system is manual. Whenever the customer is come,
the

seller helps him to buy his required item, the bill manually.
Then

he gives original copy of invoice to customer & has a carbon

copy of

invoice o cash memo of there own record.

If the customer pays his bill as a credit he accountant keeps

his

records on the credit book with the name address invoice his
credit

amount. Similarly, they purchase different items from

different

companies for sale. If they bought as borrow then they

keeps the

record of creditors in creditor’s debit book with company

name & with

debit amount.

DRAW BACKS IN EXISTING SYSTEM

The manual system is work in the following ways:

There are registers in which a record of all the things &
books is

Written when new stock is arrives. This is done on monthly

basis as

New stock arrives on every 1st day of the month after

everything is

recorded then the whole stock is loaded in the basement &

the extra

place/store hired to store the stock. After all the recording of

the stock

in a register, the things needed in the store or shop are

taken out of

the stock & are available for sale, there is no record of the
number of

copies sold for a particular book. There is no proper system

of

issuing a bill to customer as the bill is written on a piece of

paper &

the total is calculated manually. This can sometimes produce

inaccurate results as human beings can make mistake.

Following are the main draw backs of the existing system:

1. Chances of too many errors like improper stock keeping

erroneous calculation of bill etc.

2. The manual system is too much time consuming and

old fashioned.
3. It is not properly giving services to management
because it is not efficient.

4. Wastage of time.

5. Huge volume of documentation.

6. A lot of paper work.

7. Difficult to maintain records.

8. Extra usage of stationary.

9. Extra usage of Human resource.

10. No specific report system and lot of time required

to prepare reports.

11. No long life future planning.

12. Current situation of organization is unknown

To overcome the difficulties faced by organization and to

maintain

the record properly the new proposed system will be more

precise

and efficient.
CHAPTER

3 PROPOSED SYSTEM

CONTENTS:
⇒ INTRODUCTION

⇒ PROPOSED SYSTEM

⇒ OBJECTIVES OF THE PROPOSED SYSTEM

⇒ MAIN ANALYSIS DIAGRAM

 INTRODUCTION

After analyzing the existing system and encountering

the

shortcomings of the present system, it was necessary to

remove its

deficiencies and give a worthy solution for presently

encountered

problems. The proposed system has therefore been

suggested

keeping in view the need and demand of the organization.

Frequent visits to the organization (Store) and interviews of

the

concerned staff and some executive to understand the

existing

working strategy are the basis of the proposed system.

 PROPOSED SYSTEM

After knowing the existing manual system and

encountering the

shortcomings of the present procedure of getting knowledge

about

stock, purchasing & selling of items, invoice records of

creditors and

debtors it is necessary to overcome the drawback of the

current

system and gave a worthy solution of the problem. The

proposed

application for Stores is therefore been suggested keeping in

new the

needs and comforts of the user.

OBJECTIVES OF THE PROPOSED
SYSTEM

The main goal of this project is to design and

implement a GUI

system in which data entry, report generation and queries

are

possible, which help the management in decision making.

Following

objectives are kept in mind while proposing the system:

• The proposed system should be more efficient than the

existing system.

• The interface should be user friendly and provide help

to user, where required Should have the capability and
process information which is entered into it.

• It should be error free and reliable.

• To make data reliable.

• It should minimize redundancy of data.

• It should be a comprehensive.

• It should be a comprehensive data consisting of

insertion updating accession and deletion of any record.

• Keep every thing nice and simple for all users.

 • The system should generate reports whenever if
demanded by the user.

SYSTEM PROPOSAL
The pc based application is proposed which could the

necessary requirements about billing of customers, and

debited
records is small tie and in organization to get accurate
reports. It will

provide its organization with required information such as:

1. Detail information about a specific items its quality in

hands, its price per unit, when to order this item for
repurchase.

2. No of customers, Orders, Sale and Purchase Details and

items they have purchase from store.

3. Total quality sale of specific item on per day basis.

4. Total sale of all items on per day basis.

By using the system organization can make the reports and

information up to date. Consequently the whole procedure

results in

the better performance of the organization.

MAIN SYSTEM DIAGRAM:
BENEFITS/MAIN FEATURES OF THE
PROPOSED SYSTEM
 A pc based menu driven computerized system is

proposed which could satisfy the necessary requirements

and

improve upon the currently running system considering the

objectives

of the proposed system its main features are:

Following features are kept in mind while proposing the

system.

1. User Interface/Friendly:
For better user interaction the
screen

would be well designed keeping in mind that enter should be

simple

and easy for the user and data will be accepted in the same
manner

as it is done manually.

2. Checks:
Various checks will be provided in the data
entry,

updating and deletion modules to appropriate action. The

checks may

be to avoid duplicate record, item validation, range checks

etc, the
system will give appropriate message upon the conflict with
each

check.

3. Updating:
System will also provide the facility of
updating. Any

mistake detected or any other necessary updating can easily

be

made through updating. User may update any field with the
exception

of PK defined for that table because database does not allow

this.

5. Deletion:
Facility of deletion of a particular record is also
provided

to the authorized user. Only those records can be deleted

that do not

have a foreign key relationship with some other table.

6. Ease of Use:
The developed application is User -
Friendly

software to handle and use. Data entry, deletion, searches,

exit is all

provided on a single form.

7. Application Security:
The security of the application is
implemented by allowing only organization user to log on the

application and performed desired task.

8. Consistency:
Uniform notations have been used
throughout the

application. Efforts have made to keep the data

homogenous. This

had been accomplished by reducing data redundancy, insert

and

update anomalies.

CHAPTER

4 SYSTEM DESIGN

CONTENTS:
⇒ INTRODUCTION

⇒ INPUT DESIGN
 ⇒ OUTPUT DESIGN

⇒ CODE DESIGN

⇒ USER INTERFACE DESIGN

⇒ DATABASE DESIGN

INTRODUCTION
Design is the first step in moving from the problem domain
towards

Solution domain. Design is essentially the bridge b/w

requirements

specification and the final solution for satisfying the

Requirements.

It may be the process of applying various techniques and

principles

for the purpose of defining a device, a process and

application or a

system. Before the Development of any system it is

important to
make its design before its implementation. Design of the
system must

be flexible and easy for the user.

System Design is divided into following steps.

• Input design
• Output design
• Code design
• User interface design
• Database design
INPUT DESIGN
Input is the information that is required for the user for
further

processing by the system. Input design activity is related to

design of

reviewing such information from the user in well format.

Data entry forms of application are design to

get data

input. Mostly text fields, input boxes, combo boxes are used
for data

input. Also some checks are applied on data entry so that

user avoids

invalid data entry. Before designing of input taking systems

length

and type of each field is determined.

 GENERAL PRINCIPLE OF INPUT DESIGN

1. Entry only variable data

2. Don’t enter data that can’t be stored or calculated in
computer programs.
3. Use codes for appropriate attributes.
4. Include instructions for completing the form.
5. Minimize the amount of handwriting.
6. Data entered should be sequenced.
7. Place portions of the form that aren’t to be input in or
about the lower right portion of the source document.
8. Ensure that the data is valid.

Following checks can ensure validation of data like

- Completeness checks
- Limited and range checks

OUTPUT DESIGN
The output design also plays an important role in
computerized
systems. User wants the perfect and on time outputs which
can make

system more and more efficient. In designing output

following factors

are kept in mind.

1. Computer outputs should be simple to read and

interpret,

2. Title is given to every report or output screen,

3. Section headings are included to divide large pieces of

information,

4. Purpose of output should be clearly mentioned.

TYPES OF OUTPUTS
There are two types of outputs.

• Screen Outputs
• Printed Outputs

Screen Outputs:
These are such statements which gives
retrieval of
data on screen. Since the System is database oriented so the
system

should be appropriate and good for showing outputs. Screen

outputs

may be in the shape of message box, labels and some other

components of language.

Printed Outputs:
Printed outputs are typically concerned with
reports

of different types. e.g. Stock Report, Product Report etc.

CODE DESIGN

Coding is a process of writing instruction that can be run on

computer hardware.
In the coding phase, the design of a system is translated into
machine readable code by using specific language. Although
the coding phase doesn’t effects the structure of the system,
it has great impact on the internal structure of modules,
which affects the test ability and understands ability of the
system.
The goal of the coding phase is to produce simple and clear

program. That aim is not to reduce the coding effort but to

program in
a manner such that the testing and maintenance cost are
reduced.

USER INTERFACE DESIGN

The user interface design is the activity comprising
interaction
between the system users, and the computer.
There are several types of user interface styles. These
different types of interface styles are blended when we
design systems with GUIs.
With the advent of graphical operating system, the world
of computing went through a dramatic change. It opened
up a whole new world of graphics. Interface such as GUIs
became very popular because displayed on screen.
The primary requirement for an interface is that it is
easy to use. A user must be able to react intuitively to
an interface provided to him.
The design process for user interface design is iterative
and can be represented by using spiral model.

The activities of spiral model are:

 1. User, Task And Environment Analysis And Modeling,

2. Interface Design,

3. Interface Construction
4. Interface Validation

PRINCIPLE OF USER INTERFACE DESIGN

During user interface design, following guidelines are

followed:
- Placing the user in control
- Reducing the user’s memory load
- Making the interface consistent
- Hide technical details
- User familiarity
Basic Components Of A Interface:
- Windows
- Buttons
- Text boxes
- List boxes

DATABASE DESIGN

Physical database design is a process of mapping

database structures from logical design to physical
storage structures such as files and tables. Physical
database design is a activity in a activity in any
database design having following steps:

o Define database to DBMS.

o Decide on physical organization of
data
o Design program.
DESIGN OF DATABASE
CHAPTER

5 SYSTEM IMPLEMENTATION

CONTENTS:
⇒ INTRODUCTION

⇒ METHOD USED FOR IMPLEMENTATION

⇒ KEY ELEMENTS IN METHOD USED FOR

IMPLEMENTATION
 INTRODUCTION
Implementation is the next phase in the system

development life cycle. Implementation includes all those

activities

that take place to convert from the old system to the new
one.

In Implementation basically we find the way to develop the

system. In

Implementation phase coding is performed. Implementation

is also

called System Development. In this phase system is built or

meets

the proposed and designed specification.

 METHOD USED FOR IMPLEMENTATION
Method used for Implementation is divided
into some phases
1. Analysis
2. Design
3. Coding
4. Testing

When we adopt any Method for Implementation it consists of

the

phases given above.

1. Software requirement Analysis:

Software
requirement Analysis

is the first phase of the method used for Implementation. To

understands the nature of the program to be built the

software

engineer must understand the information domain for the

software, as

well as required function behavior, Performance and

Interface.

2. Design:
Software design is the next step of method
used for

implementation. It is a process that focuses on the

attributes of the
 program such as Data structure, Software architecture,
Interface

Representation and procedural Details.

The Design process Translates requirements into the

representation of the software that can be accessed for

the quality

before coding begins. Design may be procedural or

Detailed

Design.

3. Coding:
After designing next activity of method for

implementation is Coding. The design must be translated

into a

machine readable form. The code generation step performs

this task.

Coding process is also called Development or

Implementation.

4. Testing:
Once code has been generated, program
testing

begins. Testing phase insures that there are no errors and

bugs in

the system. System is tested by using many different

approaches.
 KEY ELEMENTS IN METHOD USED FOR
IMPLEMENTATION

There are some key elements which plays an

important role in implementation methods:

1. Software And Database Selection

 2. Software And Database Design

3. Selecting Suitable Software Process Model

CHAPTER

6 SYSTEM TESTING & EVALUATION

CONTENTS:
 ⇒ INTRODUCTION OF SOFTWARE TESTING

⇒ TESTING OBJECTIVES

⇒ TESTING PRINCIPLES

⇒ TESTING STEPS

⇒ TESTING STRATIGIES

⇒ CODE TESTING

⇒ PROJECT TESTING REPORT

⇒ USER TRAINING

⇒ CONCLUSIONS

Introduction of software Testing

In a software development project errors can be

injected at

any stage during the development. For each stage there are
some

techniques with which we can detect errors and bugs from

our

system. Testing is a phase where errors remaining from

earlier
phases are detected.

TESTING OBJECTIVES

Testing objectives can be stated as:

1. Testing is a process of executing a program with the
intent of finding an error.
2. A good test case is one that has a high probability of
finding an as-yet-undiscovered error.
3. A successful test is one that uncovers an as-yet-
undiscovered error.
 TESTING PRINCIPLES

Testing principles are given below:

1. All tests should be traceable to customer requirements.
2. Tests should be planned long before testing begins.
3. Testing should begin in the small and progress toward
testing in the large.
4. Exhaustive testing is not possible.
5. To be most effective, testing should be conducted by an
independent third party.
 TESTING STEPS

Software is tested from two different perspectives:

Internal program logic is exercised using white box test case
design techniques, and software requirements are exercised
using black box test case design techniques.
In both cases, the intent is to find the maximum number of
errors with the minimum amount of effort and time.
 TESTING STRATEGIES
Following testing strategies are adopted by us to ensure
software operability:
Black Box Testing:

• It is also called Functional Testing.

• Testing without the knowledge of the

internal system being tested.

• Focuses on the functional requirements of

the software.

• Test cases are designed to find the

following types of errors in the software:

a) Incorrect or missing function,

b) Interface Errors,

c) Errors in data structure or database access,

d) Behavior & Performance errors,

e) Initialization & Termination Errors.

White Box Testing

 • It is also called structural testing or glass box
testing.

• It is used to test the internal procedural working

of a module.

• It enables us to detect errors caused by typing

mistakes.

• Test cases are designed for the following

purposes:

a) Ensure the all the independent paths within a

module have been exercised at least once.

b) Exercise all logical decisions on their true and

false side.

c) Execute all loops at their boundaries and within

their operational bounds.

d) Exercise internal data structure.

System Testing:
• It consists of a series of tests to fully exercise a
computer based system.

• It includes the following types of tests:

a) Recovery Testing.

b) Security Testing.

c) Stress Testing.
 d) Performance Testing.

CODE TESTING
Code is tested by code reading and by adopting
any

strategy for testing code modules and program components.

The process of code reading is best done by reading the

code inside

out, starting with the innermost structure of the module.

For example we can adopt white box testing method and

integrating
testing method because this method can find many internal
errors.

PROJECT TESTING REPORT

After applying all testing methods such as

verification code reading analysis, White box testing and

system

testing all helped us to ensure the proper functionality of

the project

and removal of possible errors, since we are the developer of

this

software we tested this software by sample data and tried

to find out
errors and mistakes in the design and code of the software.

During the coding phase the code reading method helped us

to

detect errors often not revealed by testing. As every

program have

bugs of some type in it. It is almost impossible to find every

bug in a

commercial level program

As integrated software testing approach consist of several

stages

including module testing, program testing and acceptance

testing. In

module testing all the individual modules are tested and

assessed as

working properly, they are combined so that program testing

can

begin.

User interfaces the systems security features, the ability to

deal with

abnormal processing volume and the ability to recover from

software

failures are tested. Acceptance testing as part of the

integrated

testing strategy was not conducted because we had to

develop
software not commercially but as a requirement of the
university. But

we had tried our best to ensure that the requirements

gathered

through the analysis phase must be met to a minimum

extent, so that

it will help us to develop software in feature keep in mind,

the main

procedures of commercial software.

USER TRAINING

With the burst of activity in end-user computing and the

appearance of new tools for computer professional,
training is becoming a major component of
implementation. Whenever a system is acquired, which
often involve new hardware and software; both user and
computer professional generally need some type of
training. Often this is through classes give by developers
and through hands on leaning techniques.
For user training help documents, user guides and
manuals are also prepared
So end user can consult with these documents.
Training Approaches:
 Two main categories of end-user
training approaches are usually used:

- Instructor Led Methods

- Self Study Methods

1- Instructor Led Methods:

The most common instructor
led

approach is the lecture, but this is seldom used by itself

in end-

user training. Discussion is often use along with lecture

and

demonstration is also used specially when training user

how to

work, with new software. After the instructor

demonstrates the

task, users practice it own.

Developers may also give these classes.

2- Self Study Methods:

In recent years, increasingly more
user-training program have incorporated self-study
methods as part of the training process. Computer-based
training, tutorial and multimedia training systems are
examples of self-study methods. The user’s manual
created by us demonstrates the working of each of the
input forms of the software so that the user can learn on
his self-how to interact with the software so that he may
be able to use the software more efficiently.
 CONCLUSIONS
Finally we come to conclusion that the software testing
and evaluation phase helped a lot of to understand the basis
of software testing and its evaluation. During testing we
found that the software must be evaluated in such a way so
that it can operate in accordance with the requirements
gathered during system analysis. As every software is tested
with an intension so that all bugs and errors may have been
removed but software may present errors as they are
brought to production.

CHAPTER

7
 FUTURE EXTENSION

CONTENTS:
⇒ NEED OF EXTENSIONS

⇒ AREA NEEDING IMPROVEMENT

NEED FOR EXTENSIONS

As every man-made product is not complete in its own,

there is always a need for improvement. Because it is
our first project as a first effort, we have tried our best
to make available every functionality to the software.
But due to many constraints such as our programming
ability may not be up to the expertise need of a fully
functional system, or the technical abilities of the users,
or the time frame allowed to us to complete the project
would have not allowed us to enhance the capabilities of
the system. Also keeping in mind the idea of incremental
development paradigm (as adopted by the international
organizations) we preferred to design our project in
incremental stages. So that the users become aware of
the basic procedures of the system and would be able to
interact with more functional system, provided to them
in future.

AREAS NEEDING IMPROVEMENT

(FUTURE ENHANCEMENTS)
There are many areas in the software, which can be
enhanced or developed to further give the system an
extra ability to operate efficiently. Among several areas,
some of them are written below:

 Database features can be introduced.

 Design of the forms can be enhanced.
  More front-end security and flexibility.
 System can be converted into online System.
 System can be developed with latest technology.

CHAPTER

8 USER GUIDE

CONTENTS:
⇒ INTRODUCTION

⇒ TYPES OF HELP

⇒ USER MANUAL
 INTRODUCTION

Almost every user of an interactive, computer-based

system requires help now and then.

In some cases, a simple question addressed to a

knowledgeable colleague can do the trick. In others,
detailed research in a multivolume set of “user manual”
may do the only option. In many cases, however, modern
software provides online help facilities that enable a user
to get a question answered or resolve a problem without
leaving the interface.
 TYPES OF HELP
Two different types of help facilities are encountered:

- Integrated
- Add-on

An integrated help facility is designed into the software

from the beginning. It is often context sensitive,
enabling the user to select form those topics that are
relevant to the actions currently being performed.
Obviously, this reduces the time required for the user to
obtain help and increase the ‘friendliness’ of the
interface. For example the Tool-Tip-Text property of
controls in Microsoft Visual Basic6.0 enable the
developer to provide integrated help facilities for certain
actions, which require help for the user to operate the
system more accurately.
An add-on help facility is added to the software after the
system

has been built. In many ways, it is really a user’s manual

with

limited query capabilities. The user may query about

certain

topics to find out related information.

 USER’S MANUAL OR USER’S GUIDE:

User’s manual or User’s Guide can use graphical displays

or text to give information about the System. This
enables the user to understand the application more
frequently and he can interact with application more
easily.

User’s manual or User’s Guide of IMS is given as

Our product:
The product we have launched is named as

“INVENTORY MANAGEMENT SYSTEM” OR “IMS”.

We have basically developed it for the organizations which

use

manual system and face lots of difficulties in their business.

Working of System:
Our developed
“INVENTORY MANAGEMENT SYSTEM”

is basically software which handles the information and data

of an

organization. It handles entities like Products, Customers,

Suppliers,

Sale, Purchase, Customers order and Purchase order

and saves data about them. It also generates reports on
demand.

How To Operate:
To operate the system follows the steps:

a. Run IMS exe

b. After introduction screen login screen will be open

c. Enter the password, if password is correct then main

screen of the system will appear this screen have
the buttons and menus of all the activities.

d. Click on desire buttons or menu.

e. Clicked task will open on screen, now you can

perform your desired tasks.

REFERENCES

BEGINNING VISUAL BASIC 6

BY PETER WRIGHT’S

MASTERING IN VISUAL BASIC 6

BY EVANGELOS PETROUSTSOS

MASTERING IN DATABASE IN VISUAL BASIC 6

BY EVANGELOS PETROUSTSOS

VISUAL BASIC 6
BY C M ASLAM
MODERN DATABASE MANAGEMENT
BY FRED R. MCFADD EN & JEFFERY A.HOFFER

APPENDICES
PRODUCT FORM
CUSTOMER’S FORM
SUPPLIER’S FORM
SALE’S FORM
PURCHASE’S FORM
PURCHASE ORDER’S FORM
CUSTOMER’S ORDER FORM
TRANSACTION’S FORM
RELATIONSHIP BETWEEN TABLES