WG mtg 2015 10 20 Bham
1.1 Mike Brownsword - Atkins
1.2 Jan Rapacz - 3ds
2.1 JJ notes to meeting
2.2 AS propose presentation to ASEC for MBSE WG
3.1 Julian Johnson - Holistem
3.2 Alex Stevenson - Objektum
3.3 Ian Clark - MBDA
3.4 Robin Nickless - AWE
3.5 Ali Parandeh - Atkins
3.6 Goncalo Esteves - JLR (from 14:00hrs)
4 Meeting notes
4.1 Discussion of what discussed at previous meetings
The group referred to notes of previous meetings to remind themselves of the previous discussion, especially the concept of having 'the guide' potentially enabling an individual to move up-right in a competency map (MBSE competency vs SE competency.
4.2 What captured in notes from previous meetings
4.3 Challenges of selling MBSE, esp to Programme Managers
The topic of selling MBSE approaches cf doc-based approaches was raised multiple times.
4.4 JJ Two key stakeholders: Sys Engineers, Functional Managers
This arose from Use Case approach.
4.5 Seeing the Guide as a one or two page entrance into a larger body of information
4.6 Current Z9 focussed on 'what is...?' /
GE noted that the Z9 not going down well with seniors (primarily because of the diag and SysML terminology).
4.7 Potential structure: Why / when / where / who / how
The primary outcome from the meeting was to look at a 6-questions template as a way of connecting to the key questions the two major stakeholders may have, when considering / or being tasked to adopt MBSE.
Two tables were anticipated, for:
Sys Eng Manager
RN noted that a Learn Do Evangelise approach may represent nuances to these roles.
4.8 ASEC WG mtg:
ASEC MBSE WG mtg is an opportunity to sound out attendees to our thoughts on Omega Guide + additional info.
4.9 Flip chart table of 6 W's, for Engineering Manager
Separate word document.
4.10 RN Tangible vs non-tangible benefits, and when...
4.11 Discussion about 2 or 3 nuances of Sys Eng Manager
The headings in the table (word doc) illustrate the different roles that Systems Eng Managers may play, in supporting adoption of MBSE within an organisation:
Either for whole organisation or department;
For a single project;
Or for an Engineering Manager actually supporting role-out, as a Practitioner.
There was some discussion as to whether all three roles were actually discernable, or whether only the first two were identifiable.
4.12 RN Just done systems eng capability assessment
4.13 RN Potential n x n matrix as index into collatoral of more info behind guide
4.14 RN RLI Review Learn Improve
4.15 Flip chart table for Systems Engineer
Separate word document.
4.16 JJ presented initial fragment of MBSE vs ISO 15288 outcomes
As an AOB item on the agenda, JJ presented the outcome of an initial investigate into how the ISO15288 SE activities are typically discharged when either a document-based SE or a MBSE approach is adopted. He showed a spreadsheet, folded from the top level 4 Process Areas of ISO 15288, to then be opened to the individual activities, and then to individual outcomes for each activity.
For each outcome, he had produced a one or few sentence summary to how that outcome was represented in either conventional (doc, spreadsheet) materials, or if in a model-based artefact.
He had not yet looked at the activity explanations for a few activities, again in the two SE styles.
This work potentially showed what level of detail may exist at some point below the Guide.
4.17 Primary meeting outcomes
The framework represented by the two 6-Ws tables it was felt formed a significant output from this meeting for two reasons:
- it gave a top level framework that it was felt would be useful to anticipated audiences of stakeholders contemplating MBSE adoption and
- it potentially would act as an architecture [for the guide], (especially when the nuances of stakeholders was included) against which the whole MBSE WG could be prompted to contribute.
4.18 Meeting close