A

DISSERTATION

ON

“Sales and Inventory Management”

UNDERTAKEN AT

SHREE SAI INSTITUTE OF TECHNOLOGY

By

Arzan Bhesania

SUBMITTED TO

Vikram University, Ujjain

In

Partial fulfillment of the requirement for the Award of the Degree of

Bachelor of computer application (B.C.A)

May 2017

GUIDED BY

Prof. Sanjay Bohara

Prof. Mirza Naziya Baig

Computer Application Department

SHREE SAI INSTITUTE OF TECHNOLOGY, RATLAM
1|Page
 Certificate of the principal/director
Reference No. …………………… Date ………………..

Project Completion certificate

This is to certify that Mr. Arzan Bhesania, student of BCA (IV semester) of
Shree Sai Institute Of Technology, has successfully completed the project
work entitled “Sales And Inventory Management” under the guidance of
Prof.Sanjay Bohara & Prof Mirza Naziya Baig is a bonafide piece of work
carried out at Shree Sai Institute Of Technology.

The project entitled Sales and Inventory Management developed by

Mr. Arzan Bhesania in the Shree Sai Institute of Technology and he has
done his laboratory work during the tenure of the project with the guide
to complete this project. All the prescribed certificates are attached after
the completion of all the formalities of the project work as per schedule,
including internal examination.

Place: Signature of Principal/Director

Date: Seal of the Institute

2|Page
Reference No. …………………… Date ………………..

Certificate of Attendance

This is to certify that Mr. Arzan Bhesania student of BCA (IV Semester) of
Shree Sai Institute of Technology has put at least 200 hours of laboratory
work with the guide to complete this project during the situated period of
the project at Shree Sai Institute of Technology.

Signature of guide

Place: Signature of Principal/Director

Date: Seal of the Institute

DECLARATION
3|Page
I Arzan Bhesania of Shree Sai Institute of Technology declare that the
dissertation/project report submitted by me under the guidance of
Prof.Sanjay Bohara & Prof. Mirza Naziya Baig is a bonafide work for Partial
fulfillment of the requirement of the BCA IV semester minor project work. I
have incorporated all the suggestions provided by my guide time of time.

I further declare that to the best of my knowledge this dissertation contains

my original work and does not contain any part of any work which has been
submitted for the award of any degree either in this university or in any
other university/Deemed university/Institute etc. Without proper citation
and I shall be fully responsible for any plagiarism found at any stage.

Name & Signature of the guide Name & signature of the student

Reference No. …………………… Date ………………..

4|Page
 Dissertation Approval Certificate

This is to certify that Mr. Arzan Bhesania student of BCA (IV semester) of
Shree Sai Institute of Technology has successfully completed the project
work entitled “Sales and Inventory Management System” under my
guidance. I have regularly assessed the progress of the work and suggested
the correction wherever required. The student has incorporated all the
suggestions provided by me in this dissertation. This dissertation is
bonafide piece of work of the standard of BCA project work carried out by
the student under my supervision. Internal examination has been
completed in my presence and student’s performance was satisfactory and
hence this dissertation is approved for the submission and valuation
thereof.
Signature of Guide

Place: Signature of Principal/Director

Date: Seal of the Institute

5|Page
 ACKNOWLEDGEMENT

The satisfaction that accompanies that the successful completion of any

task would be incomplete without the mention of people whose ceaseless
cooperation made it possible, whose constant guidance and
encouragement crown all efforts with success. We are grateful to our
project guide Prof. Sanjay Bohara & Prof. Mirza Naziya Baig for the
guidance, inspiration and constructive suggestions that helpful us in the
preparation of this project. We also thank our colleagues who have helped
in successful completion of the project.

Arzan Bhesania

6|Page
 Table of Contents

S.No. Report

1. Introduction

2. Feasibility Study

3. Data Tables

4. Data Flow Diagrams

5. Entity Relationship
Diagram

6. Screen Shots of Form

7. Visual basic

8. Future Scope

9. Conclusion

10. Bibliography

7|Page
 Sales and Inventory Management
1. Introduction:-

1.1 Purpose:-

The purpose of this application is as follows:

 The software is for automation of sales and inventory management.

 It provides following facilities to

Operator:

 Can enter details related to a sales record.

 Can provide membership to sales men.

Admin:

 Can read and write information about any sales men.

 Can update, create, delete the record of sales men
As per requirement and implementation plants.

2.) Scope:

The different areas where we can use this application

Are:

 Using this software we can reduce costs for warehousing, transportation,

order fulfillment, and material handling – while improving customer service.

8|Page
  Employees can plan, enter, and document warehouse and internal stock
movements by managing goods receipts, goods issues, storage, picking
and packing, physical stock transfers, and transfer postings.

3.) Technology Used:

 Front End : Visual Basic6.0

 Back End: MS Access, My SQL.

4.) Assumptions:

 This application is used to convert the manual

application to the online application.
 Customized data will be used in this application.
 User does have right to enter information
about stock.

5.) Overview:

 Project is related to stock and inventory management which provides

inventory services to its users.

 This system is developed in such a way that even a naive user can also
operate the system easily. The calculations are made very quickly and the
records are directly saved into databases and the databases can be
maintained for a longer period of time. Each record can be retrieved and
can be verified for the future transactions.
 This system helps in tracking records so that past records can be verified
through them and one can make decisions based on the past records. This
system completes the work in a very less time resulting in less time
consumption and high level of efficiency.
9|Page
6.) Functionality:

 Online membership.
 Keeps the track of issued stock and material.

10 | P a g e
 Feasibility Study

As we know each and every project needs to have a feasibility study for the
complete understandability of the project. We will consider 3 types of feasibility
study they are technical feasibility, operational feasibility and economic feasibility.

Technical Feasibility:

This new system requires 6 fully trained people to run the system perfectly.
1 admin person to maintain database n other 5 to handle the system interface
and order making things.

As our existing system is purely manual, so we need a onetime investment of

Rs. 4 Lacks for the purchase of 6 computers, 5 invoice printers, a laser printer,
AC and networking etc. It requires approx. 10 Lacks PA as an operating cost.

With the above details our system is technically feasible as after investing 14
lacks in a year, the company is still saving Rs 15 Lacks PA.

Operational Feasibility:

The new solution is feasible in all sense but operationally it is not. The new
system demands the expulsion of at least 15 people from the company. It creates
an environment of joblessness and fear among the employees. It can lead to an
11 | P a g e
indefinite strike in the company also. So the management must take corrective
actions prior in advance in order to start the further proceedings.

Economic Feasibility:

With the manual system the operating cost of the system is about 60 Lacks
P.A. This cost comprises salary of 25 people, stationary, building rent, electricity,
water, telephone etc. But with the new system this reoccurring cost comes out to
be about 20 Lacks P.A. Hence the new system is economically feasible.

12 | P a g e
 DRAWBACKS OF PRESENT SYSTEM

Some of the problems being faced in manual system are as

Follows:

1. Time consuming

2. Less accurate

3. Less efficient

4. Lot of paper work

5. Slow data processing

6. Not user friendly environment

7. Difficult to keep old records

13 | P a g e
 PROPOSED SYSTEM

Objectives

 The main objective of this system is to keep records of the complete

inventory.

 It support for inventory management helps you record and track materials
on the basis of both quantity and value.

 It improves cash flow, visibility, and decision making.

 For warehouse management, you can track quantity and value of all your
materials, perform physical inventory, and optimize your warehouse
resources

14 | P a g e
 Operating Environment – Hardware and Software

HARDWARE REQUIREMENTS

 Processor: Pentium 4 or more for optimum performance

 RAM: Recommended 256MB
 Hard Disk: Minimum 20GB

SOFTWARE REQUIREMENTS

 Operating System - Certified Distribution of WINDOWS

 Visual Basic 2005 Express Edition
 Database(Backend) - MS Access 2003

15 | P a g e
 User Requirements

FUNCTIONAL REQUIREMENTS

A. INPUT/OUTPUT

1. System shall have a form to accept the customer details.

2. System shall have a form to accept the Plant details.
3. System shall display transaction details.
4. System shall provide search facility on customer name, Order Placed,
date of order, date of order dispatch, date of transaction, transaction
amount, credit card no etc.
5. System should provide facility for change in address/name.
6. System should maintain the details about placing order/dispatch or order
i.e., order status

B. PROCESSING

1. System should automatically generate the bill.

2. System should inform the pending order and make changes if the order
is dispatched.

16 | P a g e
C. ERROR HANDLING

1. Should report any errors on duplicate primary keys.

2. Should report any ‘Out of Range’ values on numeric fields

3. Should report any data type mismatches any field on the forms.

4. Should report on any ‘Invalid dates’

5. Should report any violation of authorization of rights

6. Should report any Invalid Login errors

NON-FUNCTIONAL REQUIREMENTS

1. All user manuals should be provided in the necessary format

2. Application should support 5 simultaneous users.
3. Transaction should be completed within 1/5th of second
4. There will be backup procedure to maintain records.

17 | P a g e
 SYSTEM ANALYSIS
In this chapter, we will discuss and analyze about the developing process of
Sales and Inventory Management including Software Requirement Specification
(SRS) and comparison between existing and proposed system. The functional
and non-functional requirements are included in SRS part to provide complete
description and overview of system requirement before the developing process is
carried out. Besides that, existing vs. proposed provides a view of how the
proposed system will be more efficient than the existing one.

2.1 SOFTWARE REQUIREMENT SPECIFICATION

2.1.1 GENERAL DESCRIPTION

PRODUCT DESCRIPTION:
Sales and Inventory Management system is a computerized system which helps
user (DSR (Dealer Sales Representative)) to manage the sales record and daily
activity in electronic format. It reduces the risk of paper work such as file lost, file
damaged and time consuming.
It can help user to manage the transaction or record more effectively and time-
saving.

PROBLEM STATEMENT:
The problem occurred before having computerized system includes:

 File lost :-
When computerized system is not implemented file is always
lost because of human environment. Sometimes due to some human error there
may be a loss of records. File damaged when a computerized system is not
there file is always lost due to some accident like spilling of water by some
member on file accidentally. Besides some natural disaster like floods or fires
may also damage the files.

18 | P a g e
  Difficult to search record :-
When there is no computerized system there
is always a difficulty in searching of records if the records are large in number.

 Space consuming:-
After the number of records becomes large the
space for physical storage of file and records also increases if no computerized
system is implemented.

 Cost consuming:-
As there is no computerized system to add each
record paper will be needed which will increase the cost for the management of
inventory.

2.1.2 SYSTEM OBJECTIVES

Improvement in control and performance

The system is developed to cope up with the current issues and problems of
inventory .The system can add user, validate user and is also bug free.

Save cost -
After computerized system is implemented less human force will be
required to maintain the inventory thus reducing the overall cost.

19 | P a g e
2.1.3 SYSTEM REQUIREMENTS

2.1.3.1 NON FUNCTIONAL REQUIREMENTS

Product Requirements

EFFICIENCY REQUIREMENT

When a Sales and Inventory Management system will be implemented DSR and
user will easily access searching of inventory and transaction will be very faster.

RELIABILITY REQUIREMENT

The system should accurately perform member registration, member validation,

report generation, book transaction and search.

USABILITY REQUIREMENT

The system is designed for a user friendly environment so that the staff of
management can perform the various tasks easily and in an effective way.

IMPLEMENTATION REQUIREMNTS

In implementing whole system it uses VB in front end with php as server side
scripting language which will be used for database connectivity and the backend
in the database part is developed using MySQL and Access.

DELIVERY REQUIREMENTS

The whole system is expected to be delivered in six months of time with a weekly
evaluation by the project guide

20 | P a g e
2.1.3.2 FUNCTIONAL REQUIREMENTS

1. NORMAL USER
1.1 USER LOGIN

Description of feature
This feature used by the user to login into system. They are required to enter
user id and password before they are allowed to enter the system .The user id
and password will be verified and if invalid id is there user is allowed to not enter
the system.

Functional requirements

-user id is provided when they register

-The system must only allow user with valid id and password to enter the system
-The system performs authorization process which decides what user level can
access to.
-The user must be able to logout after they finished using system.

Functional requirements

-System must be able to verify information

-System must be able to delete information if information is wrong

1.2 REGISTER NEW STOCK

Description of feature

This feature allows adding up of new record in the database.

Functional requirements:-
-System must be able to verify information
-System must be able to enter number of copies into table.

21 | P a g e
1.3 SEARCH CUSTOMER
DESCRIPTION OF FEATURE

This feature is found in Search Customer maintenance part. We can search

customer based on Customer code, customer name, name or by pin code.

Functional requirements
- System must be able to search the database based on select search type
- System must be able to filter book based on keyword entered
- System must be able to show the filtered book in table view

1.4 EVENT ADDITION

DESCRIPTION OF FEATURE

This feature allows DSR to add information about various inventory and stock
being used.

22 | P a g e
Functional requirements-

-System should be able to add detailed information about events.

-System should be able to display information on notice board available in the
homepage of site

2.1.4 SOFTWARE AND HARDWARE REQUIREMENTS

This section describes the software and hardware requirements of the system

2.1.4.1 SOFTWARE REQUIREMENTS

Operating system- Windows 8 is used as the operating system as it is stable

and supports more features and is more user friendly
Database MYSQL-MYSQL and MS Access is used as database as it easy to
maintain and retrieve records by simple queries which are in English language
which are easy to understand and easy to write.
Development tools and Programming language- HTML is used to write the
whole code and develop webpages with css, java script for styling work and php
for sever side scripting.

2.1.4.2 HARDWARE REQUIREMENTS

Intel core i5 2nd generation is used as a processor because it is fast than

other processors an provide reliable and stable and we can run our pc for
longtime. By using this processor we can keep on developing our project without
any worries.
Ram 1 gb is used as it will provide fast reading and writing capabilities and will
in turn support in processing

23 | P a g e
 Data Tables:
UID_PASS (Login Table)

Column Data Size Description

Name Type

USER_NAM Text 50 User name of the

E ADMIN/OPERATOR

PASSWOR Text 50 Password of the

D ADMIN/OPERATOR

customer master (Customer Details Table)

Column Data Size Description

Name Type

cust_slno Num 6 Customer identification

(PK)

cust_name Text 50 Name of the customer

cust_add1 Char 40 Address line one of the customer

cust_add2 Char 40 Address line two of the customer

Cust_add3 Char 40 Address line three of the customer

cust_pincod Num 6 Pin code of the customer address

e

cust_city Char 15 City of the customer

24 | P a g e
contact_per Char 30 Name of the person responsible for
son_name order making

contact_per Num 10 Phone number for the person who

son_name made the order

State code Char 2 Initials of the state derived from state

(FK) details table

state master (State Details table)

Column Data Size Description

Name Type

state code Char 2 Code Of the state eg. MH -

Maharashtra

state Char 50 Description of the code.

description

material master (Material Detail Table)

Column Data Size Description

Name Type

cust_slno Num 6 Customer identification

(PK)

Material_ Char 10 Code of the material

code

Material_ Char 20 Describing the material specification

description

25 | P a g e
shipping_pl Char 4 It gives detail of shipping plant n is
ant linked with plant master table

material_pri Num 10 Price of the material

ce

plant master (Plant Details Table)

Column Data Size Description

Name Type

plant_code Num 6

plant_name Char 10 Code of the material

material_de Char 20 Describing the material specification

scription

shipping_pl Char 4 It gives detail of shipping plant n is

ant linked with plant master table

material_pri Num 10 Price of the material

ce

Plant_add Char 40 Address of plant

Plant_city Char 15 City of plant

Plant_code( Char 15 Code of plant

pk)

status_master (Order Status Master)

26 | P a g e
 Column Data Size Description
Name Type

order_statu Char 4 Status of order in short

s

description Char 50 Description of the plant.

Data Flow Diagram(DFD)

27 | P a g e
 E-R MODEL

28 | P a g e
It is clear that the physical objects from the previous section– the
member, books, library – correspond to entities in the Entity-
Relationship model, and the operations to be done on those entities –
holds, checkouts, and so on –correspond to relationships. However, a
good design will minimize redundancy and attempt to store all the
required information in as small a space as possible.

29 | P a g e
30 | P a g e
31 | P a g e
32 | P a g e
 Snapshots

Login Form

33 | P a g e
Login Successful

34 | P a g e
Main Form

35 | P a g e
Transaction

36 | P a g e
Material Details

37 | P a g e
Plant Detail

38 | P a g e
Order Detail

39 | P a g e
Customer Detail

40 | P a g e
Add Plant

41 | P a g e
Add Customer

42 | P a g e
Add Material

43 | P a g e
Order Status

44 | P a g e
Sales Commission Calculator

45 | P a g e
 Introduction of Front End Tool

Microsoft visual basic (6.0) is the faster and easiest way to create application
form Microsoft Windows operating system.

What is VISUAL BASIC?

The “visual” part refers to the method used to create the graphical user interface
(GUI) rather then the writing numerous lines of code to describe the appearance
and the location of interface element. The “Basic” part refers to the basic
(beginners all purpose symbolic instruction code) language, a language used
widely. Basic language and now contain several hundreds statements, function
and key words many of which related to windows GUI. Beginners can create
useful application by learning just a few keywords, yet the power of language
allows professional to accomplish anything that can be accomplished using any
other windows programming language. The most important aspect of visual basic
is its “event base programming” which provide easy interface with the user and
software.

Visual basic editions:

1. Visual basic learning.

2. Visual basic professional edition.

3. Visual basic enterprise edition

46 | P a g e
 Visual basic

Visual Basic is a third-generation event-driven programming language and

integrated development environment (IDE) from Microsoft for its COM
programming model first released in 1991 and declared legacy in 2008. Microsoft
intended Visual Basic to be relatively easy to learn and use. Visual Basic was
derived from BASIC and enables the rapid application development (RAD) of
graphical user interface (GUI) applications, access to databases using Data
Access Objects, Remote Data Objects, or ActiveX Data Objects, and creation of
ActiveX controls and objects.

A programmer can create an application using the components provided by the

Visual Basic program itself. Over time the community of programmers developed
third party components. Programs written in Visual Basic can also use the
Windows API, which requires external function declarations.

The final release was version 6 in 1998 (now known simply as Visual Basic). On
April 8, 2008 Microsoft stopped supporting Visual Basic 6.0 IDE. The Microsoft
Visual Basic team still maintains compatibility for Visual Basic 6.0 applications on
Windows Vista, Windows Server 2008 including R2, Windows 7, Windows 8,
Windows 8.1, Windows Server 2012 and Windows 10 through its "It Just Works"
program. In 2014, some software developers still preferred Visual Basic 6.0 over
its successor, Visual Basic .NET. In 2014 some developers lobbied for a new
version of Visual Basic 6.0. In 2016, Visual Basic 6.0 won the technical impact
award at The 19th Annual D.I.C.E. Awards.

A dialect of Visual Basic, Visual Basic for Applications (VBA), is used as a macro
or scripting language within several Microsoft applications, including Microsoft

47 | P a g e
Office.

Language feature:-

Like the BASIC programming language, Visual Basic was designed to

accommodate a steep learning curve. Programmers can create both simple and
complex GUI applications. Programming in VB is a combination of visually
arranging components or controls on a form, specifying attributes and actions for
those components, and writing additional lines of code for more functionality.
Since VB defines default attributes and actions for the components, a
programmer can develop a simple program without writing much code. Programs
built with earlier versions suffered performance problems, but faster computers
and native code compilation has made this less of an issue.[citation needed]

Though VB programs can be compiled into native code executables from version
5 on, they still require the presence of around 1 MB of runtime libraries. Core
runtime libraries are included by default in Windows 2000 and later, but extended
runtime components still have to be installed. Earlier versions of Windows
(95/98/NT), require that the runtime libraries be distributed with the executable.

48 | P a g e
 An empty form in Visual Basic 6.

Forms are created using drag-and-drop techniques. A tool is used to place

controls (e.g., text boxes, buttons, etc.) on the form (window). Controls have
attributes and event handlers associated with them. Default values are provided
when the control is created, but may be changed by the programmer. Many
attribute values can be modified during run time based on user actions or
changes in the environment, providing a dynamic application. For example, code
can be inserted into the form resize event handler to reposition a control so that it
remains centered on the form, expands to fill up the form, etc. By inserting code
into the event handler for a keypress in a text box, the program can automatically
translate the case of the text being entered, or even prevent certain characters
from being inserted.

Visual Basic can create executable (EXE files), ActiveX controls, or DLL files, but
is primarily used to develop Windows applications and to interface database
systems. Dialog boxes with less functionality can be used to provide pop-up

49 | P a g e
capabilities. Controls provide the basic functionality of the application, while
programmers can insert additional logic within the appropriate event handlers.

For example, a drop-down combination box automatically displays a list. When

the user selects an element, an event handler is called that executes code that
the programmer created to perform the action for that list item.

Alternatively, a Visual Basic component can have no user interface, and instead
provide ActiveX objects to other programs via Component Object Model (COM).
This allows for server-side processing or an add-in module.

The runtime recovers unused memory using reference counting, which depends
on variables passing out of scope or being set to nothing, avoiding the problem of
memory leaks common to other languages. There is a large library of utility
objects, and the language provides basic object oriented support. Unlike many
other programming languages, Visual Basic is generally not case sensitive—
though it transforms keywords into a standard case configuration and forces the
case of variable names to conform to the case of the entry in the symbol table.
String comparisons are case sensitive by default.

The Visual Basic compiler is shared with other Visual Studio languages (C, C++).
Nevertheless, by default the restrictions in the IDE do not allow creation of some
targets (Windows model DLLs) and threading models, but over the years,
developers have bypassed these restrictions.

50 | P a g e
 SYSTEM TESTING
The aim of the system testing process was to determine all defects in our
project .The program was subjected to a set of test inputs and various
observations were made and based on these observations it will be decided
whether the program behaves as expected or not.
Our Project went through two levels of testing
1. Unit testing
2. Integration testing

UNIT TESTING

Unit testing is undertaken when a module has been created and succesfully
reviewed .In order to test a single module we need to provide a complete
environment in besides the module we would require

The procedures belonging to other modules that the module under test calls
Non local data structures that module accesses
A procedure to call the functions of the module under test with appropriate
parameters

Unit testing was done on each and every module that is described under module
description of chapter 4
1. Test for the admin module

Testing admin login form-This form is used for log in of administrator of the
system. In this we enter the username and password if both are correct
administration page will open otherwise if any of data is wrong it will get
redirected back to the login page and again ask for username and password
Student account addition- In this section the admin can verify student details
from student academics info and then only add student details to main library
database it contains add and delete buttons if user click add button data will be
added to student database and if he clicks delete button the student data will be
deleted

51 | P a g e
 Book Addition- Admin can enter details of book and can add the details to the
main book table also he can view the books requests.

2. Test for Student login module

Test for Student login Form-This form is used for log in of Student .In this we
enter the library id, username and password if all these are correct student login
page will open otherwise if any of data is wrong it will get redirected back to the
login page and again ask for library id, username and password.
Test for account creation- This form is used for new account creation when
student does not fill the form completely it asks again to fill the whole form when
he fill the form fully it gets redirected to page which show waiting for conformation
message as his data will be only added by administrator after verification.
3. Test for teacher login module-
Test for teacher login form- This form is used for login of teacher .In this we
enter the username and password if all these are correct teacher login page will
open otherwise if any of data is wrong it will get redirected back to the login page
and again ask for username and password.

52 | P a g e
INTEGRATION TESTING

In this type of testing we test various integration of the project module by

providing the input .The primary objective is to test the module interfaces in order
to ensure that no errors are occurring when one module invokes the other
module.

White box testing

Sometimes called glass-box testing is a test case design method that uses
the control structure of the procedural design to derive test cases. Using white-
box testing methods, the software engineer can derive test cases that

(1) guarantee that all independent paths within a module have been
exercised at least once,

(2) exercise all logical decisions on their true and false sides,

(3) Execute all loops at their boundaries and within their operational
bounds, and

(4) Exercise internal data structures to ensure their validity.

White-box testing of software is predicated on close examination of procedural
detail. Providing test cases that exercise specific sets of conditions and/or loops
tests logical paths through the software. The “status of the program” may be
examined at various points to determine if the expected or asserted status
corresponds to the actual status. Basis path testing is a white-box testing
technique first proposed by Tom McCabe. The basis path method enables the
test case designer to derive a logical complexity measure of a procedural design
and use this measure as a guide for defining a basis set of execution paths. Test

53 | P a g e
cases derived to exercise the basis set are guaranteed to execute every
statement in the program at least one time during testing.

In this system, the system was tested for the calculation matters were the
data provided for giving the right output or not. If wrong data was provided then
what it is throwing error or accepting.

54 | P a g e
 Black box testing

Also called behavioral testing, focuses on the functional requirements of

the software. That is, black box testing enables the software engineer to derive
sets of input conditions that will fully exercise all functional requirements for a
program. Black box testing is not an alternative to white-box techniques. Rather,
it is a complementary approach that is likely to uncover a different class of error
than white-box methods. When computer software is considered, black box
testing alludes to tests that are conducted at the software interface. Although
they are designed to uncover errors, black-box tests are used to demonstrate
that software functions are operational, that input is

Properly accepted and output is correctly produced and that the integrity of
external information is maintained. A black-box test examines some fundamental
aspect of a system with a little regard for the internal logical structure of the
software. Black-box testing attempts to find errors in the following categories:

1. Incorrect or missing functions,

2. Interface errors,
3. Errors in data structures or external database access,
4. Behavior or performance errors, and
5. Initialization and termination errors. By applying back-box techniques,
we derive a set of test cases that satisfy the following criteria:
a. Test cases that reduce, by a count that is greater than one, the
number of additional test cases that must be designed to achieve reasonable
testing and
55 | P a g e
 b. Test cases that tell us something about the presence or absence
of classes of errors, rather than an error associated only with the specific test at
hand.
White-box testing should not, however, be dismissed as impractical. A
limited number of important logical paths can be selected and exercised.
Important data structures can be probed for validity. The attributes of both black
and white box testing can be combined to provide an approach that validates the
software interface and selectively ensures that the internal workings of the
software are correct.

Black box testing for this system was done to check the internal testing i.e,
the system is working properly in each case or no. What kind of errors are there
in database design.

56 | P a g e
 FUTURE SCOPE OF APPLICATION :
This application can be easily implemented under various situations.
We can add new features as and when we require. Reusability is
possible as and when require in this application. There is flexibility
in all the modules.

SOFTWARE SCOPE:

 Extensibility: This software is extendable in ways that its original

developers may not expect. The following principles enhances
extensibility like hide data structure, avoid traversing multiple
links or methods, avoid case statements on object type and
distinguish public and private operations.

 Reusability: Reusability is possible as and when require in this

application. We can update it next version. Reusable software
reduces design, coding and testing cost by amortizing effort
over several designs. Reducing the amount of code also
simplifies understanding, which increases the likelihood that
the code is correct. We follow up both types of reusability:
Sharing of newly written code within a project and reuse of
previously written code on new projects.

 Understand ability: A method is understandable if someone other

than the creator of the method can understand the code (as
well as the creator after a time lapse). We use the method,
which small and coherent helps to accomplish this.

 Cost-effectiveness: Its cost is under the budget and make within

Given time period. It is desirable to aim for a system with a
minimum cost subject to the condition that it must satisfy the
entire requirement.

57 | P a g e
  Databases for different products range and storage can be provided.
 Multilingual support can be provided so that it can be understandable by
the person of any language.

 More graphics can be added to make it more user-friendly and

understandable.

Manage & backup versions of documents online

58 | P a g e
 Conclusion
From a proper analysis of positive points and constraints on the
component, it can be safely concluded that the product is a highly efficient GUI
based component. This application is working properly and meeting to all user
requirements. This component can be easily plugged in many other systems.
While developing the system a conscious effort has been made to create and
develop a software package, making use of available tools, techniques and
resources – that would generate a proper System While making the system, an
eye has been kept on making it as user-friendly, as cost-effective and as flexible
as possible. As such one may hope that the system will be acceptable to any
user and will adequately meet his/her needs. As in case of any system
development processes where there are a number of shortcomings, there have
been some shortcomings in the development of this system also. The project is
still under modification

59 | P a g e
 Bibliography & References

 http://www.w3schools.com/html/html_intro.asp
 http://www.w3schools.com/css/css_background.asp
 http://www.w3schools.com/js/js_datatypes.asp
 http://www.w3schools.com/sql/sql_insert.asp
 http://www.w3schools.com/sql/sql_update.asp
 http://www.w3schools.com/php/php_forms.asp
 Fundamentals of software engineering by Rajib mall, PHIlearning
 Web development and application development by Ivan Byross BPB
publications

60 | P a g e
61 | P a g e