hung system Comparison Table

Object Oriented Software Engineering View all facts Glossary Help

subject > problem > defect > hung system

Next defect: timing and co-ordination defect Up: defect, software system Previous defect: documentation defect

hung system comparison table

Subject cause by have design for be have specification is a kind of is a synonym of is a subtopic of write as have example become undergo divide develop as has part divide up into has definition automate have solution exist

defect problem bug 10.1 - Basic Definitions a simple problem statement in one or two sentences the absence of code to handle an exception A flaw in any aspect of the system including the requirements, the design or the code, that contributes, or may potentially contribute, to the occurrence of one or more failures which will normally entail developing software, although you may decide that it is better to purchase software or to develop a non-software solution

software system well-described requirements if other systems or subsystems are going to use its services or communicate with it flexibility right from the start better at error handling if it effectively prevents the user from making errors, detects errors, and helps the user to correct errors which is then implemented by a collection of components system 1.9 - Difficulties And Risks In Software Engineering as a Whole complex because it is easy to add new features and because software engineers typically add features without fully understanding a system, which may not have been originally designed to accommodate the features evolution over its life-span in many ways:
A distributed system is divided up into clients and servers
A system is divided up into subsystems
A class is divided up into methods
a prototype subsystem subsystems business process even if its components change over the course of time, or are replaced by equivalent components

hung system
deadlock
livelock
a single thread waiting for an unavailable resource
an infinite loop
a crash
well-described requirements if other systems or subsystems are going to use its services or communicate with it flexibility right from the start better at error handling if it effectively prevents the user from making errors, detects errors, and helps the user to correct errors which is then implemented by a collection of components software system 10.5 - Defects in Timing and Co-Ordination: Deadlock, Livelocks and Critical Races a simple problem statement in one or two sentences the absence of code to handle an exception complex because it is easy to add new features and because software engineers typically add features without fully understanding a system, which may not have been originally designed to accommodate the features evolution over its life-span in many ways:
A distributed system is divided up into clients and servers
A system is divided up into subsystems
A class is divided up into methods
a prototype subsystem subsystems A system that appears to the user to not be doing anything, caused by such things as a crash, a deadlock, a livelock or an infinite loop business process which will normally entail developing software, although you may decide that it is better to purchase software or to develop a non-software solution even if its components change over the course of time, or are replaced by equivalent components

Next defect: timing and co-ordination defect Up: defect, software system Previous defect: documentation defect

Subject	cause by	have	design for	be	have specification	is a kind of	is a synonym of	is a subtopic of	write as	have example	become	undergo	divide	develop as	has part	divide up into	has definition	automate	have solution	exist
defect						problem	bug	10.1 - Basic Definitions	a simple problem statement in one or two sentences	the absence of code to handle an exception							A flaw in any aspect of the system including the requirements, the design or the code, that contributes, or may potentially contribute, to the occurrence of one or more failures		which will normally entail developing software, although you may decide that it is better to purchase software or to develop a non-software solution
software system		well-described requirements if other systems or subsystems are going to use its services or communicate with it	flexibility right from the start	better at error handling if it effectively prevents the user from making errors, detects errors, and helps the user to correct errors	which is then implemented by a collection of components	system		1.9 - Difficulties And Risks In Software Engineering as a Whole			complex because it is easy to add new features and because software engineers typically add features without fully understanding a system, which may not have been originally designed to accommodate the features	evolution over its life-span	in many ways: A distributed system is divided up into clients and servers A system is divided up into subsystems A class is divided up into methods	a prototype	subsystem	subsystems		business process		even if its components change over the course of time, or are replaced by equivalent components
hung system	deadlock livelock a single thread waiting for an unavailable resource an infinite loop a crash	well-described requirements if other systems or subsystems are going to use its services or communicate with it	flexibility right from the start	better at error handling if it effectively prevents the user from making errors, detects errors, and helps the user to correct errors	which is then implemented by a collection of components	software system		10.5 - Defects in Timing and Co-Ordination: Deadlock, Livelocks and Critical Races	a simple problem statement in one or two sentences	the absence of code to handle an exception	complex because it is easy to add new features and because software engineers typically add features without fully understanding a system, which may not have been originally designed to accommodate the features	evolution over its life-span	in many ways: A distributed system is divided up into clients and servers A system is divided up into subsystems A class is divided up into methods	a prototype	subsystem	subsystems	A system that appears to the user to not be doing anything, caused by such things as a crash, a deadlock, a livelock or an infinite loop	business process	which will normally entail developing software, although you may decide that it is better to purchase software or to develop a non-software solution	even if its components change over the course of time, or are replaced by equivalent components