To assist users and potential users of STE, there are commercial companies or organizations that market software products that support STE. These efforts are greatly appreciated by ASD and the STEMG. However, neither ASD and the STEMG, nor any organization associated with the production of ASD-STE100 intend or imply any warranty or endorsement of any of the companies or organizations that provide supporting software products.
Software providers are not authorized nor certified by ASD and they cannot claim they have certification or ASD approval. It is very important that you are well informed on the fact that software providers are also not authorized to use in their material or documentation the ASD Logo, the Copyright and the European Union Trademark of ASD-STE100, even for publicity on web sites.
STE checkers available on the market today should only be seen as aids for those authors having a good knowledge of STE. None of these checkers will write STE text for you. Nor can they convert non-STE text to STE. Although STE checkers can be helpful with highlighting non-STE terms and incorrectly written STE text, they are not fool-proof.
STE CHECKERS CAN CORRECTLY PARSE STE TEXTS EVEN IF THESE TEXTS DO NOT OBEY THE STANDARD ENGLISH GRAMMAR!
The tools that exist will help you, but they will not tell you if what you have written means something or not.
In addition, there is a varying degree of accuracy in the error messages generated by word and rule checkers (this can be due to the checker, but it can also be due to other causes). Thus, they must be used with discernment. If you rely blindly on what they tell you, you are likely to write rubbish.
YOU, the author, are the one who knows, thinks and controls.
YOU are the one who must decide whether what a tool has told you is correct in your context.
Needs and constraints can be related to the potential users, and/or to the documentation production process.
To define your needs, it is useful to ask yourself some questions.
The previous section already contains some tips, but here are some more.
Do not rely completely on the error messages generated by a checker. Judgment is needed to interpret error messages correctly and to make amendments to the text that are not only correct as regards ASD-STE100, but that are also comprehensible. A checker will not tell the user if what is written actually means anything. And in the case of users whose mother tongue is not English, it will not guarantee that what they have written is correct English.
Make sure that the users of a checker have been trained not only in how to use the checker, but also, and more importantly, in how to write in ASD-STE100. If authors do not have a good knowledge of ASD-STE100 , it will be difficult for them to see when an error message is either incorrect, or not applicable.
Organize the collection of Technical Names for inclusion in the vocabulary database. Consider setting up a procedure for approving Technical Names before they are entered in the database, and having the entries made by a single person. If you do this, you will be able to control your terminology better.