Scribd
Upload
94 views

Development and Testing: Done By: Anwaar Al-Hajri Grade:12/b School: Madinat Al-Sultan Qaboos

The document summarizes the key stages in developing and testing a system: creating the system, testing the system, and improving the system based on test results. It describes strategies for testing like creating a test plan with normal, extreme, and abnormal test data and expected versus actual results. An example test plan for a payroll system is provided to demonstrate different types of test data and how the system should respond. Live data from existing systems is also used for testing. Finally, any faults identified during testing would be used to improve the system before implementation.

Uploaded by

picmin
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
94 views

Development and Testing: Done By: Anwaar Al-Hajri Grade:12/b School: Madinat Al-Sultan Qaboos

The document summarizes the key stages in developing and testing a system: creating the system, testing the system, and improving the system based on test results. It describes strategies for testing like creating a test plan with normal, extreme, and abnormal test data and expected versus actual results. An example test plan for a payroll system is provided to demonstrate different types of test data and how the system should respond. Live data from existing systems is also used for testing. Finally, any faults identified during testing would be used to improve the system before implementation.

Uploaded by

picmin
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 12

Development and testing

Done by: Anwaar al-hajri Grade:12/b School: Madinat Al-Sultan Qaboos

Introduction

Designing a system requires three stages:


Creating the system Testing the system Improving the system

The second and third stages may be repeated due to the first stage being altered because of change in test results. So they will be repeated until the system is complete.

Creating data structures and program modules

The data structures that have been designed will be created using the software or programming language recommended by system analyst. The programmer will produce the program code to solve the problem. The nature of the problem will determine the amount of programming needed.

Testing strategies

To make sure the system works, a test plan is produced by the system analyst. The test plan includes: List of test data Expected results Actual results Comment on differences between actual results and expected results.

Test data

There are three types of test data: Normal data: the data that is acceptable or valid to the system. Extreme data: only used where a range of data is input. Abnormal data: the data which is not acceptable or valid to the system.

Normal data

This type of data should not produce error messages from the system. Example: In a payslip nobody works for more than 65 hours in a week, and the lowest number of hours is zero if the worker is ill. The normal data would be any number between 0 and 65, including 0 and 65. If these types of data produced error messages then there is a problem with the system.

Extreme data

Names and addresses can not be extreme data because they have no ranges. Extreme data are the values at either ends of the acceptable range. Example: In the payslip example the extreme data would be 0 and 65 only.

Abnormal data

Abnormal data include letters when entered in a numeric field. Where a range of numbers is used abnormal data would be numbers outside the range or letters. Example: In the payslip example abnormal data would be -1, 66, 140 or Reem.

Example of test plan for the payslip example


Test Test data
-1 65

Expected results
Rejected Accepted Accepted Accepted Rejected Rejected

Actual results
Error message Wages calculated Wages calculated but result was 0 Wages calculated Error message Error message

comment
Abnormal data- the system worked as expected Extreme data- the system worked as expected Extreme data- the system worked as expected Normal data- the system worked as expected Abnormal data- the system worked as expected Abnormal data- the system worked as expected

Input hours worked 0

40 140 Reem

Live data

Live data are those that have been used in the existing system. It will be used because the outputs are already known. The original output will be compared with the output that the new system has produced, if the outputs dont match amendments will be made for the new system

Improvements that could be needed as a result of testing

The next step is to correct any mistakes before the system is implemented. The analyst will correct any faults that were identified as a result of testing. The test plan should help in identifying the faults since it shows the difference between expected and actual results. If faults can still not be identified the next step is to see where and when the differences occurred which can be achieved using a process called single stepping.

The End

You might also like