Skip to main content
Unified search: articles, nationwide company names, and robot categories (separate module)
Section content

Writing a Specification That Can Be Verified

Published: Publisher: Zhilianhai Robotics News

How to write testable requirements

RequirementTestable form
Cycle timeMeasured over a stated run with stated parts
AccuracyMeasured with a named method and conditions
AvailabilityDefined as uptime over a stated period
ChangeoverMeasured by a named person within a stated time
VolumeStated units per shift with the shift pattern

Supporting practices

  • Number every requirement so responses can be itemised.
  • State who measures and with what instrument.
  • Keep the acceptance criteria in the contract, not only in the annex.

Specifications become contractual documents. Keep them consistent with the commercial terms.

This article is published by the Zhilianhai Robotics News site. Where policies, standards, prices, company capabilities or project status are involved, cross-check the original sources as well.

Back to section

Company information

Company information in this section comes from the Zhilianhai company database. To add or correct company data, go to Company Directory to look up the company, or submit a data verification request via Contact Us; once the company data upload channel opens, this module will handle it.

Latest materials in this section

Discussion and comments