Student or educator? Sign up with your school email and get 6 months of Pro free.
CoChat

The DOI matches its Crossref record; 33 of the 35 references it cites were found in a registry or an index.

Towards a Conceptual Framework for Resilience Engineering

Madni, A.M., Jackson, S. · 2009 · IEEE Systems Journal

Abstract

As systems continue to grow in size and complexity, they pose increasingly greater safety and risk management challenges. Today when complex systems fail and mishaps occur, there is an initial tendency to attribute the failure to human error. Yet research has repeatedly shown that more often than not it is not human error but organizational factors that set up adverse conditions that increase the likelihood of system failure. Resilience engineering is concerned with building systems that are able to circumvent accidents through anticipation, survive disruptions through recovery, and grow through adaptation. This paper defines resilience from different perspectives, provides a conceptual framework for understanding and analyzing disruptions, and presents principles and heuristics based on lessons learned that can be employed to build resilient systems.

Overview

Integrity signals

Registry

Crossref · 10.1109/jsyst.2009.2017397

Cites

33 of 33 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

Citations

Cites

Show all 35 references

Research works printed but not linked: 31

  1. rechtin, 2000, Systems Architecting of Organizations
  2. woods, 2006, Resilience Engineering Concepts and Precepts
  3. 1993, Standard Practice for System Safety
  4. rechtin, 1990, Systems Architecting
  5. neumann, 2000, Practical Architectures for Survivable Systems
  6. ketchum, 2008, Mark Ketchum's Bridge Collapse Page
  7. 0, NASA Mars Climate Orbiter
  8. madni, 2007, Designing for Resilience ISTI Lecture Notes on Advanced Topics in Systems Engineering
  9. 2006, Resilience Engineering Concepts and Precepts
  10. 2000, Patte d'Oie in Gonesse (95) to the Concorde registered at F-BTSC operated by Air Force Bureau Enqu�tes Accidents (BEA)
  11. eyles, 2004, Tales from the Lunar Module Guidance Computer
  12. zarboutis, 2006, Using complexity theories to reveal emerged patterns that erode the resilience of complex systems, Proc 2nd Symp Resilience Eng
  13. madni, 2008, Agile systems architecting: Placing agility where it counts, Conf Systems Engineering Research (CSER)
  14. 2004, CAPER? Computer-Based Action Prediction Elaboration and Reasoning with Intelligent Adversaries
  15. madni, 1985, Option generation: Problems, principles, and computer-based aiding, Proc 1985 IEEE Int Conf Systems Man and Cybernetics, 757
  16. dekker, 2005, Ten Questions Bbout Human Error A New View of Human Factors and System Safety
  17. woods, 2006, Resilience Engineering Concepts and Precepts
  18. westrum, 2006, Resilience Engineering Concepts and Precepts
  19. chiles, 2002, Harper Business
  20. 1996, Aircraft Accident Report
  21. mendo�a, 2006, Adaptive capacity: Electric power restoration in New York City following the 11 September 2007 attacks, Proc 2nd Symp Resilience Eng
  22. westrum, 2006, All coherence gone: New orleans as a resilience failure, Proc 2nd Symp Resilience Eng
  23. madni, 1987, Knowledge-based simulation: An approach to intelligent opponent modeling for training tactical decision making, Proc 9th Interservice/Industry Training Systems Conf
  24. larson, 2000, Isaac's Storm The Time and the Deadliest Hurricane in History
  25. jackson, 2009, Architecting a Resilient System from Architecting Resilient Systems Accident Avoidance and Survival and Recovery from Disruptions
  26. woods, 2003, Creating foresight: How resilience engineering can transform NASA's approach to risk decision making, Testimony on the Future of NASA for Committee on Commerce Science and Transportation
  27. senge, 1999, The Dance of Change
  28. leveson, 2006, Resilience Engineering Concepts and Precepts
  29. neumann, 2007, Best Power in Ensuring Business Resilience, Newsletter, 6
  30. holling, 1996, Engineering Resilience Versus Ecological Resilience Engineering Within Ecological Constraints
  31. goble, 2002, Resilient Infrastructure Improving Your Business Resilience

Cited by

See all 649

Metadata

Authors
Madni, A. M., & Jackson, S.
Affiliations
  • Intelligent Systems Technology (United States) (US)
  • University of Southern California (US)
Venue
IEEE Systems Journal
Published
2009-06
Volume
3
Issue
2
Pages
181-191
ISSN
  • 1932-8184 (ISSN-L)
  • 1937-9234
OpenAlex
W2136897491
Cited by
649
References
35
Citations by year
2026: 31 · 2025: 41 · 2024: 64 · 2023: 55 · 2022: 59 · 2021: 55 · 2020: 36 · 2019: 61 · 2018: 51 · 2017: 42 · 2016: 42 · 2015: 37 · 2014: 28 · 2013: 17 · 2012: 14
FWCI
16.71
Type
journal article
Language
en
Open access
closed
Locations
IEEE Systems Journal (publishedVersion)
Topics
  • Physical Sciences › Engineering › Control and Systems Engineering › Systems Engineering Methodologies and Applications
  • Physical Sciences › Engineering › Civil and Structural Engineering › Infrastructure Resilience and Vulnerability Analysis
  • Social Sciences › Safety Research › Occupational Health and Safety Research
Keywords
resilience engineering, conceptual framework, complex systems, system failure, recovery, adaptation, safety management, risk management, heuristics, lessons learned

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: Towards a Conceptual Framework for Resilience Engineering. https://app.cochat.ai/papers/10.1109/jsyst.2009.2017397
The paper
Madni, A. M., & Jackson, S. (2009). Towards a Conceptual Framework for Resilience Engineering. IEEE Systems Journal. https://doi.org/10.1109/jsyst.2009.2017397

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.