Assurance issue policy

This page describes the policy for analysis, resolution and notification of assurance issues within Rapita Systems' RVS software.

Analysis of assurance issues

Potential assurance issues may be identified during the use of RVS by Rapita staff or by our customers. When we become aware of a potential assurance issue in RVS by any means, we analyze it to identify whether it is an issue (whether it can cause a functional change in the software or lead to a false positive result). While analyzing an issue, we analyze its scope, identifying the version(s) of RVS that it affects. We analyze all Current, Superseded and Deprecated versions of RVS, but do not analyze versions that have reached their End of Life unless Frozen Version Support has been arranged for those versions. For more information on our Product life cycle policy, see our Product life cycle policy webpage.

After our analysis is complete, we publish a bulletin for the issue and send a notification about it to assurance issue contacts (see Notification of assurance issues).

Resolution of assurance issues

We aim to provide workarounds or fixes for assurance issues as soon as possible. When we schedule resolutions for assurance issues, we schedule them for a specific major, minor or incremental RVS version. Fixes can include a range of updates including, but not limited to, clarifications in documentation, fixes to the off-the-shelf tools, or fixes to the generic integration support libraries that we provide. When we notify users of new assurance issues, we identify if we have already scheduled a resolution for the issue. After an assurance issue has been resolved, we update the status of that issue and send a notification about the change of status.

Notification of assurance issues

For each assurance issue, we publish a bulletin, which you can view at any time from our Customer portal as a registered RVS user, and which we send my email to assurance issue contacts (see below). Bulletins identify the RVS version(s) the issue affects, describe the issue and the situations in which it can be encountered, and describe workarounds and strategies to mitigate against the issue. We also identify the status of the issue, which can be one of:

• Open – The issue is still active and its resolution has not yet been scheduled.
• Planned – The issue is active but its resolution has been planned for a specific RVS version.
• Resolved – The issue has been resolved in a version of RVS.

By default, we add all registered RVS users to our assurance issue email notification list. We regularly keep users on this list updated by email with updates to assurance issues, including:

• New issues that have been identified
• Changes in assurance issue status at each RVS release

If you have questions about our notification process or would like us to add or update assurance issue contacts, please contact us at support@rapitasystems.com.