Skip to main content

Engineering and validation integrations

Connect requirements, revisions and test results from Jama Connect, Polarion and TestRail to change impact and missing verification evidence.

Illustration of a seal beside a laptop showing a data table and an evidence binder linked by a red thread.

What these systems hold.

Requirements and test management tools hold requirements and their revisions, the links between them, and test cases, runs and results: the traceability that shows a system was verified against what it was meant to do.

EU GMP Annex 11 asks that user requirements describe the functions a computerised system needs and stay traceable throughout its life cycle (Annex 11, 4.4). When a requirement changes, the organisation needs to find the tests it affects and the verification evidence still missing.

What Seal reads and writes back.

Jama Connect, Polarion and TestRail are each scoped against the provider’s REST API. Seal reads the requirements, work items and test results the API exposes to the connected account, and Jama’s API needs a Named Creator licence. Nothing is written back unless that is separately approved, and which system holds each record is agreed when the connection is scoped.

Seal
  1. Jama Connect, Siemens Polarion, TestRailSource of truth agreed when scoped

    Reads Selected records your edition exposes

    Writes back If separately approved

3 connections

Blueprints that use these records.

Start with one source.

Tell us what Neil needs to do and where the records live. We’ll scope the connection with your team.

Book a demo