Vis enkel innførsel

dc.contributor.authorAyala, Claudia
dc.contributor.authorNguyen Duc, Anh
dc.contributor.authorFranch, Xavier
dc.contributor.authorHöst, Martin
dc.contributor.authorConradi, Reidar
dc.contributor.authorCruzes, Daniela Soares
dc.contributor.authorAli Babar, Muhammand
dc.date.accessioned2019-03-22T08:59:39Z
dc.date.available2019-03-22T08:59:39Z
dc.date.created2018-04-02T14:21:17Z
dc.date.issued2018
dc.identifier.citationEmpirical Software Engineering. 2018, 23 (6), 3073-3128.nb_NO
dc.identifier.issn1382-3256
dc.identifier.urihttp://hdl.handle.net/11250/2591231
dc.description.abstractDeveloping systems by integrating Open Source Software (OSS) is increasingly gaining importance in the software industry. Although the literature claims that this approach highly impacts Requirements Engineering (RE) practices, there is a lack of empirical evidence to demonstrate this statement. To explore and understand problems and challenges of current system requirement–OSS component matching and mismatches resolution practices in software development projects that integrate one or more OSS components into their software products. Semi-structured in-depth interviews with 25 respondents that have performed RE activities in software development projects that integrate OSS components in 25 different software development companies in Spain, Norway, Sweden, and Denmark. The study uncovers 15 observations regarding system requirements-OSS components matching and mismatch resolution practices used in industrial projects that integrate OSS components. The assessed projects focused mainly on pre-release stages of software applications that integrate OSS components in an opportunistic way. The results also provide details of a set of previously unexplored scenarios when solving system requirement–OSS component mismatches; and clarify some challenges and related problems. For instance, although licensing issues and the potential changes in OSS components by their corresponding communities and/or changes in system requirements have been greatly discussed in the RE literature as problems for OSS component integration, they did not appear to be relevant in our assessed projects. Instead, practitioners highlighted the problem of getting suitable OSS component documentation/informationnb_NO
dc.description.abstractSystem requirements-OSS components: matching and mismatch resolution practices – an empirical studynb_NO
dc.language.isoengnb_NO
dc.publisherSpringernb_NO
dc.titleSystem requirements-OSS components: matching and mismatch resolution practices – an empirical studynb_NO
dc.typeJournal articlenb_NO
dc.typePeer reviewednb_NO
dc.description.versionacceptedVersionnb_NO
dc.source.pagenumber3073-3128nb_NO
dc.source.volume23nb_NO
dc.source.journalEmpirical Software Engineeringnb_NO
dc.source.issue6nb_NO
dc.identifier.doi10.1007/s10664-017-9594-1
dc.identifier.cristin1576537
dc.description.localcode© Springer Science+Business Media, LLC, part of Springer Nature 2018. This is a post-peer-review, pre-copyedit version of an article published in Empirical Software Engineering. Locked until 2 March 2019 due to copyright restrictions. The final authenticated version is available online at: DOI:10.1007/s10664-017-9594-1.nb_NO
cristin.unitcode194,63,10,0
cristin.unitnameInstitutt for datateknologi og informatikk
cristin.ispublishedtrue
cristin.fulltextpostprint
cristin.qualitycode2


Tilhørende fil(er)

Thumbnail

Denne innførselen finnes i følgende samling(er)

Vis enkel innførsel