Defining Reference Standards and Technical Assessment Criteria

Expert Reports & Methodology

A technical assessment becomes reviewable only when the relevant property, applicable reference, version, operational criteria and tolerances are established before the observed result is classified. The English version preserves the technical distinctions and limitations of the reviewed German V1 source.

1. Derive the reference from the examination question

Scope and technical proposition

The examination begins by fixing the proposition and the concrete state to which it applies. In this article the central task is selecting the technical reference before assessment and translating abstract quality concepts into observable or measurable criteria. The system boundary, relevant date and version identifiers are recorded before individual findings are interpreted, because a technically correct result about the wrong state cannot answer the intended question.

The scope also records explicit exclusions and dependencies. This prevents later expansion from a narrow reproduced observation to an entire product, project or historical period. The working question is written so that a knowledgeable reviewer can understand what evidence could support it and what evidence could weaken it.

2. Document scope, version and hierarchy of sources

Evidence and provenance

The examination basis is built from versioned specifications, project requirements, acceptance criteria, standards, measurements and documented tolerances. Each item is identified with the strongest practical version, provenance and time information available. Originals, exports and working copies remain distinguishable, and transformations or filters are recorded where they can influence the conclusion.

Evidence quality is assessed separately from evidence existence. A file can be intact yet incomplete, a repository can be authentic yet shallow, and a log can be correctly exported yet unsuitable for a proposition outside its retention period. Missing expected evidence is recorded as a limitation rather than silently treated as confirmation.

3. Operationalise abstract quality concepts

Reproducible examination

The technical method is to derive the reference from the examination question, document source hierarchy and operationalise each criterion before classifying the observed state. Commands, tools, parameters, thresholds and environment conditions are documented where they materially affect reproducibility. The objective is not merely to obtain a result but to preserve the reasoning path from identified input to technical finding.

Where the procedure contains judgement, the report states which parts are mechanical and which require professional interpretation. A repeated test or independent check is used where it can reveal sensitivity to configuration, tool choice, sample selection or an alternative technical mechanism.

4. Include tolerances, uncertainty and counter-checks

Counter-checking and uncertainty

Counter-checking asks what else could produce the same observation and what result would contradict the preferred explanation. This is especially important because measurement uncertainty, alternative plausible references and the difference between a technical quality model and contractual or legal binding effect. Negative evidence is only given weight when the search space and detection capability are understood.

If several explanations remain compatible with the available material, the conclusion is not forced into a single cause. Instead, the report ranks or describes the support for each explanation and records which additional evidence would be needed to distinguish them.

5. Keep finding, interpretation and assessment separate

Reference and interpretation

Interpretation connects the finding to its technical significance, while assessment uses project-specific requirements where applicable, complemented by standards such as ISO/IEC 25010 or ISO/IEC/IEEE 29148 within their stated scope. The reference, its version and its applicability are disclosed before the observed state is classified. This allows a reviewer to see whether disagreement concerns the measurement, the interpretation or the chosen criterion.

The assessment remains limited to the technical reference. A standard, specification, project requirement or repository convention may structure the technical comparison without automatically establishing contractual effect, legal responsibility, ownership or regulatory compliance.

6. Document revision triggers when the reference changes

Synthesis and statement boundary

The final synthesis returns to the original question and states which parts are directly supported by evidence, which depend on interpretation and which remain uncertain because of measurement uncertainty, alternative plausible references and the difference between a technical quality model and contractual or legal binding effect. The wording is calibrated to the evidence rather than to the desired certainty of the dispute.

The statement boundary is therefore an affirmative part of the result. It identifies unexamined states, missing records, unresolved counter-hypotheses and legal or normative questions that require a different assessment. This makes the technical conclusion reviewable and reduces the risk of overclaim.

Further reading

• Sources & Methodology
• Findings, Interpretation and Assessment
• Defining a Technical Question and Scope of Examination

Expert Report Documentation & Traceability

Structured, reviewable documentation of technical examination steps, evidence, criteria, findings and limitations.

Explore this assessment service