Difference between revisions of "SSE Meeting 26"

From Service Systems Engineering Group Wiki
Jump to: navigation, search
(Created page with "INCOSE UK Service Systems Engineering Working Group Meeting: 11 September 2017, Filton, Bristol == Attendees == Andrew Farncombe, Alan Crawford, John Davies, Iain Cardow,...")
 
Line 9: Line 9:
  
 
== Workshop for ASEC2017 ==
 
== Workshop for ASEC2017 ==
Various case studies, source documents, and findings from the group publications were compared and contrasted to see:
+
Being developed by Simon Wright. 
* which techniques, processes, representations, etc. were seen to be useful in one studies
+
==='Deriving an Ontology for Service Systems.'===
* which could be identified across different case studies
+
*To describe how a Services ontology can be derived using Systems Engineering techniques.
* which could be usefully applied to other case studies.
+
*To derive the first two layers of an ontology by using different areas of services
 +
 
 +
==Fitting Services Systems Engineering into standard handbooks.==
 +
 
 +
==Possible contents list for a Guide to Service Systems Engineering.==
 +
 
  
 
== Does the Service Systems Engineering work fit into the standard Systems Engineering guide books? ==
 
== Does the Service Systems Engineering work fit into the standard Systems Engineering guide books? ==
Line 45: Line 50:
 
== Next Meeting ==
 
== Next Meeting ==
  
Monday 11 September 2017 10-30 to 14-30, Rolls-Royce, Filton, Bristol.
+
Monday 6 December2017 10-30 to 14-30, Rolls-Royce, Filton, Bristol.

Revision as of 14:25, 12 September 2017

INCOSE UK Service Systems Engineering Working Group

Meeting: 11 September 2017, Filton, Bristol


Contents

 [hide

Attendees

Andrew Farncombe, Alan Crawford, John Davies, Iain Cardow, Simon Wright, Sarwar Ahmad, Neil Hunter

Workshop for ASEC2017

Being developed by Simon Wright.

'Deriving an Ontology for Service Systems.'

  • To describe how a Services ontology can be derived using Systems Engineering techniques.
  • To derive the first two layers of an ontology by using different areas of services

Fitting Services Systems Engineering into standard handbooks.

Possible contents list for a Guide to Service Systems Engineering.

Does the Service Systems Engineering work fit into the standard Systems Engineering guide books?

  • IS2016 paper Understanding Services Understanding Stakeholders
    • Definitions
    • Taxonomy
    • Characteristics
    • CMMI for services
    • Service Oriented Architecture
    • TOGAF
    • ITIL
  • ASEC2016 submitted paper: Comparison of Approaches to Engineering Services
    • Electric Car Rental
    • Boris Bikes
  • MODAF Service Views
  • Specification of service for Maintenance, Support and Training for military vehicles

Findings

  • the Stakeholder analysis is key and needs to be applied
  • other artefacts could be related across case studies

Way forward

  • Andrew to check SEBoK and SE Handbook to see if/where this work could best fit.
  • John to identify suitable contents list for a Services Engineering Handbook and see what information could fit where.
  • Iain to review standard stakeholder definitions and see if they need to change for Services


Next Meeting

Monday 6 December2017 10-30 to 14-30, Rolls-Royce, Filton, Bristol.

Service Systems Engineering Group Wiki

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox