Drift Correction (glossary)
A resilience design principle that states that the drift of a system into a region of increasing risk should be monitored and appropriate responses should be formulated and executed – adapted from (Leveson et al. 2006)
In a resilience context according to Jackson and Ferris (2013) drift correction is a component principle of the adaptability grouping.
Leveson, N., N. Dulac, D. Zipkin, Cutcher-Gershenfeld, J. Carroll, and B. Barrett. 2006. "Engineering Resilience into a Safety-Critical System." In Resilience Engineering: Concepts and Precepts, edited by E. Hollnagel, D. D. Woods and N. Leveson. Aldershot, UK: Ashgate Publishing Limited.
Jackson, Scott, and Timothy Ferris. 2013. "Resilience Principles for Engineered Systems." Systems Engineering 16 (2):152-164.
This is a key resilience design principle. Although the definition above implies a gradual drift into a high risk state, it can also be interpreted to imply an immediate impending danger as was done by (Jackson 2010).
Jackson, S. 2010. Architecting Resilient Systems: Accident Avoidance and Survival and Recovery from Disruptions. Edited by A. P. Sage, Wiley Series in Systems Engineering and Management. Hoboken, NJ, USA: John Wiley & Sons.
Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.
If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.blog comments powered by Disqus