| dc.contributor.author | Lucatello, Chiara | |
| dc.contributor.author | Murgescu, Monica | |
| dc.date.accessioned | 2020-07-06T09:42:42Z | |
| dc.date.available | 2020-07-06T09:42:42Z | |
| dc.date.issued | 2020-07-06 | |
| dc.identifier.uri | http://hdl.handle.net/2077/65508 | |
| dc.description | Although different ecosystem modelling techniques exist, it is difficult to assess how
used these are in practice among software companies. In this design science study,
software ecosystem practices of a software company in the automotive domain were
analysed; according to the findings, there are different perceptions of an ecosystem
among management and developers, and there are no formalised modelling techniques
being used in the company. The study was conducted in three iterations;
in the following two iterations, two modelling techniques were analysed, identifying
three different points of improvement for one of them. The technique for which
the changes were proposed was the technique favoured by the participants of the
study. The findings indicated that, while participants did not have a consistent view
of which changes would provide more benefit to the modelling technique, many of
them saw possible use cases for ecosystem modelling using the presented modelling
technique. These use cases were consistent with the perceptions that the individuals
had about software ecosystems and showed that they believed modelling techniques
to be potentially useful for the company, even if they were not currently using them. | sv |
| dc.description.abstract | Although different ecosystem modelling techniques exist, it is difficult to assess how
used these are in practice among software companies. In this design science study,
software ecosystem practices of a software company in the automotive domain were
analysed; according to the findings, there are different perceptions of an ecosystem
among management and developers, and there are no formalised modelling techniques
being used in the company. The study was conducted in three iterations;
in the following two iterations, two modelling techniques were analysed, identifying
three different points of improvement for one of them. The technique for which
the changes were proposed was the technique favoured by the participants of the
study. The findings indicated that, while participants did not have a consistent view
of which changes would provide more benefit to the modelling technique, many of
them saw possible use cases for ecosystem modelling using the presented modelling
technique. These use cases were consistent with the perceptions that the individuals
had about software ecosystems and showed that they believed modelling techniques
to be potentially useful for the company, even if they were not currently using them. | sv |
| dc.language.iso | eng | sv |
| dc.subject | software ecosystem | sv |
| dc.subject | perceptions | sv |
| dc.subject | collaboration | sv |
| dc.subject | modelling techniques | sv |
| dc.subject | software supply network diagram | sv |
| dc.subject | unified modelling language | sv |
| dc.subject | automotive industry disruptions | sv |
| dc.title | Investigating and Evaluating Software Ecosystem Modelling in Practice in a Tier-2 Vehicle Telematics Company | sv |
| dc.title.alternative | Investigating and Evaluating Software Ecosystem Modelling in Practice in a Tier-2 Vehicle Telematics Company | sv |
| dc.type | text | |
| dc.setspec.uppsok | Technology | |
| dc.type.uppsok | H2 | |
| dc.contributor.department | Göteborgs universitet/Institutionen för data- och informationsteknik | swe |
| dc.contributor.department | University of Gothenburg/Department of Computer Science and Engineering | eng |
| dc.type.degree | Student essay | |
