Difference between revisions of "MBSE Omega Guide"
From Model Based Systems Engineering Wiki
(→Status Reports) |
|||
| Line 37: | Line 37: | ||
|Member | |Member | ||
|} | |} | ||
| + | |||
| + | =Work= | ||
==TeamStorming February 2015== | ==TeamStorming February 2015== | ||
| Line 91: | Line 93: | ||
For more content see the [[Omega WIP page]] | For more content see the [[Omega WIP page]] | ||
| + | =Help= | ||
==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]]. | ||
Revision as of 14:12, 14 March 2016
Contents |
Objectives
Team
The Omega Guide team currently comprises the following members:
| Member | Organisation | Role |
| Alex Stevenson | Objektum Solutions | Lead Author |
| Julian Joseph | 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
Work in Progress on the 6 question format
Note to reader: This introduced section is an exploration by Julian Johnson 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 more content 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.
