MDD/MBE/MBSE
Model Driven Development (MDD), Model Based Systems Engineering (MBSE), and Model Based Engineering (MBE) all have one thing in common – models and modeling at their core.
Although each share similar goals, each have different purposes. It can be confusing when trying to understanding model-based methodologies because they can be used to describe either systems engineering, software engineering or both. Other model-based acronyms are Model Driven Engineering (MDE) and Model Driven Architecture (MDA). So what does it all mean and which is right for what the user needs?
- MDE is a generic term for any model-based development
- MBE pertaining to systems and software
- MBSE is for systems
- MDA and MDD are specifically for software
The most prominent MDE initiative is the Object Management Group’s (OMG) initiative Model-Driven Architecture (MDA), which is a registered trademark of OMG and is aimed at creating software engineering models that not constrained by implementation details. Model-Driven Development (MDD) is also an OMG trademark.
Model-Based Engineering (MBE) focuses on creating models of the elements of a system, the elements of the problem domain, or even the elements of the user requirements. Productivity is increased by defining common interfaces, simplifying the process of design, promoting communication between stakeholders, individuals and teams, and providing a coherent, common and consistent modeling and development environment. Models created using a standardized notation enhance knowledge capture and increase the reuse of the information. This in turn can result in reduced cycle time and lower maintenance costs to modify the design. MBE increases the ability to manage system complexity by enabling a system model to be viewed from multiple perspectives, and to analyze the impact of changes. Models can be used throughout the development lifecycle from conception to system implementation, maintenance and retirement. Models can be used by systems, software, and hardware engineers, project managers, test engineers, etc.
Artisan Studio enables MBE through its support of standards based modeling. Also, an Artisan Studio model can contain DoDAF/MODAF, SysML and UML modeling elements and provide traceability through the modeling lifecycle. Consequently, handover from architects to systems engineers to software engineers and test engineers and so on can all take place within the same model. Because the different profiles are integrated, SysML requirements can be used in DoDAF and UML projects, increasing traceability and impact analysis. In addition, because Artisan Studio is built on a repository, artifacts can be viewed, shared and controlled by all members of the team. Documentation, test scripts, code, reports etc, can all be generated from the model in a consistent and standard manner. Finally, the integration of third party tools such as Mathworks Simulink and Telelogic DOORS means that you can leverage your model information into other areas of engineering. Truly allowing your team to Work-as-One.
For more details download the Artisan Studio – Data Sheet.
