Object Oriented Software Engineering   View all facts   Glossary   Help
subject > problem > defect > defect in handling stress and unusual situations > defect in handling peak loads or missing resources
Next defect in handling stress and unusual situations: inappropriate management of resources    Up: defect in handling stress and unusual situations    Previous defect in handling stress and unusual situations: insufficient throughput or response time on minimal configurations   

defect in handling peak loads or missing resources
subjectfact 
defect in handling peak loads or missing resourceshas definition A defect that occurs when a computer cannot gracefully handle peak loads or missing resources2001-08-30 14:55:12.0
has testing strategy
  • deny the program under test the resources it normally uses, by employing such methods as deleting files, concurrently running other resource-hungry programs, making less memory available, or disconnecting the system from the network
  • run a very large number of copies of the program being tested, all at the same time
2001-08-30 14:55:12.0
is a subtopic of 10.6 - Defects in Handling Stress and Unusual Situations2001-08-30 14:55:12.0
is a kind of defect in handling stress and unusual situations2001-08-30 14:55:12.0
occurs when
  • a computer becomes short of resources such as memory, disk space or network bandwidth
  • files or data are missing
  • the system is not permitted to perform certain operations
  • the system cannot start new threads
  • the system runs out of space in a fixed size data structure
2001-08-30 14:55:12.0
defect in handling stress and unusual situationscan be detected by
  • running the system intensively
  • suppling the system with a very large amount of input
  • running many copies of the system
  • running the system on a computer or network that is busy running other systems
  • running the system in atypical environments
2001-08-30 14:55:12.0
is only encountered when a system is being heavily used, or forced to its limits in some other way2001-08-30 14:55:12.0
represents a lack of robustness2001-08-30 14:55:12.0
defecthas example the absence of code to handle an exception2001-08-30 14:55:12.0
problemhas solution which will normally entail developing software, although you may decide that it is better to purchase software or to develop a non-software solution2001-08-30 14:57:03.0
should be written as a simple problem statement in one or two sentences2001-08-30 14:57:03.0