System testing is actually a series of different tests whose primary purpose is to fully exercise the computer-based system. although each test has a different purpose, all work to verify that system elements have been properly integrated and perform allocated functions
"System testing" is to check whether or not the system is working properly. If the system is working well enough, we can proceed to further steps which is usually 'Implementation'. Testing can be at any stage and any number of times. Testing times, durations and counts depend on the 'architecture' or 'model' of the system being made. I suggest, you learn a few basic things about 'software modelling' or 'system modelling'.
There are four types of system testing:
1. Recovery testing:
It is a system test that forces the software to fail in a variety of ways and verifies that recovery is properly performed. If recovery is automatic, reinitialization, check-pointing mechanisms, data recovery, and restart are evaluated for correctness. If recovery requires human intervention, the mean-time-to-repair (MTTR) is evaluated to determine whether it is within acceptable limits.
2. Security testing:
It attempts to verify that protection mechanisms built into a system will, in fact, protect it from improper penetration. The system security must, of course, be tested for invulnerability from frontal attack-but must also be tested for invulnerability from flank or rear attack.
3. Stress testing:
It executes a system in a manner that demands resources in abnormal quantity, frequency, or volume. It is sometimes called as sensitivity testing.
4. Performance testing:
This often coupled with stress testing and usually require both hardware and software instrumentation.
Implementation: You software or package is now ready, and now you need to release it so that client or users can use it. To make your project live for using is implementation of the system.
performing a sytem testTesting is done all the way in system development. It is meant to turn up any unkown problem. Not to demonstrate the perfection of a program's manual or equipment. Though it is tediou, its help to assure the quality of the ventual system.
Stages of testing
1. Unit Testing
This involves testing of each individual module with test data to see if it's works as planned
2. Intergration testing
It's consist of intermodules and interprogram linkage test and program function
3. System test
The overal function perfomance of the system is tested. It checks the system for validity of the overal function and performance. The test results help to determine the time to initiate the service( This is usually conducted by the software developer)
4. Operational test
It's done in the actual operating environment to make a fined check to see if newly completed system is capable of actual operation. Mainly conducted by users who also see if the system has been exactly as per their expectation.
The analyst process an accurate assessment of the users that must be trained. The training strategic to be used to depend on who to be trained and who will train them.
Who to train
All the people who have the primary/secondary use of the system. It goes to the data entry personel to all the system users even those who will not come to contact with the hardware. The amount of training depend on how much one job will change because of the new system. Users of different key level and job difference must be seperated.
Below are some of training guidelines
- Establish measurable objectives
- Use appropiate training methods
- Select suitable training site
- Employee understandable training material
Types of system change over
- Direct change over
- Parallel change over
- Gradual change over
This means on a specified date the old system is dropped and replace witha new system
- Long delays might occur since there is no possibility of reverting
- Users may reside to use unfarmiliar system
- There is no adequate way to compare new and old system
It refers to the running of an old and new system at the sametime. Once the new system is proved reliable, the old system is drop.
- There is more security when the new system fails then your can revert to the new system
- There is adequate way to compare new and old systemb
- Expensive to run both two system at the same time
- Very difficult to compare the out together
- It's attempt to combine the best features of direct and parallel change over without carrying the direct link. The volume of transaction is gradually increased as the system is face out.
- Users can get a custom to the new system gradually
- Theposibility of detecting and recovery of errors without loosing a lot of time
- It's too long to get the new system in place
- Cannot be applied on large scale organization