dc.contributor.author | Brataas, Gunnar | |
dc.contributor.author | Martini, Antonio | |
dc.contributor.author | Hanssen, Geir Kjetil | |
dc.contributor.author | Ræder, Georg | |
dc.date.accessioned | 2022-08-23T18:27:13Z | |
dc.date.available | 2022-08-23T18:27:13Z | |
dc.date.created | 2021-09-23T14:24:53Z | |
dc.date.issued | 2021 | |
dc.identifier.citation | Journal of Systems and Software. 2021, 182, 111064. | en_US |
dc.identifier.issn | 0164-1212 | |
dc.identifier.uri | https://hdl.handle.net/11250/3013130 | |
dc.description.abstract | Eliciting scalability requirements during agile software development is complicated and poorly described in previous research. This article presents a lightweight artifact for eliciting scalability requirements during agile software development: the ScrumScale model. The ScrumScale model is a simple spreadsheet. The scalability concepts underlying the ScrumScale model are clarified in this design science research, which also utilizes coordination theory. This paper describes the open banking case study, in which a legacy banking system becomes open. This challenges the scalability of this legacy system. The first step in understanding this challenge is to elicit the new scalability requirements. In the open banking case study, key stakeholders from TietoEVRY spent 55 h eliciting the scalability requirements of TietoEVRY’s open banking project. According to TietoEVRY, the ScrumScale model provided a systematic way of producing scalability requirements. For TietoEVRY, the scalability concepts behind the ScrumScale model also offered significant advantages in dialogs with other stakeholders. | en_US |
dc.language.iso | eng | en_US |
dc.publisher | Elsevier | en_US |
dc.rights | Navngivelse 4.0 Internasjonal | * |
dc.rights.uri | http://creativecommons.org/licenses/by/4.0/deed.no | * |
dc.subject | Performance requirements | en_US |
dc.subject | Software performance engineering | en_US |
dc.subject | Agile software development | en_US |
dc.subject | Non-functional requirements | en_US |
dc.subject | Open systems | en_US |
dc.subject | Design science | en_US |
dc.subject | Quality requirements | en_US |
dc.subject | Requirements engineering | en_US |
dc.subject | Workload charaterization | en_US |
dc.title | Agile elicitation of scalability requirements for open systems: A case study | en_US |
dc.type | Peer reviewed | en_US |
dc.type | Journal article | en_US |
dc.description.version | publishedVersion | en_US |
dc.rights.holder | © 2021 The Authors | en_US |
dc.source.volume | 182 | en_US |
dc.source.journal | Journal of Systems and Software | en_US |
dc.identifier.doi | 10.1016/j.jss.2021.111064 | |
dc.identifier.cristin | 1937725 | |
dc.relation.project | Norges forskningsråd: 285542 | en_US |
dc.relation.project | Norges forskningsråd: 309811 | en_US |
dc.source.articlenumber | 111064 | en_US |
cristin.ispublished | true | |
cristin.fulltext | original | |
cristin.qualitycode | 2 | |