Difference between revisions of "SSE Meeting 31"
From Service Systems Engineering Group Wiki
(→Attendees) |
(→Actions) |
||
| (6 intermediate revisions by one user not shown) | |||
| Line 4: | Line 4: | ||
== Paper for ASEC 2018 == | == Paper for ASEC 2018 == | ||
| − | + | Paper submitted following review and updates. Acceptance not yet confirmed. Expect minor changes may be needed, but feel overall paper is good. | |
| − | == | + | == Way Forward == |
| − | The ASEC paper | + | The format and content of the ASEC paper was seen as a good way forward for general work. |
| − | + | Further work on 'What happened before, during and after the work in the paper will be useful in mapping out the process/lifecycle for development and use of services. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | The Systems Engineering Handbook, SeBOK and ISO/IEC 15288 were considered for their contribution, but found to cover services as a way of maintaining a system in service, rather than providing a service. | |
| + | |||
| + | Work on the Service-Centric and Product-Centric views of the system need to be extended and tested against various Case Studies to see where they are useful and where they are not. | ||
| + | |||
| + | == Methodology == | ||
| + | Work from last meeting is seen as a good basis for further work. | ||
* Four different white-board briefs of our contribution were produced and discussed. It was agreed that considering two views of the system - one service oriented and one system oriented could be used to cover the four different briefs, and provide strong message. | * Four different white-board briefs of our contribution were produced and discussed. It was agreed that considering two views of the system - one service oriented and one system oriented could be used to cover the four different briefs, and provide strong message. | ||
| Line 22: | Line 23: | ||
* Hence for example a Service-Centric Stakeholder Analysis will be similar (and use the same or similar methods) to a System-Centric Stakeholder Analysis but focus on the Service aspects and provide a richer set of outputs. | * Hence for example a Service-Centric Stakeholder Analysis will be similar (and use the same or similar methods) to a System-Centric Stakeholder Analysis but focus on the Service aspects and provide a richer set of outputs. | ||
* Comparison was made with Product Service Systems (Tukker) which deals with a range of Services from Pure Service to Pure Product. | * Comparison was made with Product Service Systems (Tukker) which deals with a range of Services from Pure Service to Pure Product. | ||
| − | * It was noted that the standard Service Oriented Architecture relating Business Model to Services provided by System Components fits into our wider | + | * It was noted that the standard Service Oriented Architecture relating Business Model to Services provided by System Components fits into our wider |
| + | |||
| + | == Dissemination == | ||
| + | * How to get our finding intooo the wider community was discussed. Favoured oprios are: | ||
| + | |||
| + | * Presentation to Bristol Local Group (and to other groups if they meet)) | ||
| + | * Paper to IS (and ASEC if the current paper is accepted) | ||
| + | * Guidance Document | ||
| + | * Z Guide | ||
| + | * Omega Guide | ||
| + | |||
== Actions == | == Actions == | ||
| − | * SW – to | + | * SW – to extend vehicle service to link into earlier and later activities related to service and also to product development. |
| − | * | + | * NT to test ideas in work related to his day job. |
| − | * | + | * JD to test ideas on other Case Studies |
| + | * AF to look at how the INCOSE UK In-service Systems engineering work was disseminated and how successful the different methods were.. | ||
| + | |||
| + | *AC is hoping to take early retirement and may not be able to contribute further. | ||
== Next Meeting == | == Next Meeting == | ||
Monday 24 September 2018, 10-30 to 14-30, Rolls Royce, Filton, Bristol. | Monday 24 September 2018, 10-30 to 14-30, Rolls Royce, Filton, Bristol. | ||
Latest revision as of 10:18, 18 July 2018
Contents |
[edit] Attendees
Andrew Farncombe, Alan Crawford, Simon Wright, John Davies, Neil Hunter.
[edit] Paper for ASEC 2018
Paper submitted following review and updates. Acceptance not yet confirmed. Expect minor changes may be needed, but feel overall paper is good.
[edit] Way Forward
The format and content of the ASEC paper was seen as a good way forward for general work.
Further work on 'What happened before, during and after the work in the paper will be useful in mapping out the process/lifecycle for development and use of services.
The Systems Engineering Handbook, SeBOK and ISO/IEC 15288 were considered for their contribution, but found to cover services as a way of maintaining a system in service, rather than providing a service.
Work on the Service-Centric and Product-Centric views of the system need to be extended and tested against various Case Studies to see where they are useful and where they are not.
[edit] Methodology
Work from last meeting is seen as a good basis for further work.
- Four different white-board briefs of our contribution were produced and discussed. It was agreed that considering two views of the system - one service oriented and one system oriented could be used to cover the four different briefs, and provide strong message.
- It was agreed that the major contribution to be expressed in this paper is for the analysis of Services in terms of Context Diagrams, Stakeholder Analysis, Behaviour Analysis, Context Analysis and Structure Analysis are different if you take Service-Centric views against what you get if you take a System-Centric views.
- The difference compared to Architecture Frameworks, that include Service views such as MoDAF, is that AFs are looking at services as system components, whereas we are looking at the enterprise or business from two views - one Service-Centric and one System-Centric.
- Hence for example a Service-Centric Stakeholder Analysis will be similar (and use the same or similar methods) to a System-Centric Stakeholder Analysis but focus on the Service aspects and provide a richer set of outputs.
- Comparison was made with Product Service Systems (Tukker) which deals with a range of Services from Pure Service to Pure Product.
- It was noted that the standard Service Oriented Architecture relating Business Model to Services provided by System Components fits into our wider
[edit] Dissemination
- How to get our finding intooo the wider community was discussed. Favoured oprios are:
- Presentation to Bristol Local Group (and to other groups if they meet))
- Paper to IS (and ASEC if the current paper is accepted)
- Guidance Document
- Z Guide
- Omega Guide
[edit] Actions
- SW – to extend vehicle service to link into earlier and later activities related to service and also to product development.
- NT to test ideas in work related to his day job.
- JD to test ideas on other Case Studies
- AF to look at how the INCOSE UK In-service Systems engineering work was disseminated and how successful the different methods were..
- AC is hoping to take early retirement and may not be able to contribute further.
[edit] Next Meeting
Monday 24 September 2018, 10-30 to 14-30, Rolls Royce, Filton, Bristol.
