Elegant space systems: How do we get there?

Can the space industry produce elegant systems? If so, how? Space systems development has become process-centric, e.g., process creation or modification is the default response to most development and/or operations challenges when problems are encountered. But is that really effective? An increasing number of researchers and practitioners disagree with such an approach and suggest that elegance is as important to a system and its operation as fulfillment of technical and contractual requirements; consequently they are proposing a review and refreshment of the systems engineering practice. Elegance is generally recognizable, but hard to achieve deterministically. The research community has begun an endeavor to define what elegance is in systems engineering terms, find ways to measure or at least characterize it, and create or adapt philosophies and methodologies that promote elegance as a design objective (driver?). This paper asserts that while elegance cannot be engineered in a traditional sense, it can emerge as a natural result of design activity. This needs to be enabled and can be facilitated, but ultimately depends on the talent of the design teams as individuals and as a group. This paper summarizes existing technical definitions of elegance and discusses a) how it can be pursued and b) cultural conditions and habits that help elegance emerge during the development and operation of a space system.

[1]  Robert A. Frosch A new look at systems engineering , 1969, IEEE Spectrum.

[2]  Walter G. Vincenti,et al.  What Engineers Know and How They Know It: Analytical Studies from Aeronautical History. , 1992 .

[3]  Ivy Hooks,et al.  Why Johnny Can't Write Requirements , 1990 .

[4]  Lawrence D. Pohlmann,et al.  The Engineering Design of Systems – Models and Methods , 2000 .

[5]  Joseph Kasser,et al.  Yes systems engineering, you are a discipline , 2012 .

[6]  Ghassan Aouad,et al.  A Requirements Engineering Framework for Integrated Systems Development for the Construction Industry , 2006, J. Inf. Technol. Constr..

[7]  Steven A. Billow The role of elegance in system architecture and design , 1999 .

[8]  Eberhardt Rechtin,et al.  The Art of Systems Architecting (3rd Edition) , 2013 .

[9]  Ian Sommerville,et al.  Socio-technical systems: From design methods to systems engineering , 2011, Interact. Comput..

[10]  Bernhard Meyer M Eng Ing P Eur 3.4.2 Putting the System Back Into Systems Engineering , 2014 .

[11]  Paul Collopy,et al.  A Research Agenda for the Coming Renaissance in Systems Engineering , 2012 .

[12]  G. Mann The Quark and the Jaguar: adventures in the simple and the complex , 1994 .

[13]  Gary Belie Non-Technical Barriers to Multidisciplinary Optimization in the Aerospace Industry , 2002 .

[14]  Ivy Hooks Why Johnny Still Cannot Write Requirements , 2010 .

[15]  Richard Beasley,et al.  4.3.1 The Barriers to Systems Thinking , 2012 .

[16]  Azad M. Madni,et al.  Elegant systems design: Creative fusion of simplicity and power , 2012, Syst. Eng..

[17]  Roshanak Nilchiani,et al.  Using Maslow's hierarchy of needs to define elegance in system architecture , 2013, CSER.

[18]  Karl T. Ulrich,et al.  Product Design and Development , 1995 .

[19]  Robert Cloutier,et al.  Applicability of Patterns to Architecting Complex Systems , 2008 .

[20]  Petra Badke-Schaub,et al.  METHODS IN PRACTICE – A STUDY ON REQUIREMENTS FOR DEVELOPMENT AND TRANSFER OF DESIGN METHODS , 2008 .

[21]  Joseph Kasser,et al.  3.4.1 Yes systems engineering, you are a discipline , 2012 .

[22]  Ralph Johnson,et al.  design patterns elements of reusable object oriented software , 2019 .