The Language of Requirements
Using a single language as your client is the basic rule in the use of language. That’s just simple. If we use a consistent language, it contributes to a better understanding ofthe requirements. Let’s put it this way, a recent project has product catalogue for seeds. In the initial draft, we categorized the seeds inyo “types”, “categories” and “sub-categories”.
While this made sense for us, the client and others involve in the project use the terms “crop”, “type” and “variety”. This might mean confusion if we don’t use the same terms as the client. So therefore, a useful technique to avoid this problem is to include a glossary of terms and definitions in the requirements document.