AHI QA Process Steps

When a client has completed the technical integration, the QA process should be initiated as follows:

1. Client requests for QA booking
2. AHI to hand QA checklist to client and simultaneously arrange an upcoming timeslot with internal QA
3. Client to do QA of the integration against the checklist to ensure all items pass
4. Client to handover app access to AHI for us to conduct second round QA
5. AHI to perform QA of the integration based on the same checklist items
   1. We commit to completing the QA process within 10 working days (excludes time taken for additional fixes)
   2. The goal is to ensure that SDK is integrated well with no errors through the initiation, scanning, and results output processes.
   3. This is not a QA of the clients' application. However, we can provide feedback for any notable flaws we encounter outside of the SDK.
6. Sign-off on QA, share Prod tokens and prepare for launch

AHI QA Checklist

General Checklist

• If user input data is taken from elsewhere (e.g. profile section), they should be mapped correctly to the SDK input schema
• Subscription packages or one-off scan purchases are linked to the correct ScanControl Product ID

BodyScan Checklist

• Remote assets for BodyScan download as expected
• Weight bounds checking has been verified - within 16-300kg or 36-660lb or equivalent.
• Height bounds checking has been verified - within 50-255cm or 1'8"-8'4" or equivalent
• BMI bounds checking has been verified - BMI between 10-60
• Age bounds checking has been verified - at least 15 years old
• SDK output data are mapped correctly to the metrics displayed
• Results that require calculations are calculated correctly
• 3D Model displaying correctly (optional feature)
• Can complete BodyScan capture

FaceScan Checklist

• Weight bounds checking has been verified - 30-300kg or 67-660lb or equivalent
• Height bounds checking has been verified - within 120-220cm or 4'0"-7'2" or equivalent
• BMI bounds checking has been verified - BMI between 10-65
• Age bounds checking has been verified - 13-120 years old
• SDK output data are mapped correctly to the metrics displayed
• Results that require calculations are calculated correctly
• Can complete FaceScan capture

Note: if the client is using both BodyScan and FaceScan and pulls height/weight info from user profile, the bounds should be validated so that it falls WITHIN the upper and lower bounds of both scans (using the smaller upper and lower numbers)

‍