Engineering & Technology · Engineering Economics, Projects & Professional Practice
Finding applicable standards, documenting decisions and evidence
A product is described as “tested to the standard,” yet the report omits the edition, tested configuration and clauses. The phrase sounds authoritative while leaving the actual claim unclear. Standards are useful when their scope and evidence can be traced.
Use design and measurement for comparisons and evidence; systems engineering develops configuration and interfaces. The supplied discount rates are arithmetic inputs, not current official rates or investment guidance. Professional codes and standards are identified by source and scope; actual legal and contractual duties require the applicable context.
Back to the chapterAfter reading, you can
Find a relevant technical reference and document its applicability, edition and supporting evidence without overstating conformity.
A familiar title is a starting point
Begin with the product or service, intended use, location, interfaces and relevant obligations. Search the responsible standards body and authoritative regulatory or contractual sources where applicable. Check the full title, identifier, edition, amendments, scope and status. A search summary or a vendor’s slogan does not provide the complete applicable text.
Standards can specify products, methods, terminology, management systems or guidance. ISO explains that its standards are voluntary documents that do not replace national law; authorities can refer to standards in regulations. A contract or project can also select technical obligations. Determine the actual basis for applicability rather than assuming every published standard is automatically mandatory or sufficient.
Keep the claim and evidence aligned
In ISO usage, “shall” expresses a requirement, “should” a recommendation, “may” permission and “can” possibility. Read these within the actual document and scope. Do not convert guidance into a universal obligation or describe a partial evaluation as conformity with every requirement. Access to a catalogue description does not mean the full standard was read.
Our fictional internal procedure P1 revision A has requirements R1, R2 and R3. The record links the first two to observations E1 and E2, while the third has missing evidence. A two-of-three link count measures record coverage only. It does not establish the observations are sufficient, that the third requirement is met or that complete conformity can be claimed.
Changes require applicability reasoning
Record the evaluated item and configuration, method, conditions, responsible review, result and unresolved deviations. Distinguish a supplier statement, purchaser evaluation and independent assessment. Each has a scope; an assessment label alone does not establish every desired product property.
When a referenced document changes, identify what was selected by the actual obligation and which technical changes affect the product or evidence. A newer edition does not automatically make every old result wrong, and an old result does not automatically satisfy changed criteria. Use the responsible applicability and change process, with competent interpretation where needed. This lesson provides a research method, not a ruling on any specific standard, contract or law.
Make one selected reference and three internal criteria concrete
Give the fictional P1 register a particular subject: an invented web booking form, page V1, software S1, browser configuration B1 and fixed light theme T1. The project team voluntarily selects the dated W3C Recommendation WCAG 2.2 of 5 October 2023 as a technical reference for web accessibility. Its web-content scope fits this subject; this does not establish a legal duty, the latest applicable edition or conformity. The inspected scope here is the document metadata, selected contrast and keyboard criteria, relevant definitions and conformance requirements, not every criterion or linked technique.
Selected criterion 1.4.3 uses a 4.5:1 minimum contrast for ordinary text, subject to its stated exceptions; criterion 2.1.1 addresses keyboard operation of functionality. P1 deliberately selects narrower internal checks, with a stricter 5.0:1 ratio for one active message in R1. That 5.0 threshold is a project choice, not a quotation from WCAG. The message is regular-weight 16 CSS px text, not a logo, inactive control or large-text example. R2 checks one normal booking path; it does not cover every function in the source criterion. R3 addresses a separate unavailable-service state.
Supply completed teaching records E1 and E2 in the table. E1 records opaque sRGB foreground #FFFFFF and background #666666, no image, gradient or transparency behind the active message, and the specified-color contrast calculation. E2 records the requested date, selected date, confirmation and keyboard actions for the normal path in the stated configuration. These are invented observations to reason about, not a test performed on an actual website. The evidence owner retains the configuration, criterion version, method, observed result and unresolved R3 path.
| Internal criterion | Method and supplied evidence | Bounded conclusion |
|---|---|---|
| R1: this message has specified-color contrast ≥5.0:1 in T1 | E1: V1/S1/B1/T1, white on #666666; WCAG sRGB calculation gives about 5.74:1 | Supports R1 for this message and color/state pair, not all page content or physical-screen legibility |
| R2: complete the stated normal connected booking path using the keyboard | E2: the defined date-selection and confirmation path completes without a pointer or special keystroke timing | Supports this path in the recorded configuration; other functions and failure states remain outside the record |
| R3: after service becomes unavailable, identify the status and reach retry using the keyboard | No E3 supplied | Unverified; two existing links do not fill this state-evidence gap |
Reject an unsupported conformity statement
The fictional P1 record has two evidence links out of three requirements. Before claiming complete conformity, the team must resolve the missing third path and evaluate whether each observation supports its actual requirement under the relevant conditions. Simply dividing 2 by 3 would quantify coverage, not compliance.
Suppose revision B changes the third test condition and leaves the first two unchanged. Investigate applicability and affected evidence rather than relabelling the old report as revision B. Retain both editions, the change decision and the precise scope of any reused result so another reviewer can reconstruct the conclusion.
For E1, the definition of relative luminance converts the encoded sRGB channels to linear values before taking their weighted sum. White gives luminance 1; #666666 gives about 0.132868. The contrast ratio is (1+0.05)/(0.132868+0.05)≈5.74. This exceeds P1’s 5.0 threshold. This is a calculation from specified colors, not a photometric measurement of a display or a reason to skip checking which colors actually appear in the selected state.
The defensible record says that R1 and the particular R2 path have the supplied supporting evidence, while R3 remains unverified. It cannot say “WCAG AA conformant”: that would need the relevant full-page, complete-process, level and accessibility-support requirements, including all applicable criteria. Even a valid narrow observation and a real standards citation do not enlarge one another’s scope.
Make the earlier revision-B change specific: only P1’s R3 condition changes from unavailable service during the session to unavailable service after restart. The item remains V1/S1/B1/T1 and R1/R2 conditions are unchanged. An applicability record may retain E1/E2 for their original claims, explaining why they are unaffected, but neither supports the new R3 state. If the item, styles or interaction changed as well, that separate impact must be assessed; changing the procedure label alone is not such evidence.
Try the reasoning
Does a catalogue page establish that the full standard was inspected?
Show the answer and reasoning
No. It can establish metadata or scope information, while the technical requirements may require access to the complete document.
Do two evidence links out of three establish partial conformity by percentage?
Show the answer and reasoning
No. Link coverage and justified conformity are different questions.
Why record the edition and configuration?
Show the answer and reasoning
They identify what criteria and product the result actually concerns and support later applicability checks.
The theme changes to white text on #777777 while R1 still requires 5.0:1. Can E1 be relabelled for this theme, and does rounding establish a pass?
Show the answer and reasoning
No. E1 concerns the #666666 background. Recalculating the changed specified-color pair gives about 4.478:1, below 5.0 and also below the selected ordinary-text minimum 4.5. Rounding it to 4.5 does not satisfy an unrounded threshold. Retain the original record, revise the design or resolve the requirement through its owner, and obtain evidence for the changed configuration. The earlier keyboard-path record also needs an impact review if visual feedback or interaction changed.
A supplier applies the same two colors to a printed poster and cites this web-form record as proof of poster conformity. What is the applicability error?
Show the answer and reasoning
The subject, method and use conditions changed. A specified sRGB web-text comparison does not establish printed contrast, viewing conditions, readable physical text or compliance with an applicable print requirement. Record the relevant print subject and authoritative reference/method before making that claim; a familiar document title and matching color names do not transfer E1 automatically.
What to carry forward
Trace authoritative references to their actual scope, selected edition and sufficient product evidence before making a conformity claim.
References
Teaching resources and research supporting this lesson’s explanations and examples.
- Systems Engineering Handbook §6.6: Technical Data ManagementNASAReference guide
- NSPE Code of Ethics for Engineers, Fundamental Canons and selected Rules/ObligationsNational Society of Professional EngineersReference guide
International Organization for Standardization2 sources
- Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation, 5 October 2023, selected criteria/definitions/conformance requirementsWorld Wide Web ConsortiumTechnical recommendation