Source Code Review
Software patent cases are the fastest-growing type of litigation for sustaining industries in a competitive environment. Source Code Review is the most potent tool in software patent litigation and trade secrets cases. Evidence from the source code review can uncover powerful arguments for infringement case toward a product. Since the software products are increasing day by day, the complexity for evaluating infringement litigation proof is also growing.
MentesoIP utilizes state of the art methods to perform source code review.
MentesoIP uses code analysis tools present in IDEs like Eclipse, Visual Studio, and SlickEdit and stand-alone products like Beyond Compare, PowerGREP, code2flow, Android Studio, etc. Source code review experts at MentesoIP are comfortable in various programming languages including C, C++, Java, C#, ROR, Python, PHP, Perl, Objective C, etc. Our source code review experts have worked on different platforms including Android, Windows, Linux, iOS, and MacOS.
The experience of our team at Source Code Review plays a vital role in generating the high-quality Evidence. Below are few of our best practices that enable us to deliver the results with flying colors:
- Organize it right - Review all other technical literature before analyzing the source code. It helps you get a good grasp of the architecture, design, functional specs, use cases and put things in perspective.
- Review the similar codes: Review technical literature of similar products available in the "Open Source" ecosystem.
- Think beyond the source code: Analyze all related creation including various libraries, API (application programming interface), installers, user interface, etc.
- The keyword is Key: Make use of targeted keywords to recognize associated functional modules - mapped to the infringement theory. Further, meticulously analyze the subset for evidence.
- The Comment on Comment: Source code comments are a gold mine for evidence. Consider using 'Comment extraction' utilities.
- Go Extra Mile - Identify what is missing, explore alternate theories, and search for additional evidence in source code based on deposition testimonies, response to interrogatories, etc.