Reveal Hidden Obscurity in Requirements Language Now
- Many Defects are Attributed to Requirements Language
- Much vagueness and obscurity is inherently hidden from the writer
- Defects cost Time and Money
Are your requirements clear, concise, correct and coherent?
Our Requirements Analysis service provides guidance that improves the clarity of Requirements. We thoroughly assess and analyze your requirements word by word and sentence by sentence. We examine EVERY term and expression looking for unintended meanings and connections. Our service finds “human resistant” defects with sophisticated computational linguistic tools deployed in our (Patent Pending) Vital Text™ processing system.
Obscure Requirements Language
Find the issues that keep you from creating clear, concise, correct and coherent requirements documents.
Improve the chances that product is built right — and that the right product is built.
Reduce costs by reducing bugs, eliminating design errors, and speeding time-to-market.
Our free Vital Text™ introductory service will find up to ten language defects per submission (limit 3 submissions) and provide recommendations for clarifying the document. Our team of linguistics and computer science professionals is working to enhance the capabilities of the groundbreaking system. So, stay tuned, this tool is rapidly evolving!
What is the problem?
Language works best in live face to face situations where speaker and hearer know each other and each knows what the other knows — and does NOT know. But requirements engineers must write for several very different audiences that often have radically different backgrounds and experience. The same term may be perfect for one audience and gobbledygook for another. An obvious connection for one audience may sail right over the heads of another. To make matters worse, requirements are like recipes that tell the reader what the cake is supposed to look like and how sweet and moist it should be, but leave it to somebody else to figure out how all that can be achieved.
Even casual users of personal computing are aware that text editors can insert or replace characters, words or entire sentences and paragraphs. Consider what could happen with instructions that use “insert” to mean “append” initially, but at another point use it to mean “overwrite,” and elsewhere use it where it could mean either. Writers can easily overlook this sort of thing, and readers may not realize what’s happening until damage has been done. Readers (including the writer reviewing their own work) spontaneously “fix” ambiguities of this kind — meaning that they plug in the appropriate sense of the word and generally never even notice that they’ve done so. There is abundant evidence that most issues of this kind are never noticed by readers.
No kidding. The example above is based on a real issue found in a carefully constructed requirements document that seems to have been intended as a model of good practice.
C9 Processing Requirements
If you would like us to evaluate your requirements document here are some conditions we currently have to impose:
- We can process 15 pages of requirements per submission.
- We can accept documents in Word or PDF formats.
- We work diligently to process your document accurately and thoroughly. Our free Vital Text™ service typically provides feedback in 3 working days. We will keep you posted on the status of your document.
If your document is in Word or PDF format,
Select and upload up to 15 pages of your requirements document below to identify up to 10 defects in your requirements
Find up to 10 Language Weaknesses Now