<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:community="http://www.bibsonomy.org/ontologies/2008/05/community#" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:admin="http://webns.net/mvcb/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:cc="http://web.resource.org/cc/" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns:swrc="http://swrc.ontoware.org/ontology#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xml:base="https://puma.ub.uni-stuttgart.de/group/researchcode/softwareEngineering"><owl:Ontology rdf:about=""><rdfs:comment>PUMA publications for /group/researchcode/softwareEngineering</rdfs:comment><owl:imports rdf:resource="http://swrc.ontoware.org/ontology/portal"/></owl:Ontology><rdf:Description rdf:about="https://puma.ub.uni-stuttgart.de/bibtex/2998132ad5963499288571f56f9cdfa20/diglezakis"><owl:sameAs rdf:resource="/uri/bibtex/2998132ad5963499288571f56f9cdfa20/diglezakis"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Article"/><owl:sameAs rdf:resource="http://www.worldscientific.com/doi/abs/10.1142/S0218194013500137"/><swrc:date>Tue Sep 12 16:10:46 CEST 2017</swrc:date><swrc:journal>International Journal of Software Engineering and Knowledge Engineering</swrc:journal><swrc:number>04</swrc:number><swrc:pages>463-506</swrc:pages><swrc:title>DEVELOPMENT OF SCIENTIFIC SOFTWARE: A SYSTEMATIC MAPPING, A BIBLIOMETRICS STUDY, AND A PAPER REPOSITORY</swrc:title><swrc:volume>23</swrc:volume><swrc:year>2013</swrc:year><swrc:keywords>softwareEngineering literatureReview software scientific research </swrc:keywords><swrc:abstract> &lt;p class=&#034;first last&#034;&gt;Scientific and engineering research is heavily dependent on effective development and use of software artifacts. Many of these artifacts are produced by the scientists themselves, rather than by trained software engineers. To address the challenges in this area, a research community often referred to as &#034;Development of Scientific Software&#034; has emerged in the last few decades. As this research area has matured, there has been a sharp increase in the number of papers and results made available, and it has thus become important to summarize and provide an overview about those studies. Through a systematic mapping and bibliometrics study, we have reviewed 130 papers in this area. We present the results of our study in this paper. Also we have made the mapping data available on an online repository which is planned to be updated on a regular basis. The results of our study seem to suggest that many software engineering techniques and activities are being used in the development of scientific software. However, there is still a need for further exploration of the usefulness of specific software engineering techniques (e.g., regarding software maintenance, evolution, refactoring, re(v)-engineering, process and project management) in the scientific context. It is hoped that this article will help (new) researchers get an overview of the research space and help them to understand the trends in the area.&lt;/p&gt; &lt;/div&gt;</swrc:abstract><swrc:hasExtraField><swrc:Field swrc:value="10.1142/S0218194013500137" swrc:key="doi"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="http://www.worldscientific.com/doi/pdf/10.1142/S0218194013500137" swrc:key="eprint"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="ROSHANAK FARHOODI"/></rdf:_1><rdf:_2><swrc:Person swrc:name="VAHID GAROUSI"/></rdf:_2><rdf:_3><swrc:Person swrc:name="DIETMAR PFAHL"/></rdf:_3><rdf:_4><swrc:Person swrc:name="JONATHAN SILLITO"/></rdf:_4></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="https://puma.ub.uni-stuttgart.de/bibtex/28d246e8148775622a62a7deee6fe2b54/diglezakis"><owl:sameAs rdf:resource="/uri/bibtex/28d246e8148775622a62a7deee6fe2b54/diglezakis"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Article"/><owl:sameAs rdf:resource="http://www.sciencedirect.com/science/article/pii/S0950584915001342"/><swrc:date>Tue Sep 12 16:07:54 CEST 2017</swrc:date><swrc:journal>Information and Software Technology </swrc:journal><swrc:pages>207 - 219</swrc:pages><swrc:title>Claims about the use of software engineering practices in science: A systematic literature review </swrc:title><swrc:volume>67</swrc:volume><swrc:year>2015</swrc:year><swrc:keywords>science softwareEngineering literatureReview Computational </swrc:keywords><swrc:abstract>Abstract Context: Scientists have become increasingly reliant on software in order to perform research that is too time-intensive, expensive, or dangerous to perform physically. Because the results produced by the software drive important decisions, the software must be correct and developed efficiently. Various software engineering practices have been shown to increase correctness and efficiency in the development of traditional software. It is unclear whether these observations will hold in a scientific context. Objective: This paper evaluates claims from software engineers and scientific software developers about 12 different software engineering practices and their use in developing scientific software. Method: We performed a systematic literature review examining claims about how scientists develop software. Of the 189 papers originally identified, 43 are included in the literature review. These 43 papers contain 33 different claims about 12 software engineering practices. Results: The majority of the claims indicated that software engineering practices are useful for scientific software development. Every claim was supported by evidence (i.e. personal experience, interview/survey, or case study) with slightly over half supported by multiple forms of evidence. For those claims supported by only one type of evidence, interviews/surveys were the most common. The claims that received the most support were: “The effectiveness of the testing practices currently used by scientific software developers is limited” and “Version control software is necessary for research groups with more than one developer.” Additionally, many scientific software developers have unconsciously adopted an agile-like development methodology. Conclusion: Use of software engineering practices could increase the correctness of scientific software and the efficiency of its development. While there is still potential for increased use of these practices, scientific software developers have begun to embrace software engineering practices to improve their software. Additionally, software engineering practices still need to be tailored to better fit the needs of scientific software development. </swrc:abstract><swrc:hasExtraField><swrc:Field swrc:value="0950-5849" swrc:key="issn"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="https://doi.org/10.1016/j.infsof.2015.07.011" swrc:key="doi"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Dustin Heaton"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Jeffrey C. Carver"/></rdf:_2></rdf:Seq></swrc:author></rdf:Description></rdf:RDF>