Consistency is a software quality characteristic: equivalent inputs, operations, and uses should produce uniform behavior. It helps turn vague requirements into questions about validation, data handling, and repeatable outcomes. section 4.4.1
Use consistency to examine:
- Whether equivalent project names are treated uniformly, including differences in capitalization. section 4.4.5
- Whether data structures permit values that later operations cannot handle reliably, such as null keys. section 4.4.5
- Whether requirements clarify how time entries are validated and interpreted. section 4.4.1
Timesheet manager
A timesheet accepts a project name and duration. The implementation rejects null project names and nonpositive durations, but a consistency review also considers capitalization and the treatment of existing entries. Normalizing names to lowercase and using a map operation that supplies a default value illustrate possible responses to inconsistent project lookup and storage.
