Boeing's hardware is effectively finalized, but the control software is still undergoing testing with the finalized (i.e., "frozen") hardware specs.
Boeing's hardware is effectively finalized, but the control software is still undergoing testing with the finalized (i.e., "frozen") hardware specs.
Not only was Boeing software supposed to be effectively finalized, but Boeing hardware also appears to have failed on that test. The thrusters experienced issues, and the antenna that were contractually required to provide end to end connectivity failed to do so. Moreover on the second most recent demonstration (pad abort) Boeing suffered a parachute failure.
The software issues were the more serious issues that grabbed more headlines. The capsule incorrectly grabbing a time value from the rocket. The control logic for whatever reason didn't understand something was wrong, but instead "proceeded as normal" as if it was further ahead in the mission. Finally there was some other error that was caught before it happened but was something related to the thruster control logic and could have caused the loss of the capsule during re-entry.
I appreciate both the thanks, and that you identified the source of the confusion. I also appreciate that you made it clear that you know what you're talking about and that I didn't really need to write such a long answer for you.
There is a second investigation currently ongoing, an "organizational root cause assessment".
I think what you mean is the "organizational safety assessment" (OSA) which will occur later this year.[1] Germane to my previous comment, this will focus more on the organizational culture that may have contributed to the failure (e.g., decision making in the presence of heavy schedule pressure).