{"id":55203,"date":"2021-07-22T03:00:09","date_gmt":"2021-07-22T10:00:09","guid":{"rendered":"https:\/\/www.jamasoftware.com\/?p=55203"},"modified":"2026-07-19T13:31:54","modified_gmt":"2026-07-19T20:31:54","slug":"getting-started-with-model-based-systems-engineering-mbse","status":"publish","type":"post","link":"https:\/\/www.jamasoftware.com\/legacy\/blog\/2021\/07\/22\/getting-started-with-model-based-systems-engineering-mbse\/","title":{"rendered":"Getting Started with Model-Based Systems Engineering (MBSE)"},"content":{"rendered":"

\"Model-Based<\/p>\n

For companies building complex systems whose stakeholders come from diverse engineering and business disciplines and need to have very precise and efficient communications,\u00a0<\/span>Jama\u00a0Connect\u00a0provides\u00a0a collaborative,\u00a0100% web-based\u00a0MBSE\u00a0platform and a proven systems engineering approach to product development.\u202fJama Connect\u00a0provides\u00a0a path to companies embracing MBSE\u202fwhere the application of\u202fcollaboration,\u202fmodeling, and methods\u202freduces time and effort\u202facross\u202fthe\u202flifecycle.\u202fWe call that path\u00a0<\/span>Jama Connect for Traceable MBSE\u2122.\u00a0<\/span><\/p>\n

Jama Connect for Traceable MBSE\u00a0is a single platform that combines requirements, architectures, behaviors, and\u00a0V&V\u00a0into a single model of the system by\u00a0applying\u00a0structure for the data; rules for the data; and a\u00a0consistent\u00a0interface\u00a0language\u00a0between parts of the system. A Jama Connect\u00a0model provides engineers, project managers, business analysts, or any stakeholder, an organized way to address all aspects of the system consistently with the assurance of completeness.<\/span>\u00a0<\/span><\/p>\n

MBSE\u00a0Defined by Industry<\/span><\/b>\u00a0<\/span><\/h3>\n

The International Council on Systems Engineering (INCOSE) describes\u00a0MBSE\u00a0as\u00a0the \u201cformalized application of modeling to support system requirements, design, analysis, verification, and validation activities beginning in the conceptual design phase and continuing through-out development and later lifecycle phases.\u201d\u00a0<\/span>\u00a0<\/span><\/p>\n

NASA says MBSE \u201cinvolves applying software-based tools to capture systems engineering evidence\u2014typically called \u201cartifacts\u201d\u2014in a systematic, disciplined way that allows people to manage complexity while communicating effectively across the life cycle of a system.<\/span>\u00a0<\/span><\/p>\n

What\u00a0is a\u00a0model?\u00a0Don\u2019t\u00a0be fooled.<\/span><\/b>\u00a0<\/span><\/h4>\n

It is a\u00a0myth that a system model can only be created in a\u00a0UML\u00a0or\u00a0SysML\u00a0tool. Models can be expressed texturally, mathematically, visually, or physically and are meant to\u00a0assist\u00a0in helping people look at problems from different directions. Jama Connect represents a model as a project\u00a0containing\u00a0textural\u00a0data items, views,\u00a0graphical\u00a0diagrams, and collaboration content.\u00a0<\/span>\u00a0<\/span><\/p>\n

NASA\u2019s\u00a0definition\u00a0provides\u00a0a good deal of\u00a0information,\u00a0but they\u00a0don\u2019t\u00a0even use the word \u201cmodel\u201d in their description.\u00a0Lenny Delligatti, one of the most respected MBSE experts\u00a0in the world\u00a0wrote that,\u00a0\u201cA modeling\u00a0<\/span>method<\/span><\/b>\u00a0is something like a road map; it\u2019s a documented set of design tasks that a modeling team performs to create a system model. More precisely,\u00a0it\u2019s\u00a0a documented set of design tasks that ensures that everyone on the team is building the system model consistently and working toward a common end point. Without such guidance, there will be wide variance in the breadth, depth, and fidelity that each member of the team builds into the system model.\u201d\u00a0<\/span>\u00a0<\/span><\/p>\n

For example, a s<\/span>witch in a system is expecting the command “On” but for some reason receives the command “Start.\u201d The switch will not function. The “On” and “Start” is the communication language and must be consistent.<\/span>\u00a0<\/span><\/p>\n

What\u00a0in simple terms\u00a0is a model then?\u00a0Wikipedia tells us that a \u201cmodel is an informative\u00a0<\/span>representation<\/span><\/b>\u00a0of an object, person or system\u201d\u00a0and INCOSE defines a model as \u201ca simplified version of a concept, phenomenon, relationship,\u00a0structure or system.\u201d\u00a0<\/span>\u00a0<\/span><\/p>\n

Before the invention of\u00a0SysML,\u00a0we used to use a document called an “Interface Control Document (ICD)” to describe the syntax of interfaces between\u00a0different parts\u00a0of a system, often\u00a0physical.\u00a0While essential, the ICD lacked the ability to describe scenarios which the interfaces would be used for.\u00a0While a\u00a0SysML\u00a0model allows for communication\u00a0of\u00a0scenarios to be documented, it often\u00a0lacks the ability to communicate the depth of requirement needed to describe the core workings of each part.\u00a0This puts a heavy\u00a0onus\u00a0on\u00a0the verification needed to ensure a part on its own was working as intended.\u00a0\u00a0<\/span>\u00a0<\/span><\/p>\n

While\u00a0SysML\u00a0is a wonderful\u00a0language to\u00a0represent\u00a0abstractions and there are some\u00a0fine\u00a0tools out there that\u00a0let you do some\u00a0powerful\u00a0things (I want to say something different here); it is still immature in the core\u00a0aspects of systems engineering\u00a0as it relates to\u00a0communication, cross-domain collaboration,\u00a0project management\u00a0including cost and schedule,\u00a0and\u00a0oversight of verification and validation activities\u00a0to name a few.\u00a0<\/span>\u00a0<\/span><\/p>\n

\n
RELATED: MBSE Made Easy \u2013 Overcoming the Organizational Challenges\u00a0<\/a><\/h5>\n
\n

Jama Connect for Traceable MBSE\u2122 \u2013 The Nuts and Bolts<\/span><\/b>\u00a0<\/span><\/h2>\n

\"JamaMBSE in\u00a0simplest terms is a framework for problem solving and system expression.\u00a0In\u00a0traditional systems engineering\u00a0the\u00a0domains of requirements, architectures, V&V\u00a0and behavior are recorded and\u00a0analyzed in a series of documents or data structures with loosely connected affiliations.\u00a0Our Traceable MBSE combines these\u00a0four\u00a0domains\u00a0into a single model of the system by applying: structure for the data;\u00a0rules\u00a0for the data;\u00a0and\u00a0a\u00a0consistent\u00a0interface\u00a0language\u00a0between parts of the system,\u00a0which\u00a0in combination\u00a0we at Jama\u00a0Software\u00a0call a \u201cframework.\u201d\u00a0The\u00a0framework provides engineers, project managers,\u00a0business analysts, or any stakeholder,\u00a0an organized way to address all aspects of the system consistently with the assurance of completeness.<\/span>\u00a0<\/span><\/p>\n

The\u00a0<\/span>Jama Connect for Traceable MBSE\u00a0framework takes requirements, architectures,\u00a0behaviors, and V&V and forms their data into a\u00a0query-able\u00a0mesh. As development progresses\u00a0the mesh becomes more stitched together.\u00a0A built-in ruleset\u00a0that uses a consistent\u00a0language,\u00a0constrains users to create the correct associations between the data elements. The framework\u2019s ruleset\u00a0eliminates\u00a0risk that manual methods or tools lacking these constraints introduce.\u00a0<\/span>Jama Connect for Traceable MBSE\u00a0also supports\u00a0leveling –\u00a0representation of system\u00a0decomposition\u00a0within a model.\u00a0Each successive level will follow the same consistent ruleset.<\/span>\u00a0<\/span><\/p>\n

Visualization\u00a0is an important part of\u00a0<\/span>Jama Connect for Traceable MBSE\u00a0and plays\u00a0a major role\u00a0in communication of information and ideas.\u00a0Data is easily visualized in\u00a0an easy to navigate hierarchal tree\u00a0view. This view not only displays the content of the data but also\u00a0how the elements are tied to each other.\u00a0These structures can be represented visually as a series of diagrams within the model.\u00a0<\/span>\u00a0<\/span><\/p>\n

Requirements<\/span><\/b>\u00a0<\/span><\/h4>\n

Requirements\u00a0are typically the first data elements to be worked on in the model.\u00a0<\/span>Jama Connect for Traceable MBSE\u2019s\u00a0flexibility gives users the ability to define unlimited levels of requirements \u2013 even those considered\u00a0outside the \u201csystem\u201d level.\u00a0A\u00a0Need\u00a0Requirement\u00a0which\u00a0is\u00a0an\u00a0input to the systems engineering process,\u00a0might consist of multiple\u00a0types\u00a0such as:\u00a0user needs,\u00a0ConOPS,\u00a0business requirements, mission\u00a0objectives, goals, regulatory requirements, or even constraints to name a few.\u00a0A needs analysis\u00a0is\u00a0performed\u00a0to flesh out those requirements which are human-centric.\u00a0Systems\u00a0engineers will analyze\u00a0all\u00a0the\u00a0broad\u00a0and at times abstract\u00a0needs\u00a0and then refine them into\u00a0system level requirements that are\u00a0representative of the system\u00a0and might describe\u00a0all\u00a0the functions that the system shall deliver as well as\u00a0non-functional characteristics such as performance or reliability of the system.\u00a0<\/span>\u00a0<\/span><\/p>\n

In\u00a0Jama Connect\u00a0each\u00a0need and\u00a0system requirement\u00a0is captured as a unique entity with its own ID. As a single entity it can then\u00a0be managed, version controlled, and linked to other entities.\u00a0When using\u00a0<\/span>Jama Connect for Traceable MBSE\u00a0framework, it\u00a0provides\u00a0mechanisms\u00a0that\u00a0keep\u00a0needs and\u00a0system\u00a0requirements\u00a0appropriately leveled\u00a0and\u00a0describe how they are\u00a0linked to each other.\u00a0This link\u00a0itself also has a name and\u00a0is called\u00a0\u201cderivedReq\u201d which is\u00a0similar\u00a0terminology used in\u00a0the\u00a0SysML\u00a0language.<\/span>\u00a0<\/span><\/p>\n

Behaviors<\/span><\/b>\u00a0<\/span><\/h4>\n

Behaviors\u00a0assist\u00a0the\u00a0systems\u00a0engineer in\u00a0identifying\u00a0the\u00a0functions, sub-functions, and interactions that the system performs.\u00a0Behaviors\u00a0can be elicited from needs and requirements through techniques such as\u00a0use cases, activities, states,\u00a0interactions, sequences\u00a0and more.\u00a0Behaviors\u00a0are most often in the form of a verb\u00a0(ex:\u00a0regulate voltage,\u00a0make deposit,\u00a0heat water,\u00a0charge controller, brake\u2026).\u00a0Capturing behaviors\u00a0adds\u00a0value because they help explain how the system\u00a0will work\u00a0and\u00a0sometimes more importantly, what could go wrong.\u00a0Behavior\u00a0can\u00a0assist\u00a0in\u00a0establishing\u00a0the cost and complexity\u00a0of the system.\u00a0Functions\u00a0can be analyzed and become a deciding factor for which\u00a0requirements\u00a0are then used to build the system.\u00a0<\/span>\u00a0<\/span><\/p>\n

\"Jama<\/p>\n

In Jama Connect behaviors can be richly\u00a0annotated\u00a0so\u00a0one can\u00a0capture the full\u00a0reasoning. This is extremely useful to stakeholders that are not necessarily modelers yet need this information to\u00a0make informed decisions.\u00a0<\/span>\u00a0<\/span><\/p>\n

Architecture<\/span><\/b>\u00a0<\/span><\/h4>\n

Application of MBSE\u00a0is not complete without tying in architectures\u00a0and making them\u00a0be\u00a0a\u00a0central point\u00a0of data.\u00a0Architectures can be defined to conceptually\u00a0represent\u00a0functions of the system, structure of the system to subsystems, physical components of the system,\u00a0or even behaviors of the system. An architecture is organized so that its own structure conveys meaning\u00a0and relationships between its members.\u00a0In Jama Connect,\u00a0architecture objects can be managed as discrete elements where relationships to other data such as requirements can be made. It is also possible to\u00a0create diagram to illustrate the relationships between the elements.<\/span>\u00a0<\/span><\/p>\n

\"Jama<\/p>\n

V&V<\/span><\/b><\/h5>\n

The verification and validation of the model and its entities within it is the\u00a0last major\u00a0domain\u00a0for MBSE.\u00a0Any element defined within the model can be verified or\u00a0validated\u00a0through means of\u00a0analysis alone,\u00a0review,\u00a0trace demonstration, or even by test execution collecting pass\/fail status.\u00a0An MBSE model\u00a0<\/span>\u00a0<\/span><\/p>\n

Jama Connect for Traceable MBSE\u00a0tests and\u00a0validates\u00a0system characteristics early with engineers and stakeholders for fast feedback on design decisions and phase it is believed that this will:<\/span>\u00a0<\/span><\/p>\n