Expert Strategies for Winning Software IP Litigation with Gary Stringham
Discover Gary Stringham's top 10 strategies for software IP litigation, leveraging his 30 years of engineering experience and expertise in embedded systems.
File
Ten Strategies for Software IP Litigation
Added on 09/27/2024
Speakers
add Add new speaker

Speaker 1: If you're involved in software IP litigation, there's one thing that's for sure. You need every strategy possible to win your case. With over 30 total years of professional engineering experience, Gary Stringham is a published author on embedded systems. He's been awarded 12 US patents for his innovative embedded systems designs and has authored 15 defensive publications. And his solutions have helped companies save millions of dollars in prototype costs, development time, and warranty costs. All of these accomplishments have made Gary Stringham a highly respected expert witness in cases concerning embedded systems. He's served as an expert witness in cases involving infringement and violations of patents, copyrights, trade secrets, and other intellectual property, and cases regarding defective products. This experience has given Gary unique, pragmatic insights, which can help you in your software IP litigation cases. That's why he's composed 10 strategies for 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, or an expert in technology across many products, may be preferable to a vertical expert, or an expert in a product using many technologies. Today, businesses across the country are turning to Gary for his expertise in embedded systems development, firmware development, source code comparisons, patent claim analysis, and intellectual property litigation. If you need an expert to consult in software source code and hardware designs, and reverse engineering the designs of others, the search is over. And let's talk.

ai AI Insights
Summary

Generate a brief summary highlighting the main points of the transcript.

Generate
Title

Generate a concise and relevant title for the transcript based on the main themes and content discussed.

Generate
Keywords

Identify and highlight the key words or phrases most relevant to the content of the transcript.

Generate
Enter your query
Sentiments

Analyze the emotional tone of the transcript to determine whether the sentiment is positive, negative, or neutral.

Generate
Quizzes

Create interactive quizzes based on the content of the transcript to test comprehension or engage users.

Generate
{{ secondsToHumanTime(time) }}
Back
Forward
{{ Math.round(speed * 100) / 100 }}x
{{ secondsToHumanTime(duration) }}
close
New speaker
Add speaker
close
Edit speaker
Save changes
close
Share Transcript