Certification is an independent party confirming that a product, process or person meets a defined standard. In engineering it is how regulators and customers gain trust in safety, security or quality they cannot inspect themselves. It rewards traceable evidence: what you said you would do, what you did, and proof of both. Requirements differ by country and sector.
Key concepts
- Standards and scope: the document that defines the requirements, and what exactly is being certified.
- Evidence and traceability: requirements linked to design, code, tests and results, each reviewable.
- Independent assessment: an accredited body or auditor reviews the evidence and may test the product.
- Process and product: some schemes certify how you work, others the product itself.
- Maintenance: changes can require re-assessment, so change control matters.
Vocabulary
- Conformity assessment: checking that requirements are met.
- Audit: a systematic, documented examination against criteria.
- Traceability matrix: a table linking each requirement to the items that implement and verify it.
- Accreditation: formal recognition that a body is competent to certify.
What to study, in order
- Read the introduction and structure of one standard in your area, and list what it requires.
- Take a small project and write its requirements with unique identifiers.
- Build a traceability matrix from requirements to tests, and find the gaps.
- Practise change control: when a requirement changes, work out what must be redone.
- Prepare for a mock audit, with a colleague asking for evidence of each claim.
Related tags
#functional-safety #standards #requirements #hardware-security