FYI, if a potential employer asks a question such as, “What are the characteristics of good user requirements?”, the following would be a good list to memorize:
The requirement addresses one and only one thing.
The requirement is fully stated in one place with no missing information.
The requirement does not contradict any other requirement and is fully consistent with all authoritative external documentation.
The requirement is atomic, i.e., it does not contain conjunctions. E.g., “The postal code field must validate American and Canadian postal codes” should be written as two separate requirements: (1) “The postal code field must validate American postal codes” and (2) “The postal code field must validate Canadian postal codes”.
The requirement meets all or part of a business need as stated by stakeholders and authoritatively documented.
The requirement has not been made obsolete by the passage of time.
The requirement is concisely stated without recourse to technical jargon, acronyms (unless defined elsewhere in the Requirements document), or other esoteric verbiage. It expresses objective facts, not subjective opinions. It is subject to one and only one interpretation. Vague subjects, adjectives, prepositions, verbs and subjective phrases are avoided. Negative statements and compound statements are avoided.
Many requirements represent a stakeholder-defined characteristic the absence of which will result in a major or even fatal deficiency. Others represent features that may be implemented if time and budget permits. The requirement must specify a level of importance.
The implementation of the requirement can be determined through basic possible methods: inspection, demonstration, test (instrumented) or analysis (to include validated modeling & simulation).