Description

Introduction

Arguably the most important software development problem is building software to
meet customer demands that it be more reliable, built faster, and built cheaper (in
general order of importance). Your success in meeting these demands affects the
market share and profitability of a product for your company, and hence your
career. These are conflicting demands, causing risk and overwhelming pressure, and
hence, they call for a practice that can help you with them.
Software reliability engineering (SRE) is such a practice, one that is a standard,
proven, widespread best practice that is widely applicable. It is low in cost, and its
implementation has virtually no schedule impact. We will show what it is, and how
it works.
We will then outline the SRE process to give you a feel for the practice, using a
single consistent example throughout. Finally, we will list some resources that will
help you learn more about it.