At the very beginning a project team deals with customer’s requirements and expectations expressed in natural language.
The highest usage scenarios of Reverse Semantic Traceability method can be: Main roles involved in RST session are:
However, it is obvious that performing RST for all artifacts can create overhead and should be well justified (for example, for medical software where possible information loss is very critical).
Importance of document is the degree of artifact impact to project success and quality of final product.
Experts should be aware of project domain and be an experienced enough to assess quality level of compared artifacts.
Depending on this value Project Manager makes a decision should both artifacts be corrected or one of them or rework is not required.
If the average mark is more than 3 but less than 4 then corrections of validated artifact to remove defects and insignificant information loss is supposed.
If the mark is greater than 4 it means that artifact is of good quality and no special corrections or rework is required.
Obviously the final decision about rework of artifacts is made by project manager and should be based on analysis of reasons of differences in texts.