Navigation ...
|
|
|
Scientific Writing ...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Other Writing ...
|
|
|
|
|
|
Reference details
| Author(s)
| Year
| Title
| Reference
| View/Download
|
Les Hatton | 1999b | Repetitive failure, feedback and the lost art of diagnosis | Journal of Systems and Software, (10) | Diag_JSS1099.pdf |
Synopsis and invited feedback
This work was reviewed and accepted by domain-specific experts appointed independently.
If you would like to provide feedback just e-mail me here.
| Synopsis
| Invited Feedback
| Importance (/10, author rated :-) )
|
| After discussing the role of control process feedback in conventional engineering, this paper shows how this is almost completely absent for what we do in software engineering. The paper closes by stressing the following engineering obligations:- a) Handle system failure as a design issue. The system will fail so plan for it.
b) When the system fails, make sure it fails with as little impact on its users as possible.
c) When the system fails, make sure that the diagnostic information is sufficient to identify why the system failed quickly. | None yet | 6 |
Related links
| Related papers and links
|
| Sorry, no links registered in database yet. |
Auto-generated: $Revision: 1.43 $, $Date: 2008/03/03 23:38:56 $, Copyright Les Hatton 2001-
|
