What Documents Are Needed to Examine a Custom-Software Dispute?

Software & Source Code

The required material depends on the technical question, but a reliable first examination usually needs the requirement baseline, identifiable software state, defect and test evidence, project history and the relevant runtime environment. The English version preserves the technical distinctions and limitations of the reviewed German V1 source.

1. Let the technical question drive the document request

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 requesting evidence that is proportionate to the concrete software question rather than collecting an undifferentiated project archive. 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. Secure requirements and the documented expected state

Evidence and provenance

The examination basis is built from requirements, source repository, commit and release identifiers, build artefacts, defect reports, tests, tickets, logs, project history and runtime environment. 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. Identify the software and source-code state

Reproducible examination

The technical method is to map each evidence class to the question, identify version and time context, preserve contradictions and document the received evidence 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. Classify defect, test and reproduction evidence

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 missing historical artefacts, unversioned exports, incomplete project records and legal questions about authenticity or contractual 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. Capture project, change history and system environment

Reference and interpretation

Interpretation connects the finding to its technical significance, while assessment uses the requirement, event or technical property that the requested material is meant to establish. 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 transfer and reliability of the material

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 missing historical artefacts, unversioned exports, incomplete project records and legal questions about authenticity or contractual 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
• Source Code: Repository, Commit, Branch and Build
• Git History and Software Provenance

Software & Source Code Assessments

Technical assessment of software architecture, source-code quality, maintainability, development evidence and technical risks.

Explore this assessment service