Engineering Manager MBSE why rationale

From Model Based Systems Engineering Wiki
Revision as of 12:56, 22 September 2017 by Dr. Julian Johnson (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Elaboration

Although there is mixed evidence of sound Return on Investment (ROI) in MBSE approaches over 'short' time frames, there is compelling evidence that MBSE approaches do systematically offer improved rigour and thoroughness to SE compared with the outcome of the same activities performed with DBSE; some authors would argue that asking 'what is the ROI for MBSE adoption?' is asking the wrong question; a better question would be 'what improvements in quality and error reduction do I realise with adoption of MBSE compared to DBSE?.

Rationale

The trend to adopt MBSE has emerged for several reasons: a few spectacular failures of DBSE often due to relatively simple reasons that might otherwise have been avoided by the adoption of more rigour from models (for instance, the Mars Lander failure, due to mis-match of engineering units between different engineering teams); the wish to increase rigour to early-phase systems engineering activities (requirements elicitation and management...).

Model Based Systems Engineering Wiki

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox