Model-Based Systems Engineering

  • O. Thomas HollandEmail author
Part of the Simulation Foundations, Methods and Applications book series (SFMA)


Today, we expect our systems to be highly sophisticated, intelligent, intuitive, robust, adaptive, and reliable. As technology, especially computational technology, has increased, so has our ability to imagine and develop even more capable and complex systems. This has progressed to the point where it is rare for an individual to understand all aspects of a system. In fact, it is typical that modern systems are the product of an army of highly trained specialists, each with expertise in traditionally diverse domains. In a modern system, the requirements developer, the mechanical engineer, the programmer, the cost analyst, the manager, and many others must work together to make a system a reality. Modern systems engineering recognizes the necessity of these varied perspectives yet must still achieve efficient and effective systems concepts, designs, implementations, and management. How multiple domains can be organized, managed, and sustained to achieve the development of a useful system is at the heart of systems engineering. In this chapter will discuss how Model-Based Systems Engineering (MBSE) is shifting the emphasis of the system engineering process away from the management of documents to describe a system, to an emphasis on a common, flexible, and persistent model of the system.


Object Management Group State Machine Diagram System Engineering Process Requirement Management Tool Shared Cultural Knowledge 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. Altova Inc (2014) SysML for Embedded Systems Modeling. Accessed 2014
  2. Box GEP, Norman RD (1987) Empirical model-building and response surfaces. Wiley, New YorkGoogle Scholar
  3. Brown B (2011) Model-based systems engineering: revolution or evolution? IBM Corporation, SomersGoogle Scholar
  4. DAU (2013) Defense acquisition guidebook. Defense Acquisition University, Washington DCGoogle Scholar
  5. IBM Corp (2014) Rational Rhapsody family. Accessed 2014.
  6. INCOSE (2007) Systems engineering vision 2020, s.l.: International council on systems engineering (INCOSE)Google Scholar
  7. LML (2013) Lifecycle modeling language. Accessed 2014
  8. NDIA Systems engineering division, M & S Committee, Model Based Engineering Subcommittee (2011) Model based engineering. s.l.: s.nGoogle Scholar
  9. No Magic Inc (2014) MagicDraw. Accessed 2014
  10. OMG (2005) Unified modeling language. Accessed July 2014
  11. OMG (2007) OMG systems modeling language. Accessed July 2014
  12. OMG (2012) OMG systems modeling language (OMG SysML) Version 1.3, s.l.: Object Management GroupGoogle Scholar
  13. Schneider F, Naughton H, Berenbach B (2012) A modeling language to support early lifecycle requirements modeling for systems engineering. Procedia, St. Lous, pp. 201–206Google Scholar
  14. Sparx Systems (2014) Full lifecycle modeling for business, software and systems. Accessed 2014

Copyright information

© Springer-Verlag London 2015

Authors and Affiliations

  1. 1.Naval Surface Warfare CenterDahlgrenUSA

Personalised recommendations