Readings in Systems Engineering

_¢q .. SP-6102 -" READINGS IN SYSTEMS ENGINEERING Edited by Francis T. Hoban and William M. Lawbaugh co ! (NASA-SP-6102) REAOINGS IN SYSTEMS N93-24678 ENGINEERING (NASa) 215 p --THRU-- N93-24693 Unclas H1/31 0158570 .J T ,j J READINGS IN SYSTEMS ENGINEERING Edited by Francis T. Hoban and William M. Lawbaugh Scientific and Technical Information Program N_A National Aeronautics and Space Administration Washington, DC 1993 READINGS IN SYSTEMS ENGINEERING Introduction by Francis T. Hoban and William M. Lawbaugh Author Title Page Robert A. Frosch A Classic Look at Systems Engineering 1 .*J,_._r_ Defense Systems Management Systems Engineering Overview and Process 9 College Paul E. Lewkowicz Systems Engineering for 17 Very Large Systems Marshall Space Flight What is a System ? NASA 's Phased 23 Center SE Handbook Project Description J NASA SE Handbook (Draft) Management Issues in Systems Engineering 35 Tony Fragomeni and Spacecraft Systems Engineering: An 79 :_ Mike Ryschkewitsch Introduction to the Process of GSFC Owen Morris SE&I and Management for Manned 87 Space Programs Charles W. Mathews The Systems Engineering Role in Top-Level Requirements 105 John D. Hodge Cost Considerations in the Systems Engineering Process 115 John E. Naugle Systems Engineering and User Requirements 127 " Eugene Kranz and SE&I in Manned Missions Christopher Kraft J Robert O. Aller Systems Engineering for Operational 157 ! Support Systems / John F. Yardley and Political and Institutional Factors of 163 zl David Wensley Systems Engineering i ] Loren A. Lemmerman Optimization in the SE Process 173 _ j_ / NASA Investigation Board Initial Flight Anomalies of Skyiab I 181 : NASA Investigation Board The Seasat Failure 201 George Trimble Defining Systems Engineering INTRODUCTION INTRODUCTION by Francis T. Hoban and William M. Lawbaugh Systems engineering is not new--it's been This group, in its final report to the around for quite some time. The ancient NASA administrator on December 30, 1986 engineers who designed and built the pyra- also recommended a renewed effort in the mids practiced some form of what we today education and training of the NASA pro- call "systems engineering." Modern systems gram and project management workforce. engineering emerged during and immediate- Unwritten but well understood in this rec- ly following World War II as weapons grew ommendation was renewed emphasis on sys- into weapon systems, due to the degree of tems engineering training. It was no easy complexity in design, development and de- task to build a knowledge base, create a li- ployability. The advent of space exploration brary collection and develop courses and further increased the need for and use of sys- workshops in systems engineering, but the tems engineering processes and practices. efforts took shape, as one essential part of The Apollo Program is perhaps NASA's NASA's Program and Project Management best example of the application of systems Initiative. This became a continuing educa- engineering. During Apollo, systems engi- tion process assisted on an Agency-wide neering processes were in place in NASA basis by the Systems Engineering Working Headquarters and at all field centers. At Group. some locations the process was formalized; at Today most large engineering organiza- others it was a back-of-the-envelope applications, including NASA, have a systems engi- tion, but it was in place. It was widely prac- neering process containing elements both ticed, and it sustained a young and vibrant common and unique to those practiced by organization during the design, development other organizations. To document these and operations of the world's greatest engi- processes NASA is now involved in the prep- neering feat. NASA systems engineering aration of the first Agency-wide systems capabilities grew out of its NACA heritage, engineering manual. The manual addresses bolstered by people from the Department of common systems engineering practices and Defense, industry and academia who joined tools, as well as those unique to NASA and the team during the Apollo build-up. It the aerospace industry. This manual, togeth- should be noted that during the Apollo era, er with those describing the individual Cen- systems engineering was conducted without ters' practices, will fully document systems Agency-wide guidance, standards or lexicon. engineering at NASA and add to the educa- After Apollo, the various NASA centers con- tion process. tinued to implement systems engineering on This present collection was inspired by complex projects but perhaps with less vigor seven papers prepared by the NASA Alumni and enthusiasm than that displayed during League, illustrating the members' systems Apollo. engineering experience. These papers make The discipline again became a priority in up the heart of this collection. We have sup- NASA when the study team of the National plemented them with papers describing Academy of Public Administration, led by industry processes and other governmental Lt. General Sam C. Phillips, recommended practices to illustrate the diversity of sys- the strengthening of systems engineering in tems engineering as it is formulated and NASA. practiced. This is one discipline that clearly READINGS IN SYSTEMS ENGINEERING benefits from cross-fertilization and infusion Systems Engineering Handbook stress the of new ideas. engineering aspects of successful manage- There is also a wide variety of tools and ment of aerospace systems. techniques described herein, some standard In our second section, devoted to specific and some unique. It is not unlike an elite applications of systems engineering, we be- crew of talented carpenters showing up for a gin with two engineers from the Goddard job, each with some different tools in their re- Space Flight Center whose presentations are spective toolboxes, and each with different famous for explaining the process and pro- tricks or techniques to save time or money-- ducts of systems engineering in unmanned to do each one-of-a-kind job better, cheaper, spacecraft. Tony Fragomeni and Mike faster. Ryschkewitsch are associate chief and chief If all the authors of Readings in Systems respectively of Goddard's new Systems Engi- Engineering were ever to assemble in one neering Office. Owen Morris, who was place, there would be some unanimity on ba- NASA's Lunar module project manager and sics and essentials but much debate and the Space Shuttle Systems and Engineerng downright disagreement on the particulars. manager, then discusses the history of sys- Nevertheless, the meeting would be lively tems engineering and integration (SE&I) and interestingma decent description of the management in manned space programs. dynamic process of systems engineering it- Chuck Mathews, past president of the NASA self. Alumni League, and NASA's manager of the Gemini Program, director of the the Skylab APPROACH Program and associate administrator for Ap- plications, then focuses upon the systems en- We begin our collection with a now-famous gineering role in establishing, verifying and speech delivered by Bob Frosch to a group of controlling top-level program requirements. engineers in New York in 1969, shortly John D. Hodge, a 25-year veteran of the before his appointment as NASA Adminis- Department of Transportation and NASA, trator. The speech sets the tone best of all for including the Mercury, Gemini, Apollo and this volume: Frosch urges a common sense Space Station programs, retiring as an asso- approach to systems engineering. ciate administrator, explains cost consider- When weapons evolved into weapons sys- ations in the systems engineering process, tems, the Department of Defense took the urging clear definition of requirements, sta- lead in systems, engineering. Today the DoD ble management and strong central control approach is widely recognized, and so we to allocate funds properly. present the newly revised (1990) description John E. Naugle, retired NASA associate of the systems engineering process from the administrator and chief scientist, describes Defense Systems Management College at the dual role of "master" and "servant" for Fort Belvoir, Virginia. A senior project engi- the systems engineer, from the requirements neer formerly with Hughes Aircraft, Paul E. phase to preliminary design. Eugene F. Lewkowitcz, then discusses requirement Kranz, director of the Johnson Space Center analysis, technology assessment, solution Mission Operations Directorate, and synthesis and performance verification for Christopher C. Kraft Jr., former director of very large systems. Marshall Space Flight the Johnson Space Center, stress manned Center does it differently, but one of the best mission operations and SE&I. Robert O. descriptions of Phase A through C can be Aller, recently retired associate administra- found in Marshall's systems engineering tor for space operations, views operations handbook. To close out this overview section, support as the infrastructure of people, excerpts from the forthcoming NASA procedures, facilities and systems for flight ii INTRODUCTION success. John Yardley, NASA's associate scribed the uncritical acceptance of "stan- administrator for manned space flight dur- dard" or "flight proven" equipment that ing the Space Shuttle development, asserts failed in 1978. But no one wants to end on a that the systems engineer should consider 10 negative, so we reproduce a Johnson Space different politicaland nontechnical groups. Center engineer's attempt to define and ex- Associate David Wensley suggests ways of plain "systems

Load more