Higher order software techniques applied to a space shuttle prototype program
HOS concepts are now being applied to a prototype Shuttle flight software system. By providing software with its own meta-software and its own universal system, not only can we produce reliable systems, but we can also communicate these systems to others. Development and real-time flexibility are not sacrificed. The only limitations applied are those which prevent a potential error from occuring, i. e., the only flexibility missing is that which allows for flexibility of errors.
KeywordsOutput Space Priority Relationship Wait State Mission Phase Dynamic Scheduler
Unable to display preview. Download preview PDF.
- 1.Hamilton, M., "Management of Apollo Programming and its Application to the Shuttle," CSDL Software Shuttle Memo No. 29, May 27, 1971.Google Scholar
- 2.Dahl, O. J., Dijkstra, E. W., and Hoare, C. A. R., Structured Programming, Academic Press, London and New York, 1972.Google Scholar
- 3.Mills, Harlen, "Top-down Programming in Large Systems," Courant Computer Science Symposium, June 29 — July 1, 1970.Google Scholar
- 4.Hamilton, M., "Computer Got Loaded," Datamation, March, 1971.Google Scholar
- 5.Hamilton, M., "First Draft of a Report on the Analysis of Apollo System Problems During Flight," CSDL Shuttle Management Note No. 14, October 23, 1972.Google Scholar
- 6.Wulf, W. A., and Shaw, M., "Global Variable Considered Harmful," Sigplan notices, February, 1973.Google Scholar
- 7.Knuth, D. E., "The Remaining Trouble Spots in Algol 60," CACM 10, October 10, 1967.Google Scholar
- 8.Hamilton, M., Zeldin, S., "Higher Order Software Requirements," CSDL E-2793, August, 1973.Google Scholar
- 9.Intermetrics, Inc., "HAL/S Language Specification," January, 1974.Google Scholar
- 10.Hamilton, M., Zeldin, S., "Top-down, Bottom-up, Structured Programming and Program Structuring," Rev. 1, CSDL E-2728, December, 1972.Google Scholar