MinimizeHumanIntervention
@ Fault Tolerant Patterns.Architectural Patterns
EVA Community Ji-won Kim([email protected]) 2013.8.24
Intent : People make mistakes and are slow; to minimize downtime the system should take care of itself, without human intervention.
2
Story Line
Human is not a god
Prevent human from going wrong way
Hardware and Software is innocent
Communication
Debug?, Dehuman! On ( ? )
Incomplete Human
50%~
25%
25%
The cause of failures
Human Hardware
Software
(From a study of the US telephone network[Kuh97])
Human can do every-thing
Recognition/Report
Fix/Modification Analysis Destruction
Test/ PlanningOperation
5
Human's Creation
Network
ComputingMachine
Math
Switch
Human is not a machine
AlwaysIdentical ProceduralSoftware&Hardware
Become Bored, inattentive with routine, monotonous tasks
So~? Give them all
Con-trol
Self Recovery
Automatic Error-HandleDetection->Processing
7
What’s the Prob-lem?
The risk of Procedural Errors
Incorrect system from imperfect Human’s
Requirements
Operator
Whole System
Implementation &Operation
If it’s already planned and predictable, make it all automatic
8
Fault Observe
r
Monitoring System
Component1 Component2
Component3
Fault Observe
r
Fault Observe
r
RecoverySystem
Operator
Benefit
Fast Response time for Error situationQuickly Recover ErrorsAvoid this
From Book, originally from©iStockphoto.com/Don Bayley
Pattern Relation
Minimize Human In-tervention
Detection• Fault Ob-
server• Audible
Alarm
Recovery• Recovery
Blocks• Error Han-
dlers• Maximize
Human Par-ticipation
Management• Mainte-
nance In-terfaces
• IO Triage
Prevention& Correct• Reintegra-
tion• Revise Pro-
cedure
Helpful Patterns :An Input and Output Pattern Language [HS00]
Risk?
Mis-operation Windows System Recovery
Top Related