6.

SYSTEM TESTING
AND VALIDATIONS
6. SYSTEM TESTING AND VALIDATIONS

IMPLEMENTATION DESCRIPTION
LOGIN MODULE
The login module is the very first and the most common module in all applications. In
the suggested system only registered users will be allowed to login the system the unauthorized
users will be unable to login. Registered users with their username and password only being
correct will moved on to the next page. Or else they will be unable to login.

REGISTRATION MODULE
Registration is one of the primary modules in any data management system. A complaint
must be registered for it to be processed furthering the proposed system the end users are allowed
to register their complaints by filling in all the required details needed to take action for the given
request. If all the fields have been filled and if the submit button was clicked the user gets a pop
up message telling that their complaints were registered successfully. So the registration module
is an important module in a program.

UPDATE STATUS MODULE

Update module is also a primary module which is mostly used by an admin to update
the status or events. Update is used to provide the user with up to date information’s. In the
suggested system the admin updates the status of a request by selecting the particular request id
for which the status must be updated. A pop up message is shown telling the user that the
complaint status was successfully updated.

VIEW MODULE
The view module is generally used to view a list of items which has been displayed in
the database table. We use a data grid view to view a list of items from the table. In the suggested
system the user views the status and events of the request updated by the admin by a
datagridview in just a click of a button. The admin also has a datagridviews to view all the
complaints registered and the feedback given by the end users.
PROCESS MODULE
A process module is generally used to list or count something as a whole. In the
suggested system the process is that all the number of complaint status that has been given by the
admin will be viewed in just a press of a button, so that the admin can cross check with the
number of complaints registered and the number of status updated.

TESTING METHODOLOGY-
FUNCTIONAL TESTING

Unit Testing Integration System Acceptance

Testing Testing Testing

NON FUNCTIONAL TESTING

Performance Security Usability Compatibility

Testing Testing Testing Testing

UNIT TESTING:
The Unit Testing is part of a testing methodology in the testing of individual software
modules or components that make up an application or system.
In the above system unit testing focuses on testing each individual modules. This test
detects errors in coding and logic within each program. Each module is checked for its
consistency.

INTEGRATION TESTING:
The Integration Testing is the testing of the different modules/components that have been
successfully unit tested when integrated together to perform specific tasks andactivities (also
known as scenario testing).
In the above system integration testing is done for all the modules that are integrated and
the entire software is tested for serial addition and expected validations. The integration strategy
dictates the order in which modules must be available and thus exerts a strong influence on the
order in which the modules are written, debugged and unit tested.

SYSTEM TESTING:
The System Testing involves testing the entire system for errors and bugs. This test is
carried out by interfacing the hardware and software components of the entire system (that have
been previously unit tested and integration tested), and then testing it as a whole.
In the above system the unit testing and integration testing has been successfully tested.
Next comes system testing, here instead of checking each and every module separately we are
going to test the entire project as a whole and detect errors if any.

ACCEPTANCE TESTING:
The Acceptance Testing is the final phase of functional software testing and involves
making sure that all the product/project requirements have been met and that the end users and
customers have tested the system to make sure it operates as expected and meets all their defined
requirements.
In the above system all the other testing has been satisfied. This is the final phase of the
testing process and the suggested system takes care of all the requirements suggested by the
customers and it satisfies with all the requirements suggested by the customers.