Ten Strategies for Software IP Litigation

Описание: Based on his litigation experience with software patents, copyrights, and trade secrets, and his 30+ years in the software engineering industry, Gary composed ten strategies to aid in software IP litigation.

1. When requesting software during discovery, request commented source code, executable files, build files, data files, design documents, manuals, etc., in their original electronic formats.

2. Even if the source code from opposing parties is written in different languages, infringement could still have occurred.

3. If security is a concern, it might be possible to examine software source code on a computer with no internet connection and with USB ports disabled.

4. Signs of potential source code copying include similar variable and function names, author names, comments, lines of code, and program flow.

5. To examine code for content that might have previously existed, request all past revisions of source code files between a specific start and end date.

6. Comprehending what the software is doing by reading source code could be a time-consuming effort. Extra time may be needed for that effort.

7. Extracting executable code from a device, and performing a “reverse assembly” to make it human-readable, may be possible and could require significant effort to understand.

8. Use of open source and third-party source code is common. It must first be identified and removed from the file set before examining the rest for IP content.

9. CodeSuite® is a tool specifically designed to detect possible copying and plagiarism of source code and executable code.

10. In looking for an expert, a horizontal expert (expert in a technology across many products) may be preferable to a vertical expert (expert in a product using many technologies).