Detect errors in your requirements
Semios for Requirements is a simple tool that will automatically analyze the requirements of your technical documents. Semios for Requirements interfaces with your everyday tools. You will avoid multiples rewriting and focus on the core as you will proofread your documents; Semios for Requirements will take care of the rest.
Something wrong happened. Please try again.
Semios for Requirements
Semios for Requirements automatically analyzes your technical documents. Semios for Requirements goes further than a simple keywords analysis, by offering a contextual and semantic analysis.
Integrated into your tools
You do not have to download yet another tool for your proofreadings. We develop add-ons for every tool you may use.
Easy to use
Semios is as easy to use as your spellchecker. The add-on is integrated into your tools and customized by our team. You only need a click to use it.
Customized to your needs
From a generic basis, we customize Semios to fit your professional context and ensure the consistency of the analysis.
By using Semios for Requirements day after day, your teams will learn what makes a good requirement. The more they will use it, the more they will improve their skills at writing useful and precise requirements.
Try Semios for free
Send us one of your technical documents, we will send you back the document annoted by Semios
Allowed file extensions: .dma (DOORS), .docx, .doc (Word)
We guarantee the strict confidentiality of your documents will be preserved, and that we will not retain them
Our technology: the semantic analysis
Semios for Requirements reports both warnings and advice.
Fuzzy terms
Semios reports fuzzy terms that make requirements uncheckable.« as soon as possible », « if needs be », « properly » and so on.
Too many coordinating conjunctions
The use of coordinating conjunctions makes the structure of the requirements complex. Semios reports such complex structures.« But », « or », « and », « therefore », « however », « neither », « for »
Too many negatives
Using many negatives can make requirements very difficult to understand. Semios will report such problems.« ... it is not enough not to set priorities ... »
Passive voice
Semios reports passive voice in your requirements. Passive voice makes it difficult to know who or what the requirements may concern.« Importing the file shall be done so ... » By whom ?
Expressions to avoid
Semios reports the expressions which shall be avoided for a better understanding of the requirements.« Etc .» « ACU », « ... », « ACD », « TBC », « TBD » ...
Requirements without shall
Semios reports requirements that do not use the "shall" modal.
Multiple requirements
Semios reports 2 requirements found in a single statement, as it makes testing less obvious.« The tool shall ask the user to confirm (...) and, as the case may be, make ... »
Control of the rationale
Best practices recommend writing the rationale of the requirement out of the requirement body. Semios reports if the Rational is included within the requirement.« The tool shall make a cache (...) in order to reduce the search time... » In this case, the rationale is included within the requirement
Conformity of the structure of sentences
Semios can control the conformity of the structure of the sentences, based on your set of rules, which will be built according to the specificities of your field and your company.For example, Semios reports the presence of a requirement that does not follow this structure: < Subject > < Action > < Object > < Condition >
Too long requirements
Semios reports if the requirement is composed of too many sentences or words.
Use of underspecified terms
Semios reports the use of underspecified terms that make the requirements unverifiable.« Any system... of any other equipment... »
And yours...
Meet us
Semios for Requirements provides both warnings and advice.
Register to our next Webinar
October 4, 2016
From 1:00pm to 2:00pm
Something wrong happened. Please try again.
October 13, 2016 : Meet us at the Emenda Event in Paris La Défense
October 11, 2016 : Meet us at the Emenda Event in Toulouse
October 4, 2016 : Webinar Semios for Requirements
Our offer
A pricing system adapted to your needs.
Licence per user
  • Semantic engine
  • Plug-in for IBM Rational DOORS or for Microsoft Word
Please contact us for further information
Licence per user
  • Semantic engine
  • Plug-in for IBM Rational DOORS
  • Plug-in for Microsoft Word
Please contact us for further information
Licence per user
  • Semantic engine
  • Access to all our plug-ins
Please contact us for further information
Our early adopters
  • Field : Aeronautics in a ARP4754A and DO 178B context

    Patrick Janjaud
    (Development Quality – Airworthiness – Qualification – Processus Manager)


  • Field : Low-power gas turbine in a ARP4754A and DO 178B context

    Nicolas Piro
    (Technical audit)


  • Field : Naval defence

    Jean-Bernard Lavaury
    (Head of department)