When I was young, my literature teacher told me: "please, avoid repeating the same noun over and over on your texts, use synonyms, pronouns...". Maybe your teachers told you the same, and they were right, but for sure they were not thinking about requirements, rather they were talking about poetry.
Another important metric that RQS takes into account is the number of verbs used in a requirement. Where most of the companies, in their guidelines and checklists are expecting for, at least, one main verb (i.e. one action); others are also prohibiting including several main verbs into the same requirement. It’s a common mistake to involve multiple needs in the same requirement.
One important aspect that must be fully clear in every requirement is the fact of “who” or “which subsystem” is the responsible for the action described in the requirement.
According to many sources, including INCOSE in its Systems Engineering Handbook, the cost of fixing a defect introduced during the early stages of a project grows exponentially as time goes by along the different phases of the project. In other words, if the cost of fixing a defect that was introduced in the requirements engineering phase were US$1, fixing the same defect during the development could be up to 100 times more expensive and fixing it in production could be up to 1,000 times more expensive.
A requirements management tool helps you to store the different requirements, prioritize them and manage different versions of them. Using a requirements tool you can also trace relationships between different requirements.
Did you know? Coupled and inconsistent requirements are two big issues when writing your requirements specifications.
Thanks to the semantic analysis of RQS, based on Natural Language Processing, a semantic graph can be generated out of every single requirement. This is the process we call formalization. Requirements with similar formalization can be considered as coupled requirements, while further analysis can be done to detect inconsistent content.
Did you know? The correct structure (grammar) of your requirements boosts the quality of your specifications. Try Requirements Authoring Tool, based on patterns, boilerplates and ontologies, while authoring your requirements.