Search This Blog

Translate

Blog Archive

Middleboro Review 2

NEW CONTENT MOVED TO MIDDLEBORO REVIEW 2

Toyota

Since the Dilly, Dally, Delay & Stall Law Firms are adding their billable hours, the Toyota U.S.A. and Route 44 Toyota posts have been separated here:

Route 44 Toyota Sold Me A Lemon



Showing posts with label Embedded System Software Quality. Show all posts
Showing posts with label Embedded System Software Quality. Show all posts

Sunday, December 10, 2017

Betsy Bejaminson: THANKS!





Betsy Benjaminson:  thoughts concerning ...
 
1.  Betsy is, and was, little known (sadly) outside of a small circle of individuals on this planet;
only publically identified as “The Toyota Whistleblower” for approximately the final 4.5 years
of her life.
 
2.  She has now (tragically) become an “historical figure.”
 
3.  While she became “a public figure,” following the Corporate Counsel Magazine article in
March 2013, with limited mention in the four Japan Times articles in June 2013, and received some
coverage in the Israeli media in early 2014, she was never “featured,” in a large mainstream
worldwide media article, or major American TV show segment, such as 20-20, 60 Minutes, etc.
 
4.  She was let-down, and failed, by many; not the least of which was NHTSA (who after all, had
initiated 3-4 (at least initial) “investigations” into reports of Toyota SUA events earlier on their
own – which subsequently went nowhere.  (With NHTSA potentially having been effectively
infiltrated by Toyota – there’s potentially an additional story there as well?)
 
5.  Beyond that, Congress, the media, insurance companies, police, IEEE (who have “never taken a
public position” concerning SUA – even as a number of their members are involved), and I’m sure
possibly others -- along the way, also let her down. 
 
Sadly, the Car Wash Association has never published, “or leaked,” their internal guidance memo
concerning vehicles noted prone to SUA -- meant as safety guidance for their members.
 
6.  “Everybody is in on the (SUA) act,” but no one wants “to publically admit” the obvious, and continuing,
ongoing truth concerning the issue.  (Still have no idea “why” Honda did (in a limited way) concerning several
of their hybrid vehicles in Japan?)
 
7.  Have no idea “what plans” Betsy had made for the potential release of any book she had (hopefully largely)
completed prior to her passing.  Same for all her original, and translated, documents.  Reportedly, approximately
one-percent of them “tell the story,” but unfortunately -- did not include -- a “smoking-gun” memo.  (In real-life,
there are rarely “Perry Mason moments,” where the guilty party dramatically “publically confesses” to the crime.)
 
8.  Even – IF --  solid plans had been completed and implemented, “how much” -- “legal wrangling” – will there be
concerning them (legal -- or otherwise -- control and ownership, their release, and financial-related issues)?  And
could Toyota (who “will spend” ANY amount of time, money, and legal fees to suppress), tie-up their release for years,
if not decades?  And finally potentially place Betsy’s family members in some form of never-ending legal and financial
jeopardy and hell?
 
9.  If NOTHING HAPPENS over the next 6- 24 months, it’s likely “her efforts” will essentially disappear, and “fade
promptly” into history.  Certainly the ability to provide “any legal consequences and/or public grief” to Toyota
will sadly, and likely, be lost
 
10.  Beyond that, 20- 30++ years from now, a researcher, etc., may “come across” her life and story – and write about it.
If it proves to be “an initial public hit,” it could then be made into a TV, or Hollywood movie.  But by that time, the SUA
issue will (hopefully) have been  largely taken care of.  (Speaking for myself, I will not be here to see this, not to mention
prove to be heartbreaking, as she becomes more famous in death, than in life, given the important nature of her efforts
and story.)
 
(Toyota has been hiring embedded software professionals in Thailand for some year now.  While “the simple answer”
is: it’s probably less expensive, a possible more complex answer is: whether additionally, these folks are “outside the
reach” of the U.S. legal system – and could never be “legally requested” to “tell what they know” about Toyota’s ETCS-i? 
(Wish I knew, the answer to this, one way or the other.)
 
11. Beyond the initial 20 - 30++ year mark, “Betsy’s story” is “discovered” 75 - 200+ years from now.  A “true” “historical
figure,” with an interesting story, from “the bad old days” in the political and corporate history of the U.S. and planet --assuming
both survive.
 
 
 
 
 




Tuesday, November 22, 2016

Embedded Software Security, Safety & Quality Preview



The vehicle you drive is filled with SOFTWARE! 

Prof. Philip Koopman offers great information to understand the surrounding issues and complexities. 






Embedded Software Security, Safety & Quality Preview
Monday, November 21, 2016
Here's a summary video on Embedded Software Security,
Safety & Quality.
https://betterembsw.blogspot.com/2016/11/embedded-software-security-safety.html
(with 3:20 min preview video)  (There are seconds of blank screen within it)
--------------------------------------------------------------------------
EDGE CASE
RESEARCH
MAKE ROBUST SOFTWARE
TRAINING SERVICES
https://www.edge-case-research.com/training
--------------------------------------------------------------------------
EDGE CASE
RESEARCH
MAKE ROBUST SOFTWARE
SOFTWARE QUALITY LIBRARY
FULL TUTORIALS
info@edge-case-research.com
https://www.edge-case-research.com/full-tutorial-videos
------------------------
Currently posted:
Tutorial:
Peer Reviews
(19:50 min video)
------------------------
Tutorial:
Security Plans
(30:33 min video)
------------------------
Tutorial:
Avoiding
Spaghetti Code
(14:42 min video)
--------------------------------------------------------------------------

Saturday, November 12, 2016

Embedded System Software Quality: Why is it so often terrible? What can we do about it?



Companion blog to the book Better Embedded System Software by Phil Koopman at Carnegie Mellon University

Monday, November 7, 2016


Embedded System Software Quality: Why is it so often terrible? What can we do about it?

I had a great time meeting old friends and new folks at ISSRE 2016.

Here are slides from my keynote address:

Embedded System Software Quality:
Why is it so often terrible? What can we do about it?

Failures of embedded system software increasingly make the news. Everyday products we rely upon are suffering from safety issues, security issues, and just plain bugs. While perfection is unrealistic, surely we can improve this situation.  Two key ideas apply: (1) embedded products often aren’t created by computer specialists, and (2) teaching application domain specialists just how to code is more of a problem than a solution.


https://betterembsw.blogspot.com/2016/11/embedded-system-software-quality-why-is.html


Top 5 Embedded Software Problem Areas

The biggest problems I see in industry code reviews are code complexity, real time performance, code quality, weak development process, and dependability gaps. Here's an index into blog postings and other sources that explains the problems and how to deal with them.

https://betterembsw.blogspot.com/2016/05/top-5-embedded-software-problem-areas.html



Embedded System Software Quality
Why is it so often terrible? What can we do about it? (Keynote Talk)
Philip Koopman
ECE, ISR, RI Depts., Carnegie Mellon University & Edge Case Research LLC
Pittsburgh, PA USA
Koopman@cmu.edu




Embedded System
Software Quality
Why is it so often terrible?
What can we do about it?
ISSRE 2016 Keynote
Prof. Philip Koopman
https://users.ece.cmu.edu/~koopman/pubs/issre2016_keynote_slides.pdf
(32 slides)

---------------------------------------------------------------------------------------
27th International Symposium on Software
Reliability Engineering, Ottawa, Canada
Submitted by webmaster on
Mon, 01/11/2016 - 22:02
http://issre.net/
--------------------------------------------------------------------------------------