There's never time to do it right, but there's always time to do it over. That said, there is a place for rapid prototyping, so long as you don't mistake prototype for enterprise level production.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of scott Ford [idfli...@gmail.com] Sent: Friday, February 28, 2020 10:23 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: OT Boeing flight software Mike, Reminds me of this whole Agile process that’s being used. Incomplete thinking, not like a lot of old timer Sysprogs, who had to think about , installation, testing, implementation in production, impact on users and backup. Boeing sounds piecemeal .. Scott On Fri, Feb 28, 2020 at 6:42 AM Ray Pearce <ray.pea...@macro4.com> wrote: > Orlando Sentinel says: > > Unfortunately, our website is currently unavailable in most European > countries. We are engaged on the issue and committed to looking at options > that support our full range of digital offerings to the EU market. We > continue to identify technical compliance solutions that will provide all > readers with our award-winning journalism. > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Mike Schwab > Sent: 28 February 2020 02:19 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: OT Boeing flight software > > > https://www.orlandosentinel.com/space/os-bz-boeing-safety-commercial-crew-20200226-bgvthodnjzgmlc36hsxcaopahu-story.html > > Boeing didn’t perform full end-to-end test of its astronaut capsule > before troubled mission, ‘surprising’ NASA safety panel. > > Critically, the panel learned early this month that Boeing did not > perform a full, end-to-end integrated test of Starliner in a Systems > Integration Lab with ULA’s Atlas V rocket. The test typically shows > how all the software systems during each component of the mission > would have responded with each other through every maneuver — and it > could potentially have caught the issues Boeing later experienced in > the mission. > > “It’s pretty exhaustive. You gotta do that,” said Christopher Saindon, > a former member who ended his tenure on the panel in mid-February. > “That was somewhat surprising to us on the panel. There were certainly > gaps in the test protocol.” > > > It was software that ultimately did fail Boeing when it flew Starliner > on a Dec. 20 mission intended to dock with the International Space > Station. The capsule’s internal clock was 11 hours ahead, causing it > to miss critical maneuvers and fly into the incorrect orbit. Then, > communication issues potentially caused by cell towers in the area > blocked Boeing from sending a command to rectify the orbit. Starliner, > the company determined, wasn’t going to be able to reach the space > station. > > But in the process of bringing it back down and re-checking its > software, the company caught yet another issue that could have caused > Starliner to collide with its service module when the two separated > prior to the capsule’s return to Earth. Teams were able to correct the > issue before to the capsule’s return on Dec. 22, but the multitude of > problems have led NASA to call for a full re-verification of Boeing’s > software — a process that will take analyzing about a million lines of > code. > > Software issues are also plaguing another arm of Boeing, which is > dealing with the fall out of problems with its 737 Max airplanes that > led to the deaths of 346 people and has grounded the planes. > > > -- > Mike A Schwab, Springfield IL USA > Where do Forest Rangers go to get away from it all? > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > This e-mail message has been scanned and cleared by Google Message > Security > and the UNICOM Global security systems. This message is for the named > person's use only. If you receive this message in error, please delete it > and notify the sender. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Scott Ford IDMWORKS z/OS Development ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
