Abstract
Engineers endow artifact with abilities to cope with expected anomalies. The ability may make the system robust. They are, however, a designed feature, which by definition cannot make the system “resilient.” Humans at the front end (e.g., operators, maintenance people) are inherently adaptive and productive that allows them to accomplish better performances and sometimes even allows them to exhibit astonishing abilities in unexpected anomalies. However, this admirable human characteristic is a double-edged sword. Normally it works well, but sometimes it may lead to a disastrous end. Hence, a system relying on such human characteristics in an uncontrolled manner should not be called “resilient.” A system should only be called “resilient” when it is tuned in such a way that it can utilize its potential abilities, whether engineered features or acquired adaptive abilities, to the utmost extent and in a controlled manner, both in expected and unexpected situations or circumstances.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Reference
Most content of this chapter is adopted from Microsoft MOSS web site.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2017 Springer International Publishing AG
About this chapter
Cite this chapter
Zohuri, B., Moghaddam, M. (2017). Business Resilience System Topology of Hardware and Software. In: Business Resilience System (BRS): Driven Through Boolean, Fuzzy Logics and Cloud Computation. Springer, Cham. https://doi.org/10.1007/978-3-319-53417-6_14
Download citation
DOI: https://doi.org/10.1007/978-3-319-53417-6_14
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-53416-9
Online ISBN: 978-3-319-53417-6
eBook Packages: EngineeringEngineering (R0)