Spartan Daily, March 7, 2001

Volume 116, Issue 29https://scholarworks.sjsu.edu/spartandaily/9665/thumbnail.jp

Spartan Daily, March 7, 2001

Volume 116, Issue 29https://scholarworks.sjsu.edu/spartandaily/9665/thumbnail.jp

SciTech News Volume 71, No. 3 (2017)

Columns and Reports From the Editor.........................3 Division News Science-Technology Division....5 Chemistry Division....................8 Conference Report, Marion E, Sparks Professional Development Award Recipient..9 Engineering Division................10 Engineering Division Award, Winners Reflect on their Conference Experience..15 Aerospace Section of the Engineering Division .....18 Architecture, Building Engineering, Construction, and Design Section of the Engineering Division................20 Reviews Sci-Tech Book News Reviews...22 Advertisements IEEE..........................................

Spartan Daily, March 9, 1993

Volume 100, Issue 27https://scholarworks.sjsu.edu/spartandaily/8385/thumbnail.jp

The natural history of bugs: using formal methods to analyse software related failures in space missions

Space missions force engineers to make complex trade-offs between many different constraints including cost, mass, power, functionality and reliability. These constraints create a continual need to innovate. Many advances rely upon software, for instance to control and monitor the next generation ‘electron cyclotron resonance’ ion-drives for deep space missions.Programmers face numerous challenges. It is extremely difficult to conduct valid ground-based tests for the code used in space missions. Abstract models and simulations of satellites can be misleading. These issues are compounded by the use of ‘band-aid’ software to fix design mistakes and compromises in other aspects of space systems engineering. Programmers must often re-code missions in flight. This introduces considerable risks. It should, therefore, not be a surprise that so many space missions fail to achieve their objectives. The costs of failure are considerable. Small launch vehicles, such as the U.S. Pegasus system, cost around $18 million. Payloads range from$4 million up to $1 billion for security related satellites. These costs do not include consequent business losses. In 2005, Intelsat wrote off$73 million from the failure of a single uninsured satellite. It is clearly important that we learn as much as possible from those failures that do occur. The following pages examine the roles that formal methods might play in the analysis of software failures in space missions

Spartan Daily, September 17, 1981

Volume 77, Issue 12https://scholarworks.sjsu.edu/spartandaily/6787/thumbnail.jp

Spartan Daily January 28, 2010

Volume 134, Issue 2https://scholarworks.sjsu.edu/spartandaily/1218/thumbnail.jp

Digital Dissemination Platform of Transportation Engineering Education Materials Founded in Adoption Research

INE/AUTC 14.0

Spartan Daily, February 7, 1996

Volume 106, Issue 9https://scholarworks.sjsu.edu/spartandaily/8794/thumbnail.jp

Spartan Daily, December 1, 1992

Volume 99, Issue 64https://scholarworks.sjsu.edu/spartandaily/8348/thumbnail.jp