04.04 Project Validation, Delivery, and Version Management

  1. Business Customer / Developer Integration Manual
  2. 4.4 Project Validation, Delivery, and Version Management

4.4 Project Validation, Delivery, and Version Management

Project delivery must be reproducible. The hardware, receiver, SDK, customer application, and test results must use the same version baseline.

Minimum Record Requirements

  • SKU, device ID, receiver, and channel group.
  • SDK or delivery package name, version, acquisition date, and applicable environment.
  • Customer application, engine, operating system, architecture, and dependency versions.
  • Minimum validation steps, expected result, actual result, and evidence ID.
  • Known limitations, upgrade conditions, rollback files, and responsible person.

Delivery Sequence

  1. Run the minimum example or minimum data path in the agreed environment.
  2. Validate the actions and optional capabilities for the current SKU.
  3. When using multiple pairs of gloves, validate asset mapping and cross-interference.
  4. Archive installation packages, the SDK, configurations, records, and redacted evidence.
  5. Both parties confirm passed items, blocking items, and the person responsible for each next action.

Version Baseline

HardwareSKU and device ID
CommunicationReceiver and channel group
SDKName and version
Runtime EnvironmentSystem, architecture, engine
Customer ApplicationBuild version
ResultPass / Blocked / Not Applicable

Next Step

If an issue occurs, continue to 5.1 Troubleshooting Commercial Deployments.