The code was copied which was used in previous missions. The faulty code was not carefully code-reviewed. NASA declared the mission a loss the next day and launched an investigation. The contact with the Orbiter was never established. The Orbiter did not exit the Martian shadow as expected at 09:27 UTC. ![]() It passed behind the planet as it was firing its rockets… and was never heard again. The mission control at the ground was expected to lose contact at 09:06 UTC as the spacecraft passed behind Mars. On September 23, 1999, the spacecraft fired its rockets to alter its path so that it would enter orbit around Mars. The Orbiter was planned to fire its main engine and then skim through Mars’ upper atmosphere for several weeks to reduce its velocity and move into a circular orbit. The spacecraft traveled through space for almost nine and a half months towards Mars and reached on September 1999. In addition to collecting data, to study the atmosphere and clouds of Mars, the Orbiter was to act as a relay station for five years assisting data transmission to and from its partner Mars Polar Lander. The mission was of one Martian year or approximately two Earth years. One such mission was Mars Climate Orbiter (MCO) launched on December 11, 1998, from NASA’s Cape Canaveral Air Force Station. There are 70 odd missions to Mars few succeeded and few failed. There has been a number of explorations done on Mars and as all of us know NASA is leading the race. Let me take you through the case of Software Failure…. There is also technical debt that adds to the cost of poor software quality. The total cost of poor software quality in the US is estimated at $2.08 trillion 5. The top three contributors to the cost of poor software quality are 1) Software Failures 2) Legacy System Problems 3) Unsuccessful development projects. ![]() The poor software quality costs money and agony to the organizations as well as end-users.
0 Comments
Leave a Reply. |