Forced-Error Test (FET)
Error-handling design and communication methods consistency
Detection and handling of common error conditions
System recovery from each error condition
Correction of unstable states caused by errors
– Accessibility: Can users enter, navigate, and exit the system with relative ease?
– Responsiveness: Can users do what they want, when they want, in an intuitive/convenient way?
– Efficiency: Can users carry out tasks in an optimal fashion with respect to time, number of steps, etc.?
– Comprehensibility: Can users quickly grasp how to use the system, its help functions, and associated documentation?
Collect data to improve usability of system
supporting system functions
Change procedures (for various adaptive, perfective, and corrective service scenarios)
All system diagnostic tools
Evaluate compliance to specified performance requirements (i.e. throughput, I/O rates, etc.)
Looks for resource bottlenecks
Pushes system to failure
Hardware: processor, memory
Operating system: type, version
Run-time environments: JRE,. NET
compatibility with other system resources in operating environment
to unauthorized access
Integrity/ Confidentiality/ Availability
Network computing resources
How long systems are expected to function
How long they can operate without exhibiting faults
How long between maintenance intervals are all important considerations
-Example: in release 4 of software, verify that all (unchanged) functionality of version 1,2, and 3 still work
–One of the most frequent occasions when System faults are introduced is when the hardware or software is modified