7.8. Take Home Message¶

As it exists Data Management Plan, It exists now Software Management Plan. If you apply for grants more and more agencies will ask you to have a SMP.

A Software Management Plan(SMP) is a reference document that describes the (best) practices put in place when developing software. It provides a means of centralising information about a software package in a single document.

The SMP is an aid to thinking and planning. It helps you ask the right questions and identify responsibilities, actions to put in place, dependencies etc. Drafting a SMP will help you implement best practices for development and code management.

Below some links on the Pasteur policy on management and sharing software code:

7.8.1. Sources for finding data and software components¶

Before generating data or developing software, it is advisable to check whether existing datasets or software produced by other scientists could be reused. This fact sheet helps you find the resources you need: the different sources you can consult and the steps to take for effective research. https://webcampus.pasteur.fr/jcms/c_951572

7.8.2. Citing a dataset or research software¶

Before generating data or developing software, it is advisable to check whether existing datasets or software produced by other scientists could be reused. This fact sheet sets out a template for citing reused datasets or software in your publications. https://webcampus.pasteur.fr/jcms/c_951575

7.8.3. Best practices in software development¶

"Best practices" are a set of informal rules that can be applied when developing software. This sheet explains what these rules are, why it is important to put them in place and which tools are available to help you implement them. https://webcampus.pasteur.fr/jcms/c_951537

7.8.4. Guide to secure development¶

This guide aims to raise awareness among developers and train them in computer security. It consists of several subsections: principles of secure development, top 10 vulnerabilities, rules for writing secure code, library of security functions and tests https://confluence.pasteur.fr/pages/viewpage.action?pageId=103580055

7.8.5. Protect and transfer your inventions¶

This FAQ answers questions that are often asked by Institut Pasteur researchers about various aspects of protecting and applying their research results. https://webcampus.pasteur.fr/jcms/c_65758/en/

7.8.6. Distributing software¶

Distributing software means making it easy to find and accessible for users, developers and organisations. This fact sheet answers the following questions: How can I make my software available and tell people about it? How do I choose a licence for my software? https://webcampus.pasteur.fr/jcms/c_951577

7.8.7. Capitalising on software¶

The potential commercial development of your software is not based solely on the source code you have developed, but also on your knowledge and your ability to develop innovative new features. This sheet specifies the cases when you can contact the Business Development team and areas that need attention if you are considering marketing your software commercially, including the choice of licence. https://webcampus.pasteur.fr/jcms/c_951616

7.8.8. Software Management Plan¶

A Software Management Plan (SMP) is a reference document that describes the (best) practices put in place when software was developed. This sheet answers several questions: What is a SMP for? Which template is recommended? When should the SMP be drafted, and where should the different versions be submitted? https://webcampus.pasteur.fr/jcms/c_951544

7.8.9. Ensuring your code is cited, visible and sustainable¶

To enable others to find and cite the right version of your software code, it is advisable to submit this version to HAL-Pasteur. The code will automatically be transferred to Software Heritage to ensure it is permanently available and citable. This fact sheet explains why, and what to do in practical terms. https://webcampus.pasteur.fr/jcms/c_951630