General > General Technical Chat
Boeing Starliner: 2 SW bugs found, patched, uploaded in-flight to avoid disaster
<< < (4/6) > >>
SiliconWizard:
This one is cute too: https://www.theregister.co.uk/2020/01/08/boeing_737_ng_cockpit_screen_blank_bug/

coppice:

--- Quote from: edy on February 11, 2020, 07:24:28 pm ---I would have expected there to be extensive simulator and systems testing, and not just on one but several different independently made simultation/testing platforms, just to hammer out every possible issue there could ever be.

--- End quote ---
The key problem with most of this kind of work is it takes a very specific kind of character to do it well. A character that largely ignores most of the obvious stuff that almost any simplistic testing will find, and seeks out the funky corner cases where most of the serious issues tend to be found too late, and often disasterously. These people need to be a part of every simulation team, and need to be the most highly regarded and rewarded. Instead they are too often suppressed, because they increase the test complexity to the point where its effective, while management just wants to ship stuff. People love talking about flushing out corner case issues, but it has a nasty tendency to go little further than talk.
splin:
Boeing have finally fessed up to their failure to properly test the software:

https://www.theregister.co.uk/2020/03/03/space_roundup/


--- Quote ---Boeing vice president and program manager John Mulholland put on a brave face
....
The latter was caused by spacecraft's propulsion controller not being available for testing (it was being used in a hot fire test of the service module). The gang made do instead with what Boeing described as an "incorrect emulator" which didn't have the correct jet mapping. It was only once the mission was under way and the hardware returned to the lab that the team could re-run the test and discover the issue. A hurried patch was uploaded.
--- End quote ---

 :palm:


--- Quote ---The approach to testing was eye-opening. It transpired that Boeing had not run an end-to-end test of the entire mission, opting to segment things instead. As far as the timer issue was concerned, where the Starliner's clock was set incorrectly and the ISS docking cancelled, the company had elected to end the test segment concerning launch at the point of spacecraft separation. A few more minutes of testing would have shown the problem.
--- End quote ---

 :palm:

Remind me again how much Boeing were billing for this?
tom66:
Boeing has some serious core engineering problems that need to be addressed.

If this was truly a free market, rather than Boeing being in the pocket of the US Military and Gov't, then the 737MAX8 disasters would have been enough to take the company down.  Think how it only took one accident to put people off the de Havilland Comet,  or the accidents that brought down McDonnell Douglas (perhaps some of the engineering transplants from MD are responsible for the fuckups at Boeing?)
wraper:

--- Quote from: tom66 on March 04, 2020, 07:56:17 am ---Boeing has some serious core engineering problems that need to be addressed.

--- End quote ---
More like management problems.

--- Quote ---(perhaps some of the engineering transplants from MD are responsible for the fuckups at Boeing?)
--- End quote ---
Management transplants. There was internal joke that McDonnell bought Boeing with Boeing's money.
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod