IT Architect Series: Designing Risk in IT Infrastructure

IT Architect Series: Designing Risk in IT InfrastructureWhat do we mean when we say designing risk? Every event that occurs does not happen in isolation. An event is a combination of people, places, and things, and is associated with a time period. Each event affects other events, like a ripple in a pond. They are all interrelated and woven into an invisible fabric that is the current state of being. One cannot ignore this fact when designing an IT infrastructure or planning a long term technological

What do we mean when we say designing risk? Every event that occurs does not happen in isolation. An event is a combination of people, places, and things, and is associated with a time period. Each event affects other events, like a ripple in a pond. They are all interrelated and woven into an invisible fabric that is the current state of being. One cannot ignore this fact when designing an IT infrastructure or planning a long-term technological strategy, because infrastructures are not comprised of detached components operating in isolation.

Risk is defined by a probability and an impact, which can be represented qualitatively or quantitatively. Or in simple terms: something may happen and it might hurt a lot or a little. You can guess and gamble your way through it, or you can truly understand what your options are and start planning.

This book will give you the ability to see beyond a fault or failure, and start understanding the relationships between risk response, resources, cost and acceptance.