One of the most important things you will do as a business analyst is document requirements. If those requirements are ambiguous, you’re going to have trouble later in the project.
Ambiguous terms leave room for interpretation by the development team and can also create requirements that are not testable.
Karl Wiegers, a well-respected requirements management consultant, in his book Software Requirements, provides this list of words to avoid and ways to improve them. You may want to print this list and post it in your office as a visual reminder.
Click this link to download and save the list of terms (this file is in PowerPoint format).