IEEE-compliant documentation of SpiraTeam data for software test specifications and software test reports

Documentation of software test specifications and software test reports is often subject to formal requirements. Examples: It must be possible to display the documentation at all times without special tools (requirement for long-term archiving). In order to compare acceptance tests for the results of the test executions with the underlying test specification, for example, the structure and the order must be identical in the documentation for the test specification and the test report. If test specifications and test reports are generated from a test tool, it must be possible to add free-form information to the generated content, e.g. to include graphical evaluation of test results. Formal requirements apply, in particular, in regulated markets (e.g. railway industry, pharmaceutical industry, healthcare) and these are supported by various standards (e.g. IEC 61508, IEEE 1558, EN 50128).