Formal requirements differ from natural language requirements in that they use a predefined language to convey the same meaning.
The advantage of this type of notation is that they are understood identically by all readers with knowledge of the same vocabulary. Thus, the formal requirements are free of interpretation. Additional work due to misinterpretation can thus be avoided and this saves money in the development. Due to their very high level of detail, they require hardly any domain-specific knowledge and are therefore very well understood even by departments not involved in development.
The derivation of formal requirements from natural language requirements can largely be understood as a consistent reformulation and refinement of existing requirements.
#TPT18 provides a set of functions to handle formal requirements in addition to natural requirements. In tandem to the feature of importing and exporting requirements, which has been available for some time, you can now natively create natural language requirements, as well as formal requirements in TPT. We have designed the UI in such a way that a requirement can always be supplemented and refined by a formal requirement at any time.
The great thing is, every requirement formally described in TPT18 is automatically evaluated and reported. We estimate that with this new feature you can reduce the cost of maintenance and maintainability of your test implementations and the overall test effort by 10-20%.