timing and co-ordination defect Comparison Table

Object Oriented Software Engineering View all facts Glossary Help

subject > problem > defect > timing and co-ordination defect

Next defect: defect in a numerical algorithm Up: defect Previous defect: hung system

timing and co-ordination defect comparison table

Subject have solution have example occur has definition have black-box testing strategy be write as is a subtopic of is a synonym of is a kind of detect by occur in

critical race which will normally entail developing software, although you may decide that it is better to purchase software or to develop a non-software solution the absence of code to handle an exception when several threads or processes interact in inappropriate ways A defect in which one thread or process can sometimes experience a failure because another thread or process interferes with the 'normal' sequence of events
Vary the time consumption of different threads by giving them differing amounts of input, or running them on hardware that varies in speed
Run a large number of threads concurrently
Deliberately deny resources to one or more threads (e.g. temporarily cut a network connection, or make a file unreadable)
hard to detect with black box testing alone since you often don't know the extent of the concurrency going on inside the system, and can not always manipulate the various threads to cause race conditions a simple problem statement in one or two sentences 10.5 - Defects in Timing and Co-Ordination: Deadlock, Livelocks and Critical Races race condition timing and co-ordination defect inspection a situation involving some form of concurrency

Subject	have solution	have example	occur	has definition	have black-box testing strategy	be	write as	is a subtopic of	is a synonym of	is a kind of	detect by	occur in
critical race	which will normally entail developing software, although you may decide that it is better to purchase software or to develop a non-software solution	the absence of code to handle an exception	when several threads or processes interact in inappropriate ways	A defect in which one thread or process can sometimes experience a failure because another thread or process interferes with the 'normal' sequence of events	Vary the time consumption of different threads by giving them differing amounts of input, or running them on hardware that varies in speed Run a large number of threads concurrently Deliberately deny resources to one or more threads (e.g. temporarily cut a network connection, or make a file unreadable)	hard to detect with black box testing alone since you often don't know the extent of the concurrency going on inside the system, and can not always manipulate the various threads to cause race conditions	a simple problem statement in one or two sentences	10.5 - Defects in Timing and Co-Ordination: Deadlock, Livelocks and Critical Races	race condition	timing and co-ordination defect	inspection	a situation involving some form of concurrency

Next defect: defect in a numerical algorithm Up: defect Previous defect: hung system