Malmö University Publications
Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Experimentation for Business-to-Business Mission-Critical Systems: A Case Study
Chalmers University of Technology, Gothenburg, Sweden.
Ericsson Stockholm, Stockholm, Sweden.
Department of Computer Science and Engineering, Chalmers University of Technology, Gothenburg, Sweden.
Malmö University, Faculty of Technology and Society (TS), Department of Computer Science and Media Technology (DVMT).ORCID iD: 0000-0002-7700-1816
2022 (English)In: Accelerating Digital Transformation: 10 Years of Software Center / [ed] Jan Bosch; Jan Carlson; Helena Holmström Olsson; Kristian Sandahl; Miroslaw Staron, Springer, 2022, , p. 451p. 351-371Chapter in book (Refereed)
Abstract [en]

Continuous experimentation (CE) refers to a group of practices used by software companies to rapidly assess the usage, value and performance of deployed software using data collected from customers and the deployed system. Despite its increasing popularity in the development of web-facing applications, CE has not been discussed in the development process of business-to-business (B2B) mission-critical systems. We investigated in a case study the use of CE practices within several products, teams and areas inside Ericsson. By observing the CE practices of different teams, we were able to identify the key activities in four main areas and inductively derive an experimentation process, the HURRIER process, that addresses the deployment of experiments with customers in the B2B and with mission-critical systems. We illustrate this process with a case study in the development of a large mission-critical functionality in the Long Term Evolution (4G) product. In this case study, the HURRIER process is not only used to validate the value delivered by the solution but to increase the quality and the confidence from both the customers and the R&D organization in the deployed solution. Additionally, we discuss the challenges, opportunities and lessons learned from applying CE and the HURRIER process in B2B mission-critical systems. 

Place, publisher, year, edition, pages
Springer, 2022. , p. 451p. 351-371
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:mau:diva-70186DOI: 10.1007/978-3-031-10873-0_15Scopus ID: 2-s2.0-85195005926ISBN: 978-3-031-10872-3 (print)ISBN: 978-3-031-10875-4 (print)ISBN: 978-3-031-10873-0 (electronic)OAI: oai:DiVA.org:mau-70186DiVA, id: diva2:1888449
Note

Originally published in Proceedings of the International Conference on Software and System Processes, pp. 95–104, June 2020. DOI: 10.1145/3379177.3388902 

Available from: 2024-08-13 Created: 2024-08-13 Last updated: 2024-08-13Bibliographically approved

Open Access in DiVA

No full text in DiVA

Other links

Publisher's full textScopusFulltext

Authority records

Olsson, Helena Holmström

Search in DiVA

By author/editor
Olsson, Helena Holmström
By organisation
Department of Computer Science and Media Technology (DVMT)
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar

doi
isbn
urn-nbn

Altmetric score

doi
isbn
urn-nbn
Total: 20 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf