When it is needed
If the origin of similarities between programs, the contents of transferred source code or changes to particular modules need to be examined.
What we examine
- Source code and project versions
- Database structure and exports
- Documentation and change history
Materials to prepare
- Source materials to be compared
- Description of the file contents and how they were obtained
- Documentation and available version history
- List of modules and circumstances to be checked
Sample questions
- Which modules and fragments are available in the submitted sets?
- Which similarities and differences were identified in the source code?
- What role do libraries, templates and automatically generated elements play?
- Do the materials contain data relating to the specified development version?
- Which circumstances of creation and transfer cannot be established by technical comparison?
How the work is carried out
- We record the contents and verification characteristics of the sets
- We compare selected modules with regard to shared dependencies
- We describe the findings and limitations on establishing origin
Result
A technical report with a reproducible comparison description and a list of files examined.
What affects the conclusions
The same function does not mean the same source code. The report does not establish the rights holder without analysis of the relevant legal grounds.
Frequently asked questions
Can compiled builds alone be examined?
The possibilities depend on the format and brief. Without source code, some questions about structure and origin will remain subject to limitations.
Should I provide access to a production server?
We first agree a safe copy and the minimum necessary scope. Passwords and production secrets should not be sent through a standard form.