Working paper Open Access

Checklist for a Software Management Plan

The Software Sustainability Institute


MARC21 XML Export

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nam##2200000uu#4500</leader>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">research software</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">software sustainability</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">software sustainability institute</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">software management plan</subfield>
  </datafield>
  <controlfield tag="005">20190409141328.0</controlfield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">The Software Sustainability Institute is supported by EPSRC grant EP/H043160/1 and EPSRC/BBSRC and ESRC grant EP/N006410/1.</subfield>
  </datafield>
  <controlfield tag="001">2159713</controlfield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">129097</subfield>
    <subfield code="z">md5:c88e49bc0ac64672b7efa0bfa17e2815</subfield>
    <subfield code="u">https://zenodo.org/record/2159713/files/SoftwareManagementPlanChecklist.pdf</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">13775</subfield>
    <subfield code="z">md5:373e1b6551e802659bc48e8cc858ffc6</subfield>
    <subfield code="u">https://zenodo.org/record/2159713/files/SoftwareManagementPlanTemplate.docx</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">4895</subfield>
    <subfield code="z">md5:b020c5036856780f76c5b22cc6537057</subfield>
    <subfield code="u">https://zenodo.org/record/2159713/files/SoftwareManagementPlanTemplate.md</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">11965</subfield>
    <subfield code="z">md5:1c339af02e89d5d21b4a11ae575afaba</subfield>
    <subfield code="u">https://zenodo.org/record/2159713/files/SoftwareManagementPlanTemplate.odt</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2018-12-10</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">openaire</subfield>
    <subfield code="o">oai:zenodo.org:2159713</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">The Software Sustainability Institute</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Checklist for a Software Management Plan</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u">http://creativecommons.org/licenses/by/4.0/legalcode</subfield>
    <subfield code="a">Creative Commons Attribution 4.0 International</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">&lt;p&gt;When developing research software, it is easy to focus only on goals and activities such as collaborating with other researchers, writing papers, attending conferences and applying for funding. Together, the demands of daily research practice can all conspire to prevent proper planning for the development of research software.&lt;/p&gt;

&lt;p&gt;A Software Management Plan (SMP) can help you to define a set of structures and goals to understand your research software including what you are going to develop; who the software is for (even if it is just for yourself); how you will deliver your software to its intended users; how it will help them; and how you will assess whether it has helped them, and contributed to research, in the ways that you intended. An SMP also helps you to understand how you can support those who wish to, or do, use your research software; how your software relates to other artefacts in your research ecosystem; and how you will ensure that your software remains available beyond the lifetime of your current project.&lt;/p&gt;

&lt;p&gt;This checklist will help you to write an SMP. It consists of sections that cover the key elements that an SMP should include.&lt;/p&gt;</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">url</subfield>
    <subfield code="i">isCitedBy</subfield>
    <subfield code="a">https://www.software.ac.uk/software-management-plans</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">url</subfield>
    <subfield code="i">references</subfield>
    <subfield code="a">https://www.software.ac.uk/software-management-plans</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">url</subfield>
    <subfield code="i">isCompiledBy</subfield>
    <subfield code="a">https://github.com/softwaresaved/software-management-plans/releases/tag/1.0</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">doi</subfield>
    <subfield code="i">isCompiledBy</subfield>
    <subfield code="a">10.5281/zenodo.2159748</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">doi</subfield>
    <subfield code="i">isVersionOf</subfield>
    <subfield code="a">10.5281/zenodo.1422656</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.2159713</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">workingpaper</subfield>
  </datafield>
</record>
824
637
views
downloads
All versions This version
Views 824563
Downloads 637427
Data volume 87.9 MB44.7 MB
Unique views 637468
Unique downloads 445305

Share

Cite as