Difference between revisions of "MBSE Omega Guide"
(→Objectives) |
|||
| Line 96: | Line 96: | ||
==Using wiki in support of Omega Guide development== | ==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]]. | Useful tips for those new to use of a wiki are available in [[wiki for Omega Guide development]]. | ||
| + | |||
| + | [http://www.incosewiki.info/Model_Based_Systems_Engineering/index.php?title=Main_Page#Current_Activities Up to parent page] | ||
Revision as of 12:28, 11 October 2016
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.
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
Evolving MBSE Adoption Guide
This page contains a link to the evolving MBSE Adoption Guide, following the communication from Julian Johnson to the team in email 15/9/2016, and the step to move evolution of the content to an evolving Guide on the Wiki, rather than in offline materials. This was in light of the experimentation of the use of the UK Wiki to elaborate an Omega Guide (aka 'how to do MBSE'), as a complement to the discussions on the MBSE.org Forum.
For the current content see the MBSE Adoption Guide
For the last content, while labelled as Omega WIP, see the Omega WIP page
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.
