Seal's Guarantee of Quality

This page is a summary of the Quality processes in Seal. It briefly describes how Seal is developed and delivered to customers in line with software development best practices, especially those of GxP-regulated industries.

Seal, designed for GxP-regulated industries, facilitates the creation, review, and maintenance of critical records and databases, as well as the capacity to process information rapidly. Seal upholds quality, reliability, and integrity across its systems, processes, and product that aligns with regulatory frameworks and international standards.

Seal follows an iterative and incremental approach based on GAMP 5 guidelines for its Computerised System Life Cycle to ensure efficient risk management, flexibility, early issue detection, and continuous improvement. The product development and support phases are guided by the following requirements from GAMP Supplier Good Practices but are not limited to:

• Documented set of procedures and standards

• Well-defined requirements from regulated companies before onboarding

• Quality planning

• Design review process

• Defined standards for software production

• Clear user documentation and training

Alongside the above, Seal enforces the following sets of requirements on the product:

Product Development and Support

Seal is required to development, installation, intensive testing, maintenance, and operation in adherence to industry good practice and to enable customers to be compliant with applicable regulations.

The following addresses some of the measures taken:

• Addressing any concerns from the customers

• Allowing the customer to raise any bugs they may have come across

• Allowing the customer to raise any problems with the functionality of the platform, and discuss new feature requests

• Helping set up the platform for the customer

• Helping the customer get to know some of the more advanced features on the platform

Operational Phase

Seal must satisfy regulatory requisites, focusing on live usage aspects such as ongoing maintenance, modifications, data handling, access controls, etc.

Production changes undergo the following stringent approach:

1. Module testing (unit and database testing)

2. Acceptance testing (utilising playwright tests)

3. Regression testing

4. Peer reviews

We employ two testing methodologies — automated (comprising database and end-to-end tests) and manual. The standards are:

1. All pull requests must pass automated tests.

2. All pull requests require the completion of a peer review and approval.

A crucial aspect is the integration of Continuous Integration, where automated checks are performed with each commit. This ensures immediate notification to the developer in case of errors, maintaining a proactive approach to identifying and addressing issues during the development lifecycle.

Regular reviews and internal audits are conducted to uphold the quality of systems and work in individual teams and across systems.