It has been decided by management to ask an external consultant to perform a reliability assessment. The external consultant will use a checklist to support the assessment. Select TWO checklist…

Question

Options

• AAre traceability matrices provided to the requirements?
• BIs all code supported by a reviewed design document?
• CIs the comment frequency at the correct level?
• DIs a dual set of hardware available?
• EAre features available for a periodic check of the database consistency?

• A
  3% (1)
• B
  6% (2)
• C
  13% (4)
• D
  77% (24)

Explanation

D and E are correct because they directly address system reliability - the ability of a system to keep functioning correctly over time. Dual hardware (D) provides redundancy so that a hardware failure doesn't bring the system down (eliminating single points of failure is a cornerstone of reliability engineering). Periodic database consistency checks (E) detect and prevent data corruption, ensuring the system continues to produce correct results over time.

A (traceability matrices) belongs on a requirements coverage or test completeness checklist, not a reliability one - it verifies linkage between requirements and tests, not system uptime. B (design documents backing code) is a code quality or maintainability concern. C (comment frequency) is a code readability/maintainability metric - neither B nor C has any bearing on whether a system will continue to operate correctly under load or after failures.

Memory tip: Ask yourself "does this item help the system stay up and stay correct?" Redundant hardware = stay up; consistency checks = stay correct. If the item is about documentation, traceability, or code comments, it's a quality/maintainability concern, not reliability.

No community discussion yet for this question.