Difference between revisions of "MBSE Competencies"

From Model Based Systems Engineering Wiki
Jump to: navigation, search
 
(5 intermediate revisions by one user not shown)
Line 1: Line 1:
 
==Objectives==
 
==Objectives==
To define MBSE roles and identify the required competencies;
+
To understand the need for guidance on application of INCOSE competencies for MBSE.
Need to revisit this to properly understand what is trying to be achieved by this workstream that is not in material already available through INCOSE.
+
  
- Review the material on competence that is available through INCOSE
+
- Review the current INCOSE material on MBSE competence
  
- Understand how this material is applicable to the MBSE scope
+
- Review roles and associated competence scopes
  
- Define the ''modelling'' roles and suggested associated competency scope
+
Need to understand what the output from this working group will be:
 
+
- Z Guide
- Understand and develop the material that INCOSE will present going forward
+
- Omega Guide
 +
- U Guide
 +
- Paper
 +
- White paper
 +
- Don't panic or other book
  
 
==Team==
 
==Team==
Line 33: Line 36:
  
 
== Review of INCOSE competency framework ==
 
== Review of INCOSE competency framework ==
MBSE is considered as a cross cutting technique
+
MBSE is considered as a cross cutting technique as defined in the systems engineering handbook.
 
We need to understand what each of the competencies in the INCOSE competency framework (reference needed) means in the context of MBSE.
 
We need to understand what each of the competencies in the INCOSE competency framework (reference needed) means in the context of MBSE.
  
  
==Modelling Roles==
+
Here follows a model defining the terms as used in the ISECF v1.
  
Holt and Perry define the following roles for consideration of MBSE comptencies:
+
[[File:ISECF Modelling Sys Analysis definition.jpg‎]]
- Configuration manager
+
  
- Assessment manager
+
And the description field also includes some ideas of why the various parts of the competency exist:
  
- Requirements manager
+
Modelling
  
- Process manager
+
[[File:ISECF definition - Description - Modelling.jpg]]
  
- Project manager
+
System Analysis
  
- Primary assessor
+
[[File:ISECF definition - System Analysis.jpg]]
  
- Secondary assessor
+
And from the why it matters section
  
- Requirement engineer
+
[[File:ISECF definition - why it matters.jpg]]
  
- Systems modeller
 
  
- Tester
 
  
- Reviewer
+
Next we need to look at the competency indicators, effectively what is a person required to demonstrate in order to attain a the levels.
 +
Firstly Awareness.
  
- Author
+
[[File:Competence Indicators-Awareness.jpg]]
  
- Process modeller
+
The remaining levels will follow along with the linked indicators (those where they build on an earlier indicator rather than introducing something new)
  
- Builder
+
Initial questions:
 +
- To where does Systems analysis provide the data/information?
 +
- Systems analysis appears to be almost an afterthought in this competence
 +
- Systems analysis is not necessarily the only process to which modelling could be applied.
 +
- How does this definition of Systems Analysis match up against he definition given in the SE handbook?
 +
- the requirements from the "why it matters" section are focused on the modelling deliverables, again suggesting that system analysis is an afterthought.
  
- SoS engineer
+
==Modelling Roles==
 
+
- MBSE champion
+
 
+
- MBSE mentor
+
 
+
- MBSE trainer
+
 
+
Each of these roles has a competency profile allocated against it both in terms of the INCOSE competency framework v3 and also against an MBSE specific competency developed by Holt/Perry. These need to be reviewed against the updated INCOSE competency framework.
+
 
+
 
+
An alternative set of modelling roles, used by A Pemberton:
+
 
+
- Lead modeller
+
 
+
- Modeller
+
 
+
- Model reviewer
+
 
+
- Subject matter expert
+
 
+
- Model user
+
 
+
- Modelling champion
+
 
+
- Modelling Referent
+
 
+
This set of roles are very specific to modelling and is designed to be applied as an additional role to another project role such as those identified by Holt/Perry, as such these roles correlate with some of the roles defined in the list from Holt/Perry. It is probably of more use to assess the competency scope required by project roles that are more commonly used across industry.
+
  
 
==Documents==
 
==Documents==
Line 110: Line 89:
 
| https://connect.incose.org/Pages/Product-Details.aspx?ProductCode=ISECFv1
 
| https://connect.incose.org/Pages/Product-Details.aspx?ProductCode=ISECFv1
 
|-
 
|-
| 2018
+
| 2015
| SysML for Systems Engineering 3rd Edition
+
| INCOSE Systems Engineering Handbook v4
| Jon Holt & Simon Perry
+
| INCOSE
| https://shop.theiet.org/sysml-for-systems-eng-3e
+
| https://www.incose.org/products-and-publications/se-handbook
 
| -
 
| -
  
 
|}
 
|}

Latest revision as of 12:34, 8 March 2023

Contents

[edit] Objectives

To understand the need for guidance on application of INCOSE competencies for MBSE.

- Review the current INCOSE material on MBSE competence

- Review roles and associated competence scopes

Need to understand what the output from this working group will be: - Z Guide - Omega Guide - U Guide - Paper - White paper - Don't panic or other book

[edit] Team

The MBSE Competencies team currently comprises the following members:

Member Organisation Role
Andrew Pemberton Thales UK Lead
TBD TBD Member
TBD TBD Member

[edit] Review of INCOSE competency framework

MBSE is considered as a cross cutting technique as defined in the systems engineering handbook. We need to understand what each of the competencies in the INCOSE competency framework (reference needed) means in the context of MBSE.


Here follows a model defining the terms as used in the ISECF v1.

ISECF Modelling Sys Analysis definition.jpg

And the description field also includes some ideas of why the various parts of the competency exist:

Modelling

ISECF definition - Description - Modelling.jpg

System Analysis

ISECF definition - System Analysis.jpg

And from the why it matters section

ISECF definition - why it matters.jpg


Next we need to look at the competency indicators, effectively what is a person required to demonstrate in order to attain a the levels. Firstly Awareness.

Competence Indicators-Awareness.jpg

The remaining levels will follow along with the linked indicators (those where they build on an earlier indicator rather than introducing something new)

Initial questions: - To where does Systems analysis provide the data/information? - Systems analysis appears to be almost an afterthought in this competence - Systems analysis is not necessarily the only process to which modelling could be applied. - How does this definition of Systems Analysis match up against he definition given in the SE handbook? - the requirements from the "why it matters" section are focused on the modelling deliverables, again suggesting that system analysis is an afterthought.

[edit] Modelling Roles

[edit] Documents

Date Title Author Link
2018 INCOSE Systems Engineering Compentency Handbook INCOSE https://connect.incose.org/Pages/Product-Details.aspx?ProductCode=ISECFv1
2015 INCOSE Systems Engineering Handbook v4 INCOSE https://www.incose.org/products-and-publications/se-handbook -

Model Based Systems Engineering Wiki

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox