Universal Systems Language: Lessons Learned from Apollo

Margaret H. Hamilton; William R. Hackler

doi:10.1109/MC.2008.541

Computer
2008
Issue No. 12 - December
Abstract - Universal Systems Language: Lessons Learned from Apollo

	This Article
	Subscribers, please Login Purchase article: $19 PDF HTML IEEE Xplore Subscribers RSS feed
	Share
	Email this Article to a friend
	Bibliographic References
	ASCII Text BibTex RefWorks Procite/RefMan/EndNote
	Add to:
	Digg Furl Spurl Blink Simpy Google Del.icio.us Y!MyWeb
	Search
	Similar Articles Articles by Margaret H. Hamilton Articles by William R. Hackler

Universal Systems Language: Lessons Learned from Apollo

December 2008 (vol. 41 no. 12)

pp. 34-43

	ASCII Text	x
	Margaret H. Hamilton, William R. Hackler, "Universal Systems Language: Lessons Learned from Apollo," Computer, vol. 41, no. 12, pp. 34-43, December, 2008.

	BibTex	x
	@article{ 10.1109/MC.2008.541, author = {Margaret H. Hamilton and William R. Hackler}, title = {Universal Systems Language: Lessons Learned from Apollo}, journal ={Computer}, volume = {41}, number = {12}, issn = {0018-9162}, year = {2008}, pages = {34-43}, doi = {http://doi.ieeecomputersociety.org/10.1109/MC.2008.541}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, }

	RefWorks Procite/RefMan/Endnote	x
	TY - MGZN JO - Computer TI - Universal Systems Language: Lessons Learned from Apollo IS - 12 SN - 0018-9162 SP34 EP43 EPD - 34-43 A1 - Margaret H. Hamilton, A1 - William R. Hackler, PY - 2008 KW - NASA KW - Universal Systems Language VL - 41 JA - Computer ER -

Margaret H. Hamilton, Hamilton Technologies

William R. Hackler, Hamilton Technologies

DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MC.2008.541

Based on a preventive, development-before-the-fact philosophy that does not allow errors in the first place, the Universal Systems Language has evolved over several decades, offering system engineers and software developers a language they can use to solve problems previously considered next to impossible to solve with traditional approaches.

1. M. Hamilton, "Inside Development Before the Fact," cover story, editorial supplement, 8ES–24ES, Electronic Design, Apr. 1994
2. M. Hamilton and W.R. Hackler, "Universal Systems Language for Preventative Systems Engineering," Proc. 5th Ann. Conf. Systems Eng. Res. (CSER), Stevens Institute of Technology, Mar. 2007, paper #36.
3. M. Hamilton, "Zero-Defect Software: The Elusive Goal," IEEE Spectrum, Mar. 1986, pp. 48–53.
4. M. Hamilton, "The Heart and Soul of Apollo: Doing It Right the First Time," Proc. 7th Int'l Military and Aerospace Programmable Logic Devices (MAPLD) Conf., NASA Office of Logic Design, paper S216, 2004.
5. M. Hamilton and W.R. Hackler, "Reducing Complexity: It Takes a Language," Innovations in Systems and Software Eng. J., NASA, to be published by Springer Verlag, 2009.
6. M. Hamilton, Shuttle Management Memo #14, Charles Stark Draper Laboratory, Cambridge, Mass., 1972.
7. M. Hamilton, What Is an Error?, tech. note, HTI, Cambridge, Mass., 1991.
8. M. Hamilton and S. Zeldin, "Higher Order Software—A Methodology for Defining Software," IEEE Trans. Software Eng., vol. SE-2, no. 1, Mar. 1976, pp. 9–32.
9. B. Krut Jr., Integrating 001 Tool Support in the Feature-Oriented Domain Analysis Methodology, tech. report CMU/SEI-93-TR-11, ESC-TR-93-188, SEI, Carnegie Mellon Univ., 1993.
10. M. Ouyang and M.W. Golay, An Integrated Formal Approach for Prototyping High-Quality Software of Safety-Critical Systems, tech. report MIT-ANP-TR-035, MIT, 1995.
11. Software Productivity Consortium, "Object-Oriented Methods and Tools Survey," SPC-98022-MC, v.02.00.02, Dec. 1998.
12. M. Hamilton and W.R. Hackler, "Deeply Integrated Guidance Navigation Unit (DI-GNU) Common Software Architecture Principles," DAAAE30-02-D-1020 and DAAB07-98-D-H502/0180, Picatinny Arsenal, NJ, 2003–2004.
13. J. Keyes, Internet Management, chapt. 30–33 on 001-Developed Systems for the Internet, pp. 391–511, Auerbach, 2000.
14. HTI, 001 Tool Suite (1986–2008); www.htius.com and http://icb.nasa.gov001 orhtius.com/001_nasa.
15. M. Hamilton, "Development Before the Fact in Action," cover story, special editorial supplement, 22ES–30ES, Electronic Design, June 1994.
16. D. Bolinger and D.A. Sears, Aspects of Language, Harcourt Brace Jovanovich, 1981, p. 109.
17. M. Hamilton and W.R. Hackler, "Towards Cost Effective and Timely End-to-End Testing," HTI, prepared for Army Res. Lab., contract no. DAKF11-99-P-1236, 17 July 2000.
18. S. Cushing, "A Note on Arrows and Control Structures: Category Theory and HOS, Candidate BMD Data and Axioms," contract no. DASG60-77-C-0155, HOS, prepared for Ballistic Missile Defense, Advanced Technology Center, June 1978.
19. S. Friedenthal, A. Moore, and A. Steiner, "OMG Systems Modeling Language (OMG SysML) Tutorial," Proc. 16th Ann. Int'l Symp. INCOSE 2006, INCOSE, 2006.
20. M. Hamilton and W.R. Hackler, "A Formal Universal Systems Semantics for SysML," Proc. 17th Ann. Int'l Symp. INCOSE 2007, INCOSE, 2007, paper #8.3.2.
21. Object Management Group, "Systems Modeling Language," v. 1.0, 2006; www.omgsysml.org.
22. Department of Defense, "National Test Bed Software Engineering Tools Experiment—Final Report," vol. 1, Experiment Summary, Table 1, p. 9. Dept. of Defense Strategic Defense Initiative Organization, Washington, D.C., Oct. 1992.
23. M. Schindler, Computer-Aided Software Design, John Wiley &Sons, 1990.

Index Terms:

NASA, Universal Systems Language

Citation:

Margaret H. Hamilton, William R. Hackler, "Universal Systems Language: Lessons Learned from Apollo," Computer, vol. 41, no. 12, pp. 34-43, Dec. 2008, doi:10.1109/MC.2008.541

Peer Review Notice | Give Us Feedback

Usage of this product signifies your acceptance of the Terms of Use.