The goal of requirements documentation is to state each need of the proposed system or process (who, what, where, when and why) precisely and thoroughly. Requirements must also eliminate ambiguity. For example, "The software system will time out when the customer leaves their computer for a while," is a poor requirement. "The system will time out after 60 minutes of inactivity," is better.