Also ensure that they are (spell grammar) error free and written per the IEEE standard.
Triggering events: Document all triggering events with its Outcomes and ensure that nothing is left out.
Terminology: There is a common understand of it and documented.
Clarity: All requirements have unique identifiers and examples are given to make it as simple as possible.
The development of software begins once the requirements document is 'ready'.
One of the objectives of this document is to check whether the delivered software system is acceptable.
I would agree with the first three; inspection, demonstration and test.
However, I am sure it could be argued that demonstration and test could be combined as well.Having an idea of the type of questions you might be asked during a business analyst interview will not only give you confidence but it will also help you to formulate your thoughts and to be better prepared to answer the interview questions you might get during the interview for a business analyst position.Of course, just memorizing a list of business analyst interview questions will not make you a great business analyst but it might just help you get that next job.The requirements document should be formulated and organized according to the standards of the organization.The organizational knowledge is used to estimate the realism of the requirements of the system.Hence, it is desirable to detect errors in the requirements before the design and development of the software begins.