June 2010
Intermediate to advanced
392 pages
8h 31m
English
Chapter 2
In Chapter 1 we defined software resilience as the ability to reduce the magnitude and/or duration of disruptive events. The effectiveness of a resilient application or infrastructure software depends on its ability to anticipate, absorb, adapt to, and/or recover rapidly from a potentially disruptive event.
We also surveyed the landscape of effects from insecure and poorly designed or developed software and the wake of damaged and defunct organizations that a tsunami of bad code leaves behind.
Chapter 2 focuses on the beginning steps that will leave the present state on the heap of history. We’ll compare and contrast functional and nonfunctional requirements and we’ll ...