Difference between revisions of "SSE Meeting 34"

From Service Systems Engineering Group Wiki
Jump to: navigation, search
(Created page with "== Attendees == John Davies, Iain Cardow, Sarwar Ahmad, Andrew Farncombe, Neil Hunter. == Overview == *Why go for a Service solution? ** What are the benefits for the Suppli...")
 
Line 1: Line 1:
 
== Attendees ==
 
== Attendees ==
  
John Davies, Iain Cardow, Sarwar Ahmad, Andrew Farncombe, Neil Hunter.
+
John Davies, Iain Cardow, Simon Wright, Andrew Farncombe, Neil Hunter.
  
== Overview ==
+
== ASEC 2018 feedback ==
*Why go for a Service solution?
+
SW did a great job as the only core team member at the event.
** What are the benefits for the Supplier and the Customer?
+
* Paper on use of AI techniques to production of System Specification went well.
* Why you will (/or will not) win a Service Contract?
+
* Paper on Service Centric Analysis was not presented but is in the Proceedings.
*What is the big picture for buying and selling Services?
+
* Workshop on use of Stakeholder Diagram attended by six people but went well.
** Can these be used to understand the processes for developing, providing, and using services?
+
*- Based on stakeholders in the NHS and  
*What types of service contract are there?
+
*- Revealing differences to a Systems-based approach.
**What are the cost models for the different types of contract?
+
* Poster displayed but not a major attraction 
 +
 
 +
It was felt that the focus of ASEC was on MBSE applied in different situations
 +
 
 +
== Discussion on use of MBSE ==
 +
 
 +
It was felt that the work of the Service Systems Engineering Group would be more acceptable for presentation at ASEC if it used MBSE diagramming techniques (such as SysML).  This may overcome the perceived barrier in getting papers accepted at ASEC. (It is accepted that papers could be submitted to the International Conference but this is too costly)
 +
 +
The work presented in the last two papers could be reworked using MBSE. This should also test
 +
* If MBSE is suitable for this work
 +
* If MBSE can cover the concepts and techniques identified for SSE
 +
* If modifications are needed
 +
* If text-based documentation is better used
 +
* If use of MBSE reveals issues within our current view of SSE
  
 
== Why go for a Service solution? ==
 
== Why go for a Service solution? ==

Revision as of 10:19, 20 February 2019

Contents

Attendees

John Davies, Iain Cardow, Simon Wright, Andrew Farncombe, Neil Hunter.

ASEC 2018 feedback

SW did a great job as the only core team member at the event.

  • Paper on use of AI techniques to production of System Specification went well.
  • Paper on Service Centric Analysis was not presented but is in the Proceedings.
  • Workshop on use of Stakeholder Diagram attended by six people but went well.
  • - Based on stakeholders in the NHS and
  • - Revealing differences to a Systems-based approach.
  • Poster displayed but not a major attraction

It was felt that the focus of ASEC was on MBSE applied in different situations

Discussion on use of MBSE

It was felt that the work of the Service Systems Engineering Group would be more acceptable for presentation at ASEC if it used MBSE diagramming techniques (such as SysML). This may overcome the perceived barrier in getting papers accepted at ASEC. (It is accepted that papers could be submitted to the International Conference but this is too costly)

The work presented in the last two papers could be reworked using MBSE. This should also test

  • If MBSE is suitable for this work
  • If MBSE can cover the concepts and techniques identified for SSE
  • If modifications are needed
  • If text-based documentation is better used
  • If use of MBSE reveals issues within our current view of SSE

Why go for a Service solution?

What are the benefits for the Supplier and the Customer?

For the Supplier:

  • Use of existing environment
  • Use of existing service components

Service Systems Engineering Group Wiki

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox