![]() |
subject > problem > defect > hung system |
![]() ![]() | ||||
hung system | ||||
subject | fact |
hung system | has definition 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 | ![]() |
is a subtopic of 10.5 - Defects in Timing and Co-Ordination: Deadlock, Livelocks and Critical Races | ![]() | |
is a kind of defect | ![]() | |
is a kind of software system | ![]() | |
may be caused by | ![]() | |
defect | has example the absence of code to handle an exception | ![]() |
software system | becomes 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 | ![]() |
can automate business process | ![]() | |
can be divided in many ways:
| ![]() | |
is better at error handling if it effectively prevents the user from making errors, detects errors, and helps the user to correct errors | ![]() | |
is typically initially developed as a prototype | ![]() | |
must have well-described requirements if other systems or subsystems are going to use its services or communicate with it | ![]() | |
should be designed for flexibility right from the start | ![]() | |
undergoes evolution over its life-span | ![]() | |
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 | ![]() |
should be written as a simple problem statement in one or two sentences | ![]() | |
system | can have specification which is then implemented by a collection of components | ![]() |
exists even if its components change over the course of time, or are replaced by equivalent components | ![]() | |
has scope | ![]() | |
has part component | ![]() | |
has part hardware | ![]() | |
has part module | ![]() | |
has part software | ![]() | |
has part subsystem | ![]() | |
is divided up into subsystems | ![]() |
Next defect: timing and co-ordination defect Up: defect, software system Previous defect: documentation defect