C'mon - Klunk is the inventor, Dick Dastardly is the middle manager who messes it up!
... I'll get my coat^H^H^H^Hflying jacket!
26 posts • joined 7 Nov 2013
I agree entirely. Personally, I think the MCAS was classed as a DAL-D device (Device failing is minor inconvenience), so safety critical requirements were not needed.
Now, FAA have, I think, upgraded the DAL to DAL-A/B (Device failing is hazardous or catastrophic), causing to add many checks to the process. One of those checks is to simulate bit-flips/stuck-at faults etc. (That's why I reckon the MCAS is a SRAM FPGA because the most common bit-flip failures is in the State-Machines).
(Have done > 7 years doing DO-254, going up to DAL-B in severity)
Microsoft have a choice to make, as many commenters above have written. Whether to down the route of subscription (as Adobe, Amazon, et al. have done), or down the route of added value (Red Hat). I fear though Microsoft will go down the familiar path of Embrace, Extend, Extinguish.
We've seen in the press about MS embracing some of the components in a Linux environment. Soon, they will introduce Outlook & Office in a closed source binary with a Windows like GUI on Linux (Windows style on Linux), to get the flock back to using they products . Slowly they will tinker with the Linux kernel (extend), before forking it. Microsoft will then force the flock to use that fork because Outlook & Office (et al.) will only run on that fork. After that, Microsoft's Linux and Windows 13.11 will be merged.
(Microsoft's play book is Animal Farm...)
Biting the hand that feeds IT © 1998–2020