Premium
Maps or Itineraries? A Systems Engineering Insight from Ancient Navigators
Author(s) -
Schindel William D.
Publication year - 2015
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2015.00137.x
Subject(s) - context (archaeology) , focus (optics) , process (computing) , space (punctuation) , computer science , semantics (computer science) , diagram , systems engineering , software engineering , engineering , programming language , geography , archaeology , database , physics , optics , operating system
Processes and procedures are the heart of current descriptions of Systems Engineering. The “Vee Diagram”, ISO 15288, the INCOSE SE 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 MBSE Semantics) focuses on the underlying configuration space inherent to systems.