MBSE & MDA

From Model Based Systems Engineering Wiki
Jump to: navigation, search

Contents

Objectives

1. Identify two or three definitive sources for a definition of MBSE(so as not to reinvent the wheel), but context for 3;

2. Identify two or three definitive sources for a definition of MDA (ditto);

3. Form a coherent explanation (graphical and textual) for the relationship(s) of MBSE and MDA;

4. Provide one or more Use Cases or scenarios in which MDA can support one or more SE activities in an MBSE context, and provide illustrations of same.

(Source: Email from JJ 26/4/2016, and subsequent reactions from team members, as recorded in sub-group status report 19/5/2016, [1] )

Team

The MBSE & MDA team currently comprises the following members:

Member Organisation Role
Julian Johnson Holistem Lead
Hedley Apperly PTC Member
Alistair Blair Thales Member
Ian Clark MBDA Member
Chris Raistrick Abstract Solutions Member
Francis Thom Fran-Sys-Thom Ltd Member
Neil Burt Member

Progress Reports

2016

Meeting Notes

2017

Documents

Date Title Author Link
03-03-16 MBSE and MDA; what are they and how do they interrelate? J Johnson Link
19-05-16 MDA at the MOD C Raistrick Link

Emerging Outputs

1 Definitive sources for a definition of MBSE

INCOSE Systems Engineering Vision 2020, INCOSE-TP-2004-004-02, September, 2007:

"Model-based systems engineering (MBSE) is the formalized application of modeling to support system requirements, design, analysis, verification and validation activities beginning in the conceptual design phase and continuing throughout development and later life cycle phases. "

Note the above definition is also cited by "A practical Guide to SysML The Systems Modelling Language", Friendenthal, Moore and Steiner, MK / OMG, second edition, 2012.

Final Report, Model-Based Engineering Subcommittee, NDIA, Feb. 2011:

"Model-Based Engineering (MBE): An approach to engineering that uses models as an integral part of the technical baseline that includes the requirements, analysis, design, implementation, and verification of a capability, system, and/or product throughout the acquisition life cycle."

(This definition located in Slide 8 of file Model-based-Systems-Engineering-MBSE-101.ppt, Model-based Systems Engineering (MBSE) 101, presented at INCOSE International Workshop, 25-26/1/2014, Torrance, CA, USA.)

Wikipedia Entry:

Model-based systems engineering (MBSE) is a systems engineering methodology that focuses on creating and exploiting domain models as the primary means of information exchange between engineers, rather than on document-based information exchange.

2 Definitive sources for a definition of MDA

OMG MDA site

The current version of the OMG MDA Guide 2.0 is available via that site as below:

MDA 2.0 Word format

MDA 2.0 pdf format

A subset of the Executive Summary from the above guide is:

"MDA provides an approach for deriving value from models and architecture in support of the full life cycle of physical, organizational and I.T. systems."

The Executive summary goes onto elaborate what it means by 'models' and how such models can be used:

"The MDA approach represents and supports everything from requirements to business modeling to technology implementations. The primary feature of MDA which enables us to deal with complexity and derive value from models and modeling is defining the structure, semantics, and notations of models using industry standards – models conforming to these standards are “MDA Models”. MDA models can then be used … (sentences removed-JJ). MDA models can represent systems at any level of abstraction or from different viewpoints, ranging from enterprise architectures to technology implementations. MDA “connects the dots” between these different viewpoints and abstractions."

3 A coherent explanation (graphical and textual) for the relationship(s) of MBSE and MDA

MBSE-MDA-single-page-visualisation-v1.1.jpg.JPG

4 Use Cases or scenarios in which MDA can support one or more SE activities in an MBSE context

Example Use Cases include:

1. Part-generation of software component of functionality through transformation, based on models of a) required / defined functionality b) target technology as model and c) transformation model.

2. Part-verification of cross-discipline design versus requirements by generation of correspondence (compliance) model via MDA transformation from two or more design models, model of requirements and transformation (comparison) model.

Model Based Systems Engineering Wiki

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox