Engineering Manager MBSE what rationale

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

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

Elaboration

It will also mean:

  • Considering support and resources to run small MBSE trials, or engage with other parties (such as academia) who might be running such trials;
  • Establishing a migration strategy, addressing: training, tooling, infrastructure, processes, internal and external stakeholders affected;
  • Establish a migration plan to implement your adoption strategy;
  • Obtaining resources and funding to support the execution of the plan;
  • Monitoring and course-correcting as necessary.

Rationale

As an engineering manager the focus is on the appropriate engineering contribution to effective development to cost, quality and timescale. This then brings in all the perspectives of persons, process, tools, infrastructure, interoperability, configuration control, technical risk, lean vs agility, and appropriateness of approach for the given level of integrity (safety level etc).

Conventional document-based systems engineering (DBSE) is a known quantity (to some extent). Adopting a MBSE approach requires a different skill set and experience, different tools, different infrastructure and a profile of progress for the development that is likely to be significantly different to that for DBSE.

Model Based Systems Engineering Wiki

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox