Learn what the score means, how it's calculated, and how to use it to improve your requirements.
What is the Quality Analysis Score?
Quality Analysis gives each requirement a numeric score based on how well it aligns with your selected rule set. It’s a quick way to assess clarity, consistency, and compliance — so you can focus your review where it matters most.
QVscribe scores each requirement from 1-5 and provides guidance on remediating the detected problems.
🦖 Did you know?
The Average Score is a good indicator of the overall health of your requirements document.
How is the individual score calculated?
The score is based on the following Quality Score Indicators, which can be adjusted in the Configuration settings:- One and only one Imperative
- No Negative Imperatives
- No Vagueness
- No Optional Escape Clauses
- No Optional Open-Ended Clauses
- No Superfluous Infinitives
- No Cross-Referencing Pronouns
- No Immeasurable Quantification
- No Non-specific Temporal Words
- Few Continuances (no more than 2)
- Proper use of Directives (off by default)
Want more details on the Configurations? Here's more information on the Starting Configurations and How to Further Customize Configurations.
Quality Warnings may also be present in the analysis results, but these do not impact the Quality Analysis Score. Think of these as more of an FYI, as they depend heavily on the context of the requirement:
- Proper Use of Universal Quantifiers
- No Justification Information
- No Incomplete Sentences
- No improper use of Passive Voice
Understanding the Potential for Risk
The Quality Analysis Score is also colour-coded to reflect the level of risk associated with the problems found.
Think of QVscribe’s Quality Analysis Score like a traffic light for your requirements:
🔴 Red (1): Stop and revise. There may be significant clarity issues, vague terms, or formatting concerns to address.
🟡 Yellow (2-4): Be careful, this may read as perfectly clear to you, but some of the word choices may leave more room for (mis)interpretation than you think.
🟢 Green (5): Clear to go! Your requirement is well-structured, unambiguous, and aligns with your standards.
This doesn’t mean “bad” or “wrong” — red just means there’s room for improvement, and QVscribe is here to help guide that process.
Seeing lots of low scores? Here’s why that’s okay — and what to do next.
Quality Analysis Score vs. Requirement Quality
A low score helps identify improvement areas, but it doesn’t always mean the requirement is incorrect. Likewise, a high score doesn’t guarantee technical completeness.
QVscribe checks how requirements are written, not what they mean in context. That's where you, the professional, come into the equation!
Think of it as a powerful partnership — combining human judgment with the speed and precision of technology. 🤝
QVscribe helps apply the principles, clarify the content, and identify the potential problems. You understand the project and scope, are the framework's author, and can work with QVscribe to help solve the problems.
Problem Type Deep Dive
In the webinar below, Morgan takes a closer look at several key QVscribe Problem Types — what they mean, the issues they can cause in your requirements, and how to effectively resolve them.