Difference between revisions of "SSE Meeting 51"

From Service Systems Engineering Group Wiki
Jump to: navigation, search
(Created page with "discussion for further work and how to find them == Attendees == John Davies, Simon Wright, Andrew Farncombe, Iain Cardow, Sarvar Ahmad Mark Womersley, apologised == e-R...")
 
(Z Guide and/or Omiga Guide)
 
(25 intermediate revisions by one user not shown)
Line 6: Line 6:
 
Mark Womersley, apologised
 
Mark Womersley, apologised
  
== e-Review ==
+
==  Membership and Organisation==
The group was asked to provide a report for e-Preview. This was produced based on the last meeting using the rrport in Wiki.
+
 
+
went to this meeting and presented a slide on our wirk, again based on the report of the report on the wiki
+
 
+
== Don;t Panic Guide ==
+
Simon reported that the Guide was going out. Comments on the Guide will be collated and sent to Simon to deal with.
+
 
+
==  Membership ==
+
 
* There are currently around 60 people in thev group of which 6 attend virtual meetings  
 
* There are currently around 60 people in thev group of which 6 attend virtual meetings  
 
* We need a way of involving them and benefit from their ideas and knowledge.
 
* We need a way of involving them and benefit from their ideas and knowledge.
*The current organisation will continue
+
*The current organisation WAS agreed:
 +
 
 
** Chair John Davies
 
** Chair John Davies
** - Chair  Iain Cardow: Andrew  Farncombe
+
** Co-Chair  Iain Cardow: Andrew  Farncombe
 
** Core Tean Members: Sarwar Arhmad, Work Wormsley
 
** Core Tean Members: Sarwar Arhmad, Work Wormsley
  
==- Format/work of the group ==
+
= Ways forward =
 
+
  
= Ideas for ways forward (with Lead)) ==
+
== Don't Panic Guide ==
After discussion the following work was identified for consideration:
+
*Comments received via INCOSE UK will go to Simon
 +
*Mark will compare with standard texts such as the IINCOSE  Handbook (Verso 5 is due out in july
  
* Poll our members on what they want from the SSE group (Simon)
+
== Poll our SSE members ==
 +
On what they want from the SSE group and make them aware of the current start of the work.(Simon)
  
* Review content of Don't Panic Guide with the SEBoK and other standard texts (Mark)
+
== *SSE and SysML, MoDAF etc. ==
 +
* *Objectiv: To Understand and document the relationships between SSE/Guide with Architectural Frameworks and formal modelling Language's
 +
*Process: to include lassoing with the Incose UK Architecture Groups and MBSE Groups
 +
* Note from the OMG (Object Management Group):
 +
** The Unified Architecture Framework® (UAF®) was developed in response to SysML®, UML®, and military defense (DoDAF, MoDAF, & NAF) requirements to generate standardized and consistent architectures.
 +
** UAF is a highly efficient means of representing enterprise architectures that meet integration needs of commercial, governmental, and industrial enterprises
 +
** The recent adoption and publication of Part 1: Domain Metamodel (DMM) and Part 2: Unified Architecture Framework Modeling Language (UAFML) of the UAF as international ISO standards, is of wide interest.
  
*Deal with comments on Don't panic Guide (Simon)
+
== Z Guide and/or Omiga Guide ==
+
* General feeling is not to bother with these.  This view seems to be shared with Jon Holt 
*Understand and document the relationships between SSE/Guide with Architectural Frameworks (such as SoSaf, Togaf, and and graphical Languages (such as SysML).(Simon)
+
*With a Don;t Panic Guide costing money, it may be better to have a two-page free-bee guide for SSE based on the Don't Panic Guide.
 +
*The Core team know what its all about but others need to know before they buy a DPG.
 +
* Is there a plan for roll-out of the Don;t Panic?
 +
*This could be questioned in the Survey (see above).
 +
V
 +
=Back-log==
  
*Consider producing a Z Guide and/or Omiga Guide for SSE based on the Don't Panic Guide (Mark Simon)
+
=== What is the Backlog? ===
 +
A list of possible ideas for the SSE Goup way forward. At Meeting 50 it was suggested we
 +
*re-visit work done
 +
*Find Ideas that have been shelved
 +
*but may provide topics for future work.
  
*Produce a 'back log' of ideas and approaches identified during the operations of this group (John)
+
'''How was it created?'''  
  
== Date of next meeting ==
+
*Run through the minutes of the 50 meetings run so far
 +
*Identify the technical content
 +
'''Identify a number of groupings'''
 +
for each grouping
 +
*link to the minutes of the meeting the data came from
 +
*.and the Technical ideas covered 
 +
make this available''' to all
 +
Members via the Service Systems Engineering Working Group WIKI
 +
'''Hit this link. [[List_of_ideas]]''
 +
[[[[back log 2]]]]
  
21 June 2023 10:00 to 11:00.  Iain to arrange and sort out access.
+
= Date of nest Meeting =
 +
9tj August, 10:00 tp 11:00.  Organised  on-line by Iain.

Latest revision as of 10:59, 10 August 2023

discussion for further work and how to find them

Contents

[edit] Attendees

John Davies, Simon Wright, Andrew Farncombe, Iain Cardow, Sarvar Ahmad

Mark Womersley, apologised

[edit] Membership and Organisation

  • There are currently around 60 people in thev group of which 6 attend virtual meetings
  • We need a way of involving them and benefit from their ideas and knowledge.
  • The current organisation WAS agreed:
    • Chair John Davies
    • Co-Chair Iain Cardow: Andrew Farncombe
    • Core Tean Members: Sarwar Arhmad, Work Wormsley

[edit] Ways forward

[edit] Don't Panic Guide

  • Comments received via INCOSE UK will go to Simon
  • Mark will compare with standard texts such as the IINCOSE Handbook (Verso 5 is due out in july

[edit] Poll our SSE members

On what they want from the SSE group and make them aware of the current start of the work.(Simon)

[edit] *SSE and SysML, MoDAF etc.

  • *Objectiv: To Understand and document the relationships between SSE/Guide with Architectural Frameworks and formal modelling Language's
  • Process: to include lassoing with the Incose UK Architecture Groups and MBSE Groups
  • Note from the OMG (Object Management Group):
    • The Unified Architecture Framework® (UAF®) was developed in response to SysML®, UML®, and military defense (DoDAF, MoDAF, & NAF) requirements to generate standardized and consistent architectures.
    • UAF is a highly efficient means of representing enterprise architectures that meet integration needs of commercial, governmental, and industrial enterprises
    • The recent adoption and publication of Part 1: Domain Metamodel (DMM) and Part 2: Unified Architecture Framework Modeling Language (UAFML) of the UAF as international ISO standards, is of wide interest.

[edit] Z Guide and/or Omiga Guide

  • General feeling is not to bother with these. This view seems to be shared with Jon Holt
  • With a Don;t Panic Guide costing money, it may be better to have a two-page free-bee guide for SSE based on the Don't Panic Guide.
  • The Core team know what its all about but others need to know before they buy a DPG.
  • Is there a plan for roll-out of the Don;t Panic?
  • This could be questioned in the Survey (see above).

V

[edit] Back-log=

[edit] What is the Backlog?

A list of possible ideas for the SSE Goup way forward. At Meeting 50 it was suggested we

  • re-visit work done
  • Find Ideas that have been shelved
  • but may provide topics for future work.
How was it created? 
  • Run through the minutes of the 50 meetings run so far
  • Identify the technical content

Identify a number of groupings for each grouping

  • link to the minutes of the meeting the data came from
  • .and the Technical ideas covered

make this available to all Members via the Service Systems Engineering Working Group WIKI 'Hit this link. List_of_ideas [[back log 2]]

[edit] Date of nest Meeting

9tj August, 10:00 tp 11:00. Organised on-line by Iain.

Service Systems Engineering Group Wiki

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox