Software & Source Code | Knowledge

Knowledge topic

Software versions, repositories, source code, build states, requirements, testing and technical quality characteristics. This overview brings together the published technical articles and provides entry points into further technical questions.

Professional boundary: The articles address technical and methodological questions. Legal evaluation and legal advice remain separate.

Technical articles

6 published

Documents Needed in a Custom-Software Dispute

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.

Read article

Software Defects: Requirements-to-Actual-State Comparison

A technical defect examination compares a defined software state with a documented expected state under reproducible conditions, while keeping the technical deviation separate from its legal consequences.

Read article

Which Software Version Should Be Examined?

The relevant software version follows from the technical question and event date; commit, branch, tag, release label and build artefact are related identifiers but not interchangeable evidence of the same state.

Read article

Source Code: Repository, Commit, Branch and Build

A reproducible source-code examination identifies the repository and immutable revision, records working-tree and index state, includes submodules and dependencies where relevant, and connects source to the build artefact.

Read article

Git History and Software Provenance

Git history can support technical provenance by showing object relationships, references, metadata and reachable development history, but it does not by itself establish authorship, ownership or the completeness of all development activity.

Read article

Code Reuse and Software Similarity

Code similarity is evidence that requires context. Clone-detection results, manual review, repository history and third-party sources are combined to distinguish characteristic overlap from common libraries, generated code or independent implementation.

Read article

← Back to all knowledge topics

Author's technical literature and publications

The following works provide additional technical and methodological context. They do not replace required primary sources, standards, manufacturer documentation or other independent specialist sources. Unpublished manuscripts, drafts and teaching materials are deliberately not presented here as public sources.

Technical question in this topic?

For an initial professional review, the technical question, an overview of available documents and the desired timeframe can be provided.

Information for Courts & Law Firms