1 TESTING AND DEBUGGING


1.1 TESTING


In the Payroll System, testing that had done is based on a regression technique split into several major focuses, namely internal, unit, application, and stress.

a) Internal Testing

b) Unit Testing

c) Application Testing

d) Stress Testing

In this system, all type of testing will be used. The testers that involve in these tests are:

a) Programmer - Person that responsible to develop the system.

b) Customer - Person that request on system development.

c) Outside Expertise - Person that had more experience in develop the same system.


After the programmer test the module one by one and the whole system, programmer need to identify errors or bug in this system. There is some example of error or bug that has been identified:

a) The expecting results not same with the theory result.

b) Some button not functioning.

c) The button link to the wrong interface.

d) The data that had been saved not write in the database.

e) The coding of the module is incorrect.



1.2 DEBUGGING



In Payroll System, debugging process also will be held module by module. This process will be done by the programmer. The programmer will use a tool calls debuggers to detect bug or defects. Debuggers are software tools which enable the programmer to monitor the execution of a program, stop it, re-start it and set breakpoints.

For Payroll System, Visual Basic 6.0 had been used to develop the interface and all the function. With this application, the bug or defect will automatically detect by debugger tool. Programmer also can run, pause or stop the system anytime if they need whether the module finished or not. So, they can detect the bug or defect easily.




2 CORRECTION AND MAINTENANCE


2.1 CORRECTION


In this system, programmer need to make some corrections if there is error or bug occurs. This correction will be done according to the error or bug found. The examples of the correction done in this system are shown below:

a) The expecting results not same with the theory result.
- Programmer had changed the coding for the calculation.

b) Some button not functioning.
- Programmer had added the coding to the button.

c) The button link to the wrong interface.
- Programmer had changed the link to the correct interface.

d) The data that had been saved not write in the database.
- Programmer had checked the connection to database.
- Programmer had changed the correct to input the data to database.

e) The coding of the module is incorrect.
- Programmer had changed the correct right coding
- Programmer had run the module until the module run correctly and follows the user requirement.


2.2 MAINTENANCE


The examples of the maintenance that we provide to the customer are shown below:

a) Add new function to the system.

b) Change the calculation coding if required.

c) Add new module to the system.

d) Make improvement to the system. E.g.: Online system.

e) Compress the module or function if customer does not need it anymore.

f) Correct the failure of the system.

g) Change the interface according to customer satisfaction and make it more users friendly.

Report by : Muhamad Mujahid, Leader 3dishess