Reliability describes the ability of a system to perform its required functions under defined conditions for a specified period.
Teams measure it through values such as availability, failure rate, recovery time, and mean time between failures. Therefore, they should define clear targets and operating conditions.
A reliability requirement must state the relevant function, environment, workload, and measurement period. Moreover, it should include objective acceptance criteria and verification methods.
For example, a system may need to achieve 99.95% availability during defined business hours. Monitoring data, simulations, and operational tests can then provide evidence.
Teams should also analyse risks, dependencies, maintenance periods, and recovery strategies. In addition, traceability should connect each requirement with its source, design elements, and test cases.
Field data may reveal new failure patterns after deployment. Consequently, teams should review targets and tests throughout the system lifecycle.
Clear dependability targets support objective testing, effective risk management, and consistent system operation.
« Back to Glossary Index