crash concept from the Object Oriented Software Engineering knowledge base

Object Oriented Software Engineering View all facts Glossary Help

Next failure: deadlock or livelock Up: failure

crash

subject fact

crash is a subtopic of 10.2 - Effective and Efficient Testing 2001-08-30 14:55:08.0
is a kind of failure

failure can be the result of a violation of an implicit requirement 2001-08-30 14:55:35.0
has example the production of incorrect outputs, the system running too slowly, or the user having trouble finding online help
is usually the result of a violation of those requirements that are stated explicitly in a requirements document
may arise from violations of either functional requirements or non-functional requirements 2001-08-30 14:55:35.0
may be cause by several defects working together

problem has solution which will normally entail developing software, although you may decide that it is better to purchase software or to develop a non-software solution 2001-08-30 14:57:03.0
should be written as a simple problem statement in one or two sentences

crash	is a subtopic of 10.2 - Effective and Efficient Testing
crash	is a kind of failure
failure	can be the result of a violation of an implicit requirement
	has example the production of incorrect outputs, the system running too slowly, or the user having trouble finding online help
	is usually the result of a violation of those requirements that are stated explicitly in a requirements document
	may arise from violations of either functional requirements or non-functional requirements
	may be cause by several defects working together
problem	has solution which will normally entail developing software, although you may decide that it is better to purchase software or to develop a non-software solution
problem	should be written as a simple problem statement in one or two sentences