Quality and certification

Proof that every screen was validated, organized for an audit

Custom system to record the validation trail of every feature, with the historical record rescued from spreadsheets and a report ready for ISO/IEC 17025 compliance.

Sitragol QA

An accredited laboratory does not just have to do things right: it has to be able to prove it did, with the evidence organized and dated. In software that means showing, for every screen, which test cases were run, who validated them and in which round.

All of that history lived in spreadsheets and in the suggestions module of the previous system. It worked as long as someone knew where to look, and it would not survive an audit.

Sitragol QA turns it into a five-level structure — system, screen, use case, test case and validation — with an audit trail on every change, and produces the status report the standard requires.

A five-level hierarchy: system, screen, use case, test case and validation

States with a transition machine, so a case cannot jump from proposed to validated

Validations by round, with verdict, remarks, validator and date

Import of the historical record from the validation spreadsheet and the previous system’s suggestions

Status report for ISO/IEC 17025 compliance and the internal procedure

Separate administrator, developer and validator roles, with an activity log

Evidence is not improvised on audit day.

It is built while the work happens, or it does not exist.

01

Reconstructed data is labelled as reconstructed. Imported history carries its source and is never presented as primary evidence: in an audit that is the difference between a data point and a problem.

02

The connection to the previous system is read-only and used solely by the import commands. There is no way for the QA system to modify the system it is validating.

If you can imagine it, we can build it.

Tell us what you need. We'll get back with a clear proposal, no jargon.