Testing:

The testing phase is an important part of software development. It is the process of finding errors
and missing operations and also a complete verification to determine whether the objectives are
met and the user requirements are satisfied.

Software testing is carried out in three steps:

The first includes unit testing, where in each module is tested to provide its correctness,
validity and also determine any missing operations and to verify whether the objectives have
been met. Errors are noted down and corrected immediately. Unit testing is the important and
major part of the project. So errors are rectified easily in particular module and program clarity is
increased. In this project entire system is divided into several modules and is developed
individually. So unit testing is conducted to individual modules.
The second step includes Integration testing. It need not be the case, the software whose
modules when run individually and showing perfect results, will also show perfect results when
run as a whole. The individual modules are clipped under this major module and tested again and
verified the results. This is due to poor interfacing, which may results in data being lost across an
interface. A module can have inadvertent, adverse effect on any other or on the global data
structures, causing serious problems.
The final step involves validation and testing which determines which the software
functions as the user expected. Here also some modifications were. In the completion of the
project it is satisfied fully by the end user. They are different levels of testing.

Unit Testing:

This is the first level of testing where different modules are tested against the
specifications produced during design for the modules. The goal is to test the internal logic of the
modules
Integration Testing:

The testing is systematic technique for constructing a program structure, we see whether the
modules can be integrated properly. There are two approaches.

1. Top Down Integration:

Modules are integrated by moving downward beginning with the main program, the
subordinate modules coming to structure in either breadth first or depth first manner.

2. Bottom Up Integration:

This begins construction and testing in automatic modules. The modules are integrated from
bottom up; sub ordinates to the modules at given level are always available. The needs for stubs
are eliminated.

System Testing:

This testing consists of tests that will closely approximate the acceptance test.First, the black
box test cases for the product as a whole must be run.Second the robustness of the product as a
whole must be tested. In addition the product must be subjected to stress testing &volume
testing.
Third, we must check if the product satisfies all constraints like storage and security.Fourth, we
must review the documentation that is handed over to the client along with the code. Once the
product testing is completed, the product is handed over to the client for acceptance testing.

Acceptance Testing:

The purpose of this testing is for the client to determine whether the product indeed
satisfies it's specifications as claimed by the developer. This testing is done either by the client
organization, by the SQA group hired by the client for this purpose.
Four major components of Acceptance testing are:

 Testing correctness.
 Robustness.
 Performance.
 Documentation

A key aspect of this testing is that it must perform on actual data rather than on test data. When
the product has passed its acceptance test, the task of the developers is complete. Any changes
now made to that product constitute maintenance.

Implementation:

We are using Ms.net platform and the technologies we are using are vb.net.
Other software’s we are using are
 SQL SERVER (Backend)