Journal article Open Access

Software engineering practices for scientific software development: A systematic mapping study

Elvira-Maria Arvanitou; Apostolos Ampatzoglou; Alexander Chatzigeorgiou; Jeffrey C. Carver

DataCite XML Export

<?xml version='1.0' encoding='utf-8'?>
<resource xmlns:xsi="" xmlns="" xsi:schemaLocation="">
  <identifier identifierType="URL"></identifier>
      <creatorName>Elvira-Maria Arvanitou</creatorName>
      <affiliation>Department of Applied Informatics, University of Macedonia, Thessaloniki, Greece</affiliation>
      <creatorName>Apostolos Ampatzoglou</creatorName>
      <affiliation>Department of Applied Informatics, University of Macedonia, Thessaloniki, Greece</affiliation>
      <creatorName>Alexander Chatzigeorgiou</creatorName>
      <affiliation>Department of Applied Informatics, University of Macedonia, Thessaloniki, Greece</affiliation>
      <creatorName>Jeffrey C. Carver</creatorName>
      <affiliation>Department of Computer Science, University of Alabama, United States of America</affiliation>
    <title>Software engineering practices for scientific software development: A systematic mapping study</title>
    <date dateType="Issued">2020-10-23</date>
  <resourceType resourceTypeGeneral="JournalArticle"/>
    <alternateIdentifier alternateIdentifierType="url"></alternateIdentifier>
    <relatedIdentifier relatedIdentifierType="DOI" relationType="IsIdenticalTo">10.1016/j.jss.2020.110848</relatedIdentifier>
    <rights rightsURI="">Creative Commons Attribution 4.0 International</rights>
    <rights rightsURI="info:eu-repo/semantics/openAccess">Open Access</rights>
    <description descriptionType="Abstract">&lt;p&gt;Background:&lt;/p&gt;

&lt;p&gt;The development of scientific software applications is far from trivial, due to the constant increase in the necessary complexity of these applications, their increasing size, and their need for intensive maintenance and reuse.&lt;/p&gt;


&lt;p&gt;To this end, developers of scientific software (who usually lack a formal computer science background) need to use appropriate software engineering (SE) practices. This paper describes the results of a systematic mapping study on the use of SE for scientific application development and their impact on software quality.&lt;/p&gt;


&lt;p&gt;To achieve this goal we have performed a systematic mapping study on 359 papers. We first describe a catalog of SE practices used in scientific software development. Then, we discuss the quality attributes of interest that drive the application of these practices, as well as tentative side-effects of applying the practices on qualities.&lt;/p&gt;


&lt;p&gt;The main findings indicate that scientific software developers are focusing on practices that improve implementation productivity, such as code reuse, use of third-party libraries, and the application of &amp;ldquo;&lt;em&gt;good&lt;/em&gt;&amp;rdquo; programming techniques. In addition, apart from the finding that performance is a key-driver for many of these applications, scientific software developers also find maintainability and productivity to be important.&lt;/p&gt;


&lt;p&gt;The results of the study are compared to existing literature, are interpreted under a software engineering prism, and various implications for researchers and practitioners are provided. One of the key findings of the study, which is considered as important for driving future research endeavors is the lack of evidence on the trade-offs that need to be made when applying a software practice, i.e., negative (indirect) effects on other quality attributes.&lt;/p&gt;</description>
      <funderName>European Commission</funderName>
      <funderIdentifier funderIdentifierType="Crossref Funder ID">10.13039/100010661</funderIdentifier>
      <awardNumber awardURI="info:eu-repo/grantAgreement/EC/H2020/801015/">801015</awardNumber>
      <awardTitle>Enhancing Programmability and boosting Performance Portability for Exascale Computing Systems</awardTitle>
Views 95
Downloads 49
Data volume 179.9 MB
Unique views 89
Unique downloads 48


Cite as