Plaintiffs Vie for a Look at Toyota's 'Crown Jewels'

, The National Law Journal

   |1 Comments

In the sudden acceleration cases against Toyota, there are confidential documents and highly confidential documents. And then there is what the judge overseeing most of the cases called the company's "crown jewels"—the source software code behind the electronics of its vehicles, which almost no one has seen.

This article has been archived, and is no longer available on this website.

View this content exclusively through LexisNexis® Here

Not a LexisNexis® Subscriber?

Subscribe Now

Why am I seeing this?

LexisNexis® is now the exclusive third party online distributor of the broad collection of current and archived versions of ALM's legal news publications. LexisNexis® customers will be able to access and use ALM's content by subscribing to the LexisNexis® services via lexis.com® and Nexis®. This includes content from The National Law Journal®, The American Lawyer®, Law Technology News®, The New York Law Journal® and Corporate Counsel®, as well as ALM's other newspapers, directories, legal treatises, published and unpublished court opinions, and other sources of legal information.

ALM's content plays a significant role in your work and research, and now through this alliance LexisNexis® will bring you access to an even more comprehensive collection of legal content.

For questions call 1-877-256-2472 or contact us at customercare@alm.com

What's being said

  • Thomas J. Kesolits PE

    From my experience in dealing with software for over 40 years, I don't believe access to the source code will show anything of value. In order to find a defect in the software, and most software has defects, the people evaluating it must have a detailed background in the programming language used and the requirments that drove the development of the software code. They will then have to analyze the, not the source code, but the application code. Subject matter experts will have to analyze the code line by line, instruction by instruction and I guarantee, they probably won't find anything. As an example, Microsoft releases operating systems and continually supplies patches to fix problems. They never find all of the problems no will people analyzing the source or application code. What must be done, is to look at how Toyota tested the fully delivered code, applied to the system, to see if any compromises occur. In the PC world, we know these as freezes, blue screens, or lock-ups. In applictions to control machinery, such as an automobile, these could manifest themselves as loss of control to an actuator, i.e. throttle, or over control to an actuator, appliction of power as a run-away. Even these kinds of tests don't show everything that can happen if a software instruction were to become corrupted by a high voltage pulse, RF radiation or something else.

    This commentary is written as stricty a netural postion. I do not own a Toyota product or stock in the company. I am looking for fairness and want to emphasize that in this world of cyber controls, unpredictable things can happen. The only thing to counter this is a full manual abort process initiated by a kill switch or something as mundane.



    Tom Kesolits

    732-245-5420

Comments are not moderated. To report offensive comments, click here.

Preparing comment abuse report for Article# 1202598940543

Thank you!

This article's comments will be reviewed.