Testing is vital to the success of the system. System testing makes a logical assumption that if all the parts of the system are correct, the goal will successfully achieved. Inadequate testing or contesting leads to errors t may not appear until months later. This creates two problems: (1) the time lag between the cause and the appearance of the problem (the longer time interval, the more complicated the problem has become), and (2) the effect of system errors on files and records within the system. A small system error can conceivably explode into a much larger problem. Effective testing early in the process translates directly into long-term cost savings from a reduced number of errors.
Another reason for system testing is its utility as a user-oriented vehicle before implementation. The best program is worthless if it does not meet user needs. Unfortunately, the user demands are often compromised by efforts to facilitate program or design efficiency in terms of processing time or memory utilization. Often the computer technician and the user have communication barriers due to different backgrounds, interests, priorities, and perhaps languages. The system tester (designer, programmer, or user) who has developed some computer mastery can bridge this barrier.
No comments:
Post a Comment