<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Alice Allen</style></author><author><style face="normal" font="default" size="100%">Cecilia Aragon</style></author><author><style face="normal" font="default" size="100%">Christoph Becker</style></author><author><style face="normal" font="default" size="100%">Jeffrey Carver</style></author><author><style face="normal" font="default" size="100%">Andrei Chis</style></author><author><style face="normal" font="default" size="100%">Benoit Combemale</style></author><author><style face="normal" font="default" size="100%">Mike Croucher</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Daniel Garijo</style></author><author><style face="normal" font="default" size="100%">Ashish Gehani</style></author><author><style face="normal" font="default" size="100%">Carole Goble</style></author><author><style face="normal" font="default" size="100%">Robert Haines</style></author><author><style face="normal" font="default" size="100%">Robert Hirschfeld</style></author><author><style face="normal" font="default" size="100%">James Howison</style></author><author><style face="normal" font="default" size="100%">Kathryn Huff</style></author><author><style face="normal" font="default" size="100%">Caroline Jay</style></author><author><style face="normal" font="default" size="100%">Daniel S. Katz</style></author><author><style face="normal" font="default" size="100%">Claude Kirchner</style></author><author><style face="normal" font="default" size="100%">Katie Kuksenok</style></author><author><style face="normal" font="default" size="100%">Ralf Lämmel</style></author><author><style face="normal" font="default" size="100%">Oscar Nierstrasz</style></author><author><style face="normal" font="default" size="100%">Matt Turk</style></author><author><style face="normal" font="default" size="100%">Rob van Nieuwpoort</style></author><author><style face="normal" font="default" size="100%">Matthew Vaughn</style></author><author><style face="normal" font="default" size="100%">Jurgen J. Vinju</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Alice Allen</style></author><author><style face="normal" font="default" size="100%">et al</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Engineering Academic Software (Dagstuhl Perspectives Workshop 16252)</style></title><secondary-title><style face="normal" font="default" size="100%">Dagstuhl Manifestos</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2017</style></year><pub-dates><date><style  face="normal" font="default" size="100%">01/2017</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://drops.dagstuhl.de/opus/volltexte/2017/7146</style></url></web-urls></urls><number><style face="normal" font="default" size="100%">1</style></number><publisher><style face="normal" font="default" size="100%">Schloss Dagstuhl–Leibniz-Zentrum fuer Informatik</style></publisher><pub-location><style face="normal" font="default" size="100%">Dagstuhl, Germany</style></pub-location><volume><style face="normal" font="default" size="100%">6</style></volume><pages><style face="normal" font="default" size="100%">1–20</style></pages><abstract><style face="normal" font="default" size="100%">Software is often a critical component of scientific research. It can be a component of the academic research methods used to produce research results, or it may itself be an academic research result. Software, however, has rarely been considered to be a citable artifact in its own right. With the advent of open-source software, artifact evaluation committees of conferences, and journals that include source code and running systems as part of the published artifacts, we foresee that software will increasingly be recognized as part of the academic process. The quality and sustainability of this software must be accounted for, both a prioro and a posteriori. The Dagstuhl Perspectives Workshop on &quot;Engineering Academic Software&quot; has examined the strengths, weaknesses, risks, and opportunities of academic software engineering. A key outcome of the workshop is this Dagstuhl Manifesto, serving as a roadmap towards future professional software engineering for software-based research instruments and other software produced and used in an academic context. The manifesto is expressed in terms of a series of actionable &quot;pledges&quot; that users and developers of academic research software can take as concrete steps towards improving the environment in which that software is produced.</style></abstract></record></records></xml>