Abstract
ABSTRACTProcesses and procedures are the heart of current descriptions of systems engineering. The “vee diagram,” ISO 15288, the INCOSE Systems Engineering Handbook, and enterprise‐specific business process models focus attention on process and procedure. However, there is a non‐procedural way to view systems engineering. This approach is to describe the configuration space “navigated” by systems engineering, and what is meant by system trajectories in that space, traveled during system life cycles. This sounds abstract because we have lacked explicit maps necessary to describe this configuration space. We understand concrete steps of a procedure, so we focus there. But where do these steps take us? And what does “where” mean in this context? Clues are found in recent discoveries about ancient navigation, as well as later development of mathematics and physics. This paper, part I of a case for stronger model‐based systems engineering (MBSE) semantics, focuses on the underlying configuration space inherent to systems.
Reference44 articles.
1. Mental Representation and Processing of Geographic Knowledge
2. Berg E.2014. “Affordable Systems Engineering: An Application of Model-Based System Patterns to Consumer Packaged Goods Products Manufacturing and Distribution.” Presented at the Annual International Workshop of INCOSE (MBSE Workshop) Los Angeles US-CA 25-28 January.
3. Beihoff B. andW.Schindel.2012. “Systems of Innovation I: Models of Their Health and Pathologies.” Paper presented at the 22nd Annual International Symposium of INCOSE Rome IT 9-12 July.
4. Bradley J. M.Hughes andW.Schindel 2010. “Optimizing Delivery of Global Pharmaceutical Packaging Solutions Using Systems Engineering Patterns.” Paper presented at the 20th Annual International Symposium of INCOSE Chicago US-IL 12-15 July.
5. Casagrande-Kim Roberta et al. n.d.NYU ISAW web site and bibliography on ancient cartography:http://isaw.nyu.edu/exhibitions/space/bibliography.html.1