Assets in Software Engineering: What are they after all?

During the development and maintenance of software-intensive products or services, we depend on various artefacts. Some of those artefacts, we deem central to the feasibility of a project and the product’s final quality. Typically, these central artefacts are referred to as assets. However, despite...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Veröffentlicht in:The Journal of systems and software Jg. 193; S. 111485
Hauptverfasser: Zabardast, Ehsan, Frattini, Julian, Gonzalez-Huerta, Javier, Mendez, Daniel, Gorschek, Tony, Wnuk, Krzysztof
Format: Journal Article
Sprache:Englisch
Veröffentlicht: Elsevier Inc 01.11.2022
Schlagworte:
ISSN:0164-1212, 1873-1228, 1873-1228
Online-Zugang:Volltext
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
Abstract During the development and maintenance of software-intensive products or services, we depend on various artefacts. Some of those artefacts, we deem central to the feasibility of a project and the product’s final quality. Typically, these central artefacts are referred to as assets. However, despite their central role in the software development process, little thought is yet invested into what eventually characterises as an asset, often resulting in many terms and underlying concepts being mixed and used inconsistently. A precise terminology of assets and related concepts, such as asset degradation, are crucial for setting up a new generation of cost-effective software engineering practices. In this position paper, we critically reflect upon the notion of assets in software engineering. As a starting point, we define the terminology and concepts of assets and extend the reasoning behind them. We explore assets’ characteristics and discuss what asset degradation is as well as its various types and the implications that asset degradation might bring for the planning, realisation, and evolution of software-intensive products and services over time. We aspire to contribute to a more standardised definition of assets in software engineering and foster research endeavours and their practical dissemination in a common, more unified direction. •We critically reflect upon the notion of assets in software engineering.•Assets are artefacts with value for the organisation and are used more than once.•Assets are subject to degradation during all stages of the product life cycle.•When an asset is degraded, it is likely to influence the value of other assets.•Asset management is the administration of assets during the product life cycle.
AbstractList During the development and maintenance of software-intensive products or services, we depend on various artefacts. Some of those artefacts, we deem central to the feasibility of a project and the product's final quality. Typically, these central artefacts are referred to as assets. However, despite their central role in the software development process, little thought is yet invested into what eventually characterises as an asset, often resulting in many terms and underlying concepts being mixed and used inconsistently. A precise terminology of assets and related concepts, such as asset degradation, are crucial for setting up a new generation of cost-effective software engineering practices. In this position paper, we critically reflect upon the notion of assets in software engineering. As a starting point, we define the terminology and concepts of assets and extend the reasoning behind them. We explore assets’ characteristics and discuss what asset degradation is as well as its various types and the implications that asset degradation might bring for the planning, realisation, and evolution of software-intensive products and services over time. We aspire to contribute to a more standardised definition of assets in software engineering and foster research endeavours and their practical dissemination in a common, more unified direction. © 2022 The Authors
During the development and maintenance of software-intensive products or services, we depend on various artefacts. Some of those artefacts, we deem central to the feasibility of a project and the product’s final quality. Typically, these central artefacts are referred to as assets. However, despite their central role in the software development process, little thought is yet invested into what eventually characterises as an asset, often resulting in many terms and underlying concepts being mixed and used inconsistently. A precise terminology of assets and related concepts, such as asset degradation, are crucial for setting up a new generation of cost-effective software engineering practices. In this position paper, we critically reflect upon the notion of assets in software engineering. As a starting point, we define the terminology and concepts of assets and extend the reasoning behind them. We explore assets’ characteristics and discuss what asset degradation is as well as its various types and the implications that asset degradation might bring for the planning, realisation, and evolution of software-intensive products and services over time. We aspire to contribute to a more standardised definition of assets in software engineering and foster research endeavours and their practical dissemination in a common, more unified direction. •We critically reflect upon the notion of assets in software engineering.•Assets are artefacts with value for the organisation and are used more than once.•Assets are subject to degradation during all stages of the product life cycle.•When an asset is degraded, it is likely to influence the value of other assets.•Asset management is the administration of assets during the product life cycle.
ArticleNumber 111485
Author Zabardast, Ehsan
Mendez, Daniel
Frattini, Julian
Wnuk, Krzysztof
Gonzalez-Huerta, Javier
Gorschek, Tony
Author_xml – sequence: 1
  givenname: Ehsan
  orcidid: 0000-0002-1729-5154
  surname: Zabardast
  fullname: Zabardast, Ehsan
  email: ehsan.zabardast@bth.se
  organization: Software Engineering Research Lab SERL, Blekinge Institute of Technology, Campus Karlskrona, Valhallavägen 1, Karlskrona, Sweden
– sequence: 2
  givenname: Julian
  orcidid: 0000-0003-3995-6125
  surname: Frattini
  fullname: Frattini, Julian
  email: julian.frattini@bth.se
  organization: Software Engineering Research Lab SERL, Blekinge Institute of Technology, Campus Karlskrona, Valhallavägen 1, Karlskrona, Sweden
– sequence: 3
  givenname: Javier
  orcidid: 0000-0003-1350-7030
  surname: Gonzalez-Huerta
  fullname: Gonzalez-Huerta, Javier
  email: javier.gonzalez.huerta@bth.se
  organization: Software Engineering Research Lab SERL, Blekinge Institute of Technology, Campus Karlskrona, Valhallavägen 1, Karlskrona, Sweden
– sequence: 4
  givenname: Daniel
  orcidid: 0000-0003-0619-6027
  surname: Mendez
  fullname: Mendez, Daniel
  email: daniel.mendez@bth.se
  organization: Software Engineering Research Lab SERL, Blekinge Institute of Technology, Campus Karlskrona, Valhallavägen 1, Karlskrona, Sweden
– sequence: 5
  givenname: Tony
  surname: Gorschek
  fullname: Gorschek, Tony
  email: tony.gorschek@bth.se
  organization: Software Engineering Research Lab SERL, Blekinge Institute of Technology, Campus Karlskrona, Valhallavägen 1, Karlskrona, Sweden
– sequence: 6
  givenname: Krzysztof
  surname: Wnuk
  fullname: Wnuk, Krzysztof
  email: krzysztof.wnuk@bth.se
  organization: Software Engineering Research Lab SERL, Blekinge Institute of Technology, Campus Karlskrona, Valhallavägen 1, Karlskrona, Sweden
BackLink https://urn.kb.se/resolve?urn=urn:nbn:se:bth-23601$$DView record from Swedish Publication Index (Blekinge Tekniska Högskola)
BookMark eNp9kMtKAzEUQINUsK1-gLv5AKfm0UlSXUip9QEFF76WITNz02YYMyWJlv69KaMbF65yCefcC2eEBq5zgNA5wROCCb9sJk0IE4opnRBCprI4QkMiBcsJpXKAhomZppnQEzQKocEYiwQPkZyHADFk1mXPnYk77SFburV1AN669VX2vtExO_zGDewzbSL4TLftzSk6NroNcPbzjtHr3fJl8ZCvnu4fF_NVXjEhYk45lwUXhJG6mmnDhDGSCF6AYJQJzGeghQSYlUxIVieylpyVosA1sJoYw8boot8bdrD9LNXW2w_t96rTVt3at7nq_FqVcaMo45gkXPR45bsQPBhV2aij7Vz02raKYHXopRqVeqlDL9X3Sib5Y_6e-s-57h1IBb4seBUqC66C2nqooqo7-4_9DWBwg5s
CitedBy_id crossref_primary_10_15407_pp2024_04_114
crossref_primary_10_1109_MS_2023_3346646
crossref_primary_10_1016_j_infsof_2023_107201
crossref_primary_10_1016_j_jss_2023_111701
Cites_doi 10.1007/s10270-019-00714-3
10.1016/j.infsof.2018.05.010
10.1016/0164-1212(79)90022-0
10.1016/j.procs.2016.08.278
10.1016/j.ijepes.2006.03.007
ContentType Journal Article
Copyright 2022 The Authors
Copyright_xml – notice: 2022 The Authors
DBID 6I.
AAFTH
AAYXX
CITATION
ADTPV
AOWAS
D8T
DF3
ZZAVC
DOI 10.1016/j.jss.2022.111485
DatabaseName ScienceDirect Open Access Titles
Elsevier:ScienceDirect:Open Access
CrossRef
SwePub
SwePub Articles
SWEPUB Freely available online
SWEPUB Blekinge Tekniska Högskola
SwePub Articles full text
DatabaseTitle CrossRef
DatabaseTitleList

DeliveryMethod fulltext_linktorsrc
Discipline Computer Science
EISSN 1873-1228
ExternalDocumentID oai_DiVA_org_bth_23601
10_1016_j_jss_2022_111485
S0164121222001662
GrantInformation_xml – fundername: SHADE KK-Hög project
  grantid: 2017/0176
– fundername: Research Profile project SERT
  grantid: 2018/010
GroupedDBID --K
--M
-~X
.DC
.~1
0R~
1B1
1~.
1~5
29L
4.4
457
4G.
5GY
5VS
6I.
7-5
71M
8P~
9JN
9M8
AABNK
AACTN
AAEDT
AAEDW
AAFTH
AAIKJ
AAKOC
AALRI
AAOAW
AAQFI
AAQXK
AAXUO
AAYFN
AAYOK
ABBOA
ABEFU
ABFNM
ABFRF
ABFSI
ABJNI
ABMAC
ABTAH
ABXDB
ABYKQ
ACDAQ
ACGFO
ACGFS
ACGOD
ACNNM
ACRLP
ACZNC
ADBBV
ADEZE
ADHUB
ADJOM
ADMUD
AEBSH
AEFWE
AEKER
AENEX
AFKWA
AFTJW
AGHFR
AGUBO
AGYEJ
AHHHB
AHZHX
AI.
AIALX
AIEXJ
AIKHN
AITUG
AJBFU
AJOXV
ALMA_UNASSIGNED_HOLDINGS
AMFUW
AMRAJ
AOUOD
ASPBG
AVWKF
AXJTR
AZFZN
BKOJK
BKOMP
BLXMC
CS3
DU5
E.L
EBS
EFJIC
EFLBG
EJD
EO8
EO9
EP2
EP3
FDB
FEDTE
FGOYB
FIRID
FNPLU
FYGXN
G-Q
G8K
GBLVA
GBOLZ
HLZ
HVGLF
HZ~
IHE
J1W
KOM
LG9
M41
MO0
MS~
N9A
O-L
O9-
OAUVE
OZT
P-8
P-9
P2P
PC.
PQQKQ
Q38
R2-
RIG
RNS
ROL
RPZ
RXW
SBC
SDF
SDG
SDP
SES
SEW
SPC
SPCBC
SSV
SSZ
T5K
TAE
TN5
TWZ
UHS
UNMZH
VH1
WUQ
XPP
ZMT
ZY4
~G-
9DU
AATTM
AAXKI
AAYWO
AAYXX
ABDPE
ABWVN
ACLOT
ACRPL
ACVFH
ADCNI
ADNMO
AEIPS
AEUPX
AFJKZ
AFPUW
AGQPQ
AIGII
AIIUN
AKBMS
AKRWK
AKYEP
ANKPU
APXCP
CITATION
EFKBS
~HD
ADTPV
AOWAS
D8T
DF3
ZZAVC
ID FETCH-LOGICAL-c377t-2668567131dc9af37ff81765e73237069ea78ee9b3783d567d863b750de3d1ff3
ISICitedReferencesCount 5
ISICitedReferencesURI http://www.webofscience.com/api/gateway?GWVersion=2&SrcApp=Summon&SrcAuth=ProQuest&DestLinkType=CitingArticles&DestApp=WOS_CPL&KeyUT=000967989300022&url=https%3A%2F%2Fcvtisr.summon.serialssolutions.com%2F%23%21%2Fsearch%3Fho%3Df%26include.ft.matches%3Dt%26l%3Dnull%26q%3D
ISSN 0164-1212
1873-1228
IngestDate Tue Nov 04 16:15:00 EST 2025
Sat Nov 29 07:26:42 EST 2025
Tue Nov 18 21:33:45 EST 2025
Fri Feb 23 02:38:13 EST 2024
IsDoiOpenAccess true
IsOpenAccess true
IsPeerReviewed true
IsScholarly true
Keywords Asset management
Assets
Software artefacts
Technical debt
Asset degradation
Language English
License This is an open access article under the CC BY license.
LinkModel OpenURL
MergedId FETCHMERGED-LOGICAL-c377t-2668567131dc9af37ff81765e73237069ea78ee9b3783d567d863b750de3d1ff3
ORCID 0000-0003-3995-6125
0000-0003-1350-7030
0000-0002-1729-5154
0000-0003-0619-6027
OpenAccessLink https://urn.kb.se/resolve?urn=urn:nbn:se:bth-23601
ParticipantIDs swepub_primary_oai_DiVA_org_bth_23601
crossref_citationtrail_10_1016_j_jss_2022_111485
crossref_primary_10_1016_j_jss_2022_111485
elsevier_sciencedirect_doi_10_1016_j_jss_2022_111485
PublicationCentury 2000
PublicationDate 2022-11-01
PublicationDateYYYYMMDD 2022-11-01
PublicationDate_xml – month: 11
  year: 2022
  text: 2022-11-01
  day: 01
PublicationDecade 2020
PublicationTitle The Journal of systems and software
PublicationYear 2022
Publisher Elsevier Inc
Publisher_xml – name: Elsevier Inc
References Klotins, Gorschek (b8) 2022
Khurum, Gorschek, Wilson (b7) 2013; 25
Schneider, Gaul, Neumann, Hogräfer, Wellßow, Schwan, Schnettler (b16) 2006; 28
Amadi-Echendu, J.E., Brown, K., Willett, R., Mathew, J., Definitions, Concepts and Scope of Engineering Asset Management. Vol. 1. Springer London, London.
Alégroth, Gonzalez-Huerta (b1) 2017
Lehman (b9) 1979; 1
Mens, Demeyer (b13) 2008
Cunningham (b5) 1993
Lehman (b11) 1996
Lehman (b10) 1980; vol. 68
ISO/IEC/IEEE (b6) 2014
Méndez Fernández, Böhm, Vogelsang, Mund, Broy, Kuhrmann, Weyer (b12) 2019; 18
Reussner, Goedicke, Hasselbring, Vogel-Heuser, Keim, Märtin (b14) 2019
Rios, de Mendonça Neto, Spínola (b15) 2018; 102
Avgeriou, Kruchten, Ozkaya, Seaman, Seaman (b3) 2016
Sundelin, Gonzalez-Huerta, Wnuk (b17) 2020
Casale, Chesta, Deussen, Di Nitto, Gouvas, Koussouris, Stankovski, Symeonidis, Vlassiou, Zafeiropoulos (b4) 2016; 97
Reussner (10.1016/j.jss.2022.111485_b14) 2019
Cunningham (10.1016/j.jss.2022.111485_b5) 1993
Rios (10.1016/j.jss.2022.111485_b15) 2018; 102
10.1016/j.jss.2022.111485_b2
Klotins (10.1016/j.jss.2022.111485_b8) 2022
Mens (10.1016/j.jss.2022.111485_b13) 2008
Méndez Fernández (10.1016/j.jss.2022.111485_b12) 2019; 18
Casale (10.1016/j.jss.2022.111485_b4) 2016; 97
ISO/IEC/IEEE (10.1016/j.jss.2022.111485_b6) 2014
Lehman (10.1016/j.jss.2022.111485_b9) 1979; 1
Schneider (10.1016/j.jss.2022.111485_b16) 2006; 28
Avgeriou (10.1016/j.jss.2022.111485_b3) 2016
Khurum (10.1016/j.jss.2022.111485_b7) 2013; 25
Sundelin (10.1016/j.jss.2022.111485_b17) 2020
Lehman (10.1016/j.jss.2022.111485_b10) 1980; vol. 68
Alégroth (10.1016/j.jss.2022.111485_b1) 2017
Lehman (10.1016/j.jss.2022.111485_b11) 1996
References_xml – volume: 25
  start-page: 711
  year: 2013
  end-page: 741
  ident: b7
  article-title: The software value map—an exhaustive collection of value aspects for the development of software intensive products
  publication-title: J. Software: Evol. Process
– year: 2019
  ident: b14
  article-title: Managed Software Evolution
– volume: 97
  start-page: 34
  year: 2016
  end-page: 42
  ident: b4
  article-title: Current and future challenges of software engineering for services and applications
  publication-title: Procedia Comput. Sci.
– volume: 18
  start-page: 2777
  year: 2019
  end-page: 2786
  ident: b12
  article-title: Artefacts in software engineering: A fundamental positioning
  publication-title: Softw. Syst. Model.
– volume: vol. 68
  start-page: 1060
  year: 1980
  end-page: 1076
  ident: b10
  article-title: Programs, life cycles, and laws of software evolution
  publication-title: Proceedings of the IEEE
– volume: 28
  start-page: 643
  year: 2006
  end-page: 654
  ident: b16
  article-title: Asset management techniques
  publication-title: Int. J. Electr. Power Energy Syst.
– start-page: 108
  year: 1996
  end-page: 124
  ident: b11
  article-title: Laws of software evolution revisited
  publication-title: European Workshop on Software Process Technology
– start-page: 110
  year: 2016
  end-page: 138
  ident: b3
  article-title: Managing technical debt in software engineering
  publication-title: Dagstuhl Reports
– start-page: 3
  year: 2022
  end-page: 12
  ident: b8
  article-title: Continuous software engineering in the wild
  publication-title: Software Quality: The Next Big Thing in Software Engineering and Quality
– year: 2008
  ident: b13
  article-title: Software Evolution
– volume: 102
  start-page: 117
  year: 2018
  end-page: 145
  ident: b15
  article-title: A tertiary study on technical debt: Types, management strategies, research trends, and base information for practitioners
  publication-title: Inf. Software Technol.
– reference: Amadi-Echendu, J.E., Brown, K., Willett, R., Mathew, J., Definitions, Concepts and Scope of Engineering Asset Management. Vol. 1. Springer London, London.
– start-page: 67
  year: 2020
  end-page: 76
  ident: b17
  article-title: The hidden cost of backward compatibility: When deprecation turns into technical debt - An experience report
  publication-title: Proceedings - 2020 IEEE/ACM International Conference on Technical Debt
– year: 2014
  ident: b6
  article-title: Asset Management - Overview, Principles, and Terminology ISO/IEC/IEEE 55000:2014
– volume: 1
  start-page: 213
  year: 1979
  end-page: 221
  ident: b9
  article-title: On understanding laws, evolution, and conservation in the large-program life cycle
  publication-title: J. Syst. Softw.
– start-page: 404
  year: 2017
  end-page: 411
  ident: b1
  article-title: Towards a mapping of software technical debt onto testware
  publication-title: Euromicro Conference on Software Engineering and Advanced Applications
– start-page: 29
  year: 1993
  end-page: 30
  ident: b5
  article-title: The WyCash portfolio management system
  publication-title: Proc. Object-Oriented Programming Systems, Languages, and Applications, Vol. 4
– year: 2014
  ident: 10.1016/j.jss.2022.111485_b6
– start-page: 3
  year: 2022
  ident: 10.1016/j.jss.2022.111485_b8
  article-title: Continuous software engineering in the wild
– volume: vol. 68
  start-page: 1060
  year: 1980
  ident: 10.1016/j.jss.2022.111485_b10
  article-title: Programs, life cycles, and laws of software evolution
– start-page: 404
  year: 2017
  ident: 10.1016/j.jss.2022.111485_b1
  article-title: Towards a mapping of software technical debt onto testware
– volume: 25
  start-page: 711
  year: 2013
  ident: 10.1016/j.jss.2022.111485_b7
  article-title: The software value map—an exhaustive collection of value aspects for the development of software intensive products
  publication-title: J. Software: Evol. Process
– volume: 18
  start-page: 2777
  year: 2019
  ident: 10.1016/j.jss.2022.111485_b12
  article-title: Artefacts in software engineering: A fundamental positioning
  publication-title: Softw. Syst. Model.
  doi: 10.1007/s10270-019-00714-3
– volume: 102
  start-page: 117
  year: 2018
  ident: 10.1016/j.jss.2022.111485_b15
  article-title: A tertiary study on technical debt: Types, management strategies, research trends, and base information for practitioners
  publication-title: Inf. Software Technol.
  doi: 10.1016/j.infsof.2018.05.010
– start-page: 67
  year: 2020
  ident: 10.1016/j.jss.2022.111485_b17
  article-title: The hidden cost of backward compatibility: When deprecation turns into technical debt - An experience report
– start-page: 110
  year: 2016
  ident: 10.1016/j.jss.2022.111485_b3
  article-title: Managing technical debt in software engineering
– start-page: 108
  year: 1996
  ident: 10.1016/j.jss.2022.111485_b11
  article-title: Laws of software evolution revisited
– start-page: 29
  year: 1993
  ident: 10.1016/j.jss.2022.111485_b5
  article-title: The WyCash portfolio management system
– volume: 1
  start-page: 213
  year: 1979
  ident: 10.1016/j.jss.2022.111485_b9
  article-title: On understanding laws, evolution, and conservation in the large-program life cycle
  publication-title: J. Syst. Softw.
  doi: 10.1016/0164-1212(79)90022-0
– volume: 97
  start-page: 34
  year: 2016
  ident: 10.1016/j.jss.2022.111485_b4
  article-title: Current and future challenges of software engineering for services and applications
  publication-title: Procedia Comput. Sci.
  doi: 10.1016/j.procs.2016.08.278
– year: 2008
  ident: 10.1016/j.jss.2022.111485_b13
– volume: 28
  start-page: 643
  year: 2006
  ident: 10.1016/j.jss.2022.111485_b16
  article-title: Asset management techniques
  publication-title: Int. J. Electr. Power Energy Syst.
  doi: 10.1016/j.ijepes.2006.03.007
– year: 2019
  ident: 10.1016/j.jss.2022.111485_b14
– ident: 10.1016/j.jss.2022.111485_b2
SSID ssj0007202
Score 2.4049215
SecondaryResourceType review_article
Snippet During the development and maintenance of software-intensive products or services, we depend on various artefacts. Some of those artefacts, we deem central to...
SourceID swepub
crossref
elsevier
SourceType Open Access Repository
Enrichment Source
Index Database
Publisher
StartPage 111485
SubjectTerms Asset
Asset degradation
Asset management
Assets
Assets management
Cost effective
Cost effectiveness
Cost engineering
Position papers
Product and services
Software artefacts
Software design
Software development process
Software engineering practices
Technical debt
Technical debts
Terminology
Title Assets in Software Engineering: What are they after all?
URI https://dx.doi.org/10.1016/j.jss.2022.111485
https://urn.kb.se/resolve?urn=urn:nbn:se:bth-23601
Volume 193
WOSCitedRecordID wos000967989300022&url=https%3A%2F%2Fcvtisr.summon.serialssolutions.com%2F%23%21%2Fsearch%3Fho%3Df%26include.ft.matches%3Dt%26l%3Dnull%26q%3D
hasFullText 1
inHoldings 1
isFullTextHit
isPrint
journalDatabaseRights – providerCode: PRVESC
  databaseName: Elsevier SD Freedom Collection Journals 2021
  customDbUrl:
  eissn: 1873-1228
  dateEnd: 99991231
  omitProxy: false
  ssIdentifier: ssj0007202
  issn: 1873-1228
  databaseCode: AIEXJ
  dateStart: 19950101
  isFulltext: true
  titleUrlDefault: https://www.sciencedirect.com
  providerName: Elsevier
link http://cvtisr.summon.serialssolutions.com/2.0.0/link/0/eLvHCXMwtV1JS8NAFB5EPXhxF3dy0IsQaTJNZnIsWjdEBBd6GzKZibZIKm2qxV_vmy0NbujBSwjpTJb3DW9e3_I9hPYEV0a3amiSUuE3U859mjaIL7MEdruIxpEm07m_JFdXtNNJrm1b9qFuJ0CKgo7HyfO_Qg3XAGxVOvsHuKubwgU4B9DhCLDD8VfAqzBuqbNcb0DFvqrMrhrpYN0YnZSFaYPUkDobzuahnVr5lVXkX6SmQKT9WMvkOVE0yF3dGEoXW09-Oe0Xb7D9vPlnIxXxNzm5ahuuQJbOgW0K3eseCPjzGlQeCKM0KcF-ENoib6dVTePDTxraOAt6h72hIksPQ6Wzm6ZrzxfE18fd-xbrDx4YLx9ZiGNVqTcTkigBBTbTOm93Lqptl4Q6wVRRhsHLmDC3ezEXztaJfR-e_K1BUmeO1dbG7SKat6h4LQPvEpqSxTJacC04PKuRV9CuQdvrFp5D26uhvYruTtq3R2e-bXnhZ5iQ0gdziUYxCXAgsiTNMclzGpA4kgSHmDTiRKaESplwTCgWMFLQGHOw-oTEIshzvIami34h15EHxjOHoUTwTDQzkVA4jWAODyRWJGsbqOG-m2WWD161JXliLvGvx0BUTImKGVFtoINqyrMhQ_lpcNMJk1lrzlhpDJbCT9P2jeCrJ3y9DjZ_OW4LzU3W7DaaLgcjuYNms5eyOxzs2kX0DjSXdJ8
linkProvider Elsevier
openUrl ctx_ver=Z39.88-2004&ctx_enc=info%3Aofi%2Fenc%3AUTF-8&rfr_id=info%3Asid%2Fsummon.serialssolutions.com&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.atitle=Assets+in+Software+Engineering&rft.jtitle=The+Journal+of+systems+and+software&rft.au=Zabardast%2C+Ehsan&rft.au=Frattini%2C+Julian&rft.au=Gonzalez-Huerta%2C+Javier&rft.au=Mendez%2C+Daniel&rft.date=2022-11-01&rft.issn=1873-1228&rft.volume=193&rft_id=info:doi/10.1016%2Fj.jss.2022.111485&rft.externalDocID=oai_DiVA_org_bth_23601
thumbnail_l http://covers-cdn.summon.serialssolutions.com/index.aspx?isbn=/lc.gif&issn=0164-1212&client=summon
thumbnail_m http://covers-cdn.summon.serialssolutions.com/index.aspx?isbn=/mc.gif&issn=0164-1212&client=summon
thumbnail_s http://covers-cdn.summon.serialssolutions.com/index.aspx?isbn=/sc.gif&issn=0164-1212&client=summon