Mastering the Requirements Process

Some, though not all, of the non-functional requirements should be the earliest to be gathered and understood. They should never be assumed, as frequently happens, even when the customers and the developers believe they are obvious.