Difference between revisions of "MBSE Omega Guide"
(→Objectives) |
|||
| Line 88: | Line 88: | ||
* [http://www.incosewiki.info/Model_Based_Systems_Engineering/Files/d/dd/2016_05_19_INCOSE_UK_MBSE_WG_-_subgroups_Status_JJ_v3.pdf 19-05-16] | * [http://www.incosewiki.info/Model_Based_Systems_Engineering/Files/d/dd/2016_05_19_INCOSE_UK_MBSE_WG_-_subgroups_Status_JJ_v3.pdf 19-05-16] | ||
| − | == | + | ==Omega Team Reference material (source)== |
| − | + | The majority of the older material is actually on Alex's mbse.org site, specifically at this link, for those registered for the site: | |
| + | * [http://www.mbse.org.uk/forum/viewforum.php?f=6 MBSE.org Forum page, contact Alex Stevenson for access.]. | ||
| − | + | A summary of the material and discussions on that forum appears in the table below, for easy reference. Any items which are explicit about potential '''content''' (as distinct to characteristics it should exhibit, like useability, credibility, etc.), are highlighted in bold. ''If there are significant points missing, please edit this page and its table content to correct.'' | |
| − | + | {| class="wikitable" | |
| − | + | | Date created | |
| + | | Topic title | ||
| + | | Content summary, especially if relevant to '''content''' | ||
| + | |- | ||
| + | | 5/5/2015 | ||
| + | | Summary of Omega Men Session at WG Meeting 23/04/15 | ||
| + | | Notes of meeting. Diagram of aim or post guide awareness: pre-Guide vs post-Guide awareness, both axes competency levels. | ||
| + | '''Thoughts about guide contents: case studies, languages, applicability of MBSE to specific project'''. | ||
| + | Reference to '''how aligned with ISO 15288'''. | ||
| + | |- | ||
| + | | 16/7/2015 | ||
| + | | Moving Forward | ||
| + | | Discussions: refinement to above framework, '''competency, UKSPEC (yes, no), that MBSE is ‘not new’, stakeholders (inc system engineer, engineering manager) and use case diagram'''. | ||
| + | |- | ||
| + | | 21/10/2015 | ||
| + | | 2015 10 20 Omega Group mtg Bham | ||
| + | | Notes of meeting. Emergence of the '''Why / when / where / who / how''' structure, '''MBSE vs 15288 outcomes''', other stakeholders?, '''reference to PM and RACI framework, benefits and challenges'''. | ||
| + | |- | ||
| + | | 7/11/2015 | ||
| + | | MBSE Question | ||
| + | | Summary of the 6 questions from Engineer / Eng Manager perspectives, suggestion common questions vs any stakeholder, pointer to OmegaProgress slideset at ASEC (inc slide 9 “how you can contribute”: 3 questions to MBSE WG participants), details of one response to presentation (8 paras), paraphrase of response from JJ “good points, apparently confusion over stakeholders?”, '''incorporate MBSE during bid phase'''. | ||
| + | |} | ||
| + | Note that there are also potential content suggestions summarised in [[MBSE_Omega_Guide]], from the Teamstorming session, (see summary table) again highlighted in '''bold'''. | ||
=Help= | =Help= | ||
Revision as of 10:04, 18 March 2017
Contents |
Objectives
We note that in the minutes to the MBSE WG meeting, 02/09/2014, which was when it was posed to the Council to start work on an 'Omega Guide', it was phrased as a "How to do MBSE" Guide. link here
The Adoption Guide will not focus on the business case for adoption of MBSE, since there is a parallel sub-group activity MBSE Value. However there will be some mention of reasons for adoption of MBSE under the 'why?' questions.
Team
The Omega Guide team currently comprises the following members:
| Member | Organisation | Role |
|---|---|---|
| Julian Johnson | Holistem | Lead Author |
| Ian Clark | MBDA | Member |
| Robin Nickless | AWE | Member |
| Ali Parandeh | Atkins | Member |
| Jan Rapacz | Dassault Systèmes | Member |
| James Towers | Scarecrow Consultants | Member |
Work
TeamStorming February 2015
The working group held a "TeamStorming" session during the February 2015 meeting in order to explore the question "What should the new omega guide be about?" The outputs from that session can be found below:
- Omega Guide – TeamStorming Overview
- Omega Guide – User Empathy Map
- Omega Guide – Reviewer ensures appropriate Content scenario
- Omega Guide – Author delivering Practical Guidance Scenario
- Omega Guide – Practical Guidance to User Scenario
- Omega Guide – Publihser delivering Value Scenario
A summary of the particular relevance of these outputs to content of the Guide, for convenience, is shown below:
| Item | Content summary | Relevance to Guide content |
| TeamStorming Overview | 16 pp, mostly photos of what should guide be about (concept map), empathy analysis (hearing, seeing, feeling, seeing) for stakeholders (author, publisher, reviewer, user); storyboards. | yes, at meta-level: content must address scope and objectives, must be usable, inform audience, give practical guidance to deliver value. |
| User Empathy Map | 2 pp | Yes, in some aspects: real-world examples, links to other info/help. Otherwise it is a useful list of characteristics that content should exhibit. |
| Reviewer ensures appropriate Content scenario | 4 pp, reviewer storyboard, beaver / monkey analysis | No: more useful for how to run the reviewing process effectively. |
| Author delivering Practical Guidance Scenario | 1 table, 2 figs, author storyboard | yes, at meta-level (fine aim, understand need, understand stakeholders): no direct info about suggested content. |
| Practical Guidance to User Scenario | 1 table, user scenario, spanners and responses to combat spanners. | yes, at meta-level (not enough info, I don't believe the claims): no direct info about suggested content. |
| Publihser (sic) delivering Value Scenario | storyboard, beavers and spanners | yes, at meta-level (inconsistent with INCOSE WG, insufficient scope, lacks innovation...): no direct info about suggested content. |
Status Reports
Omega Team Reference material (source)
The majority of the older material is actually on Alex's mbse.org site, specifically at this link, for those registered for the site:
A summary of the material and discussions on that forum appears in the table below, for easy reference. Any items which are explicit about potential content (as distinct to characteristics it should exhibit, like useability, credibility, etc.), are highlighted in bold. If there are significant points missing, please edit this page and its table content to correct.
| Date created | Topic title | Content summary, especially if relevant to content |
| 5/5/2015 | Summary of Omega Men Session at WG Meeting 23/04/15 | Notes of meeting. Diagram of aim or post guide awareness: pre-Guide vs post-Guide awareness, both axes competency levels.
Thoughts about guide contents: case studies, languages, applicability of MBSE to specific project. Reference to how aligned with ISO 15288. |
| 16/7/2015 | Moving Forward | Discussions: refinement to above framework, competency, UKSPEC (yes, no), that MBSE is ‘not new’, stakeholders (inc system engineer, engineering manager) and use case diagram. |
| 21/10/2015 | 2015 10 20 Omega Group mtg Bham | Notes of meeting. Emergence of the Why / when / where / who / how structure, MBSE vs 15288 outcomes, other stakeholders?, reference to PM and RACI framework, benefits and challenges. |
| 7/11/2015 | MBSE Question | Summary of the 6 questions from Engineer / Eng Manager perspectives, suggestion common questions vs any stakeholder, pointer to OmegaProgress slideset at ASEC (inc slide 9 “how you can contribute”: 3 questions to MBSE WG participants), details of one response to presentation (8 paras), paraphrase of response from JJ “good points, apparently confusion over stakeholders?”, incorporate MBSE during bid phase. |
Note that there are also potential content suggestions summarised in MBSE_Omega_Guide, from the Teamstorming session, (see summary table) again highlighted in bold.
Help
Using wiki in support of Omega Guide development
Useful tips for those new to use of a wiki are available in wiki for Omega Guide development.
