Model-Based Systems Engineering

As organizations move to agile practices to reduce development and delivery time, they’re learning that something is holding them back. Traditional, heavily structured, document-based systems engineering (DBSE) contradicts agile software development’s fast-paced, iterative nature. Documents are not robust enough to support complex systems or system-of-systems (SoS) development.

In contrast, model-based systems engineering (MBSE) keeps pace with agile development and, consistent with the Navy’s “Compile to Combat in 24 Hours” or “C2C24” initiative, helps to get innovations into warfighters’ hands more reliably and more quickly.

Generating deliverables from systems models, instead of manually-maintained documents, provide several benefits:

• Reduce slippage, keep the projects on-track
• Provide automated consistency among work products
• Save on development costs (re-coding and re-testing) needed to correct errors that are often produced by manual documentation methods and inconsistent ways of communicating system changes
• Improve the quality of software releases by ensuring stakeholders have accurate and complete information on the system
• Quickly generate real-time documentation that provides definitive answers to stakeholders’ questions
• Save time and money by eliminating the extra, manual step required to maintain traditional documentation methods (Word documents, Excel spreadsheets, etc.)

A model-based approach to systems engineering provides real-time, reliable information for stakeholders working on projects or reviewing and approving system releases. Unlike static documents that may or may not be current, system models are centralized, always current, and get the right information to the right people at the right time. No longer will stakeholders have concerns about the integrity of system information. MBSE provides automated consistency among work products throughout the development lifecycle.

Unlike a document-based system engineering methodology that frequently follows development, an MBSE methodology leads system design and development. Developing and maintaining a model of a system in an automated, collaborative, easily accessible, and secure framework is a significant improvement over a manual, time-consuming, error-prone, document-based approach to systems engineering.

• With MBSE, a system model drives software development. This process leverages modeling to ensure that the impact of software updates is analyzed system-wide before being implemented.
• Based on system design and system information, when updates are implemented, networked systems models are instantly updated, so changes are quickly and accurately made systems-wide.
• The underlying system model’s metadata and data model allow for the generation of specific views for specific stakeholders. Model viewpoints reduce information overload and ensure only relevant information is provided to developers, testers, integrators, decision-makers, and other stakeholders.

Developers and engineers have a vested interest in committing to MBSE as the outcomes are mutually beneficial. Rite-Solutions’ MBSE methodology is stakeholder-centric and focused on frequent stakeholder interaction and input, and iterative deliveries.

The extensibility of SysML and modeling tools are powerful and can be overwhelming at first. Rite-Solutions’ OMG-Certified Systems Modeling Professional (OCSMP) system modelers work closely with customers to ensure well-formed models are created and yield the best ROI by:

• Prioritizing organization needs and system requirements
• Providing training materials, videos, support
• Utilizing proven enterprise standards

Our custom MBSE solutions allow for the leading modeling tool, Cameo Systems Modeler, to work effectively with “V”, Waterfall, or Agile methodologies and processes. Rite-Solutions’ MBSE experts have experience in classified environments and help organizations transition from a document-based systems engineering approach to a model-based approach.