I3. Dependencies availability¶
Whether dependencies are documented and mechanisms to obtain them exist.
Software dependencies are essential for it to function properly.
I3.1. Existence of Dependencies statement¶
What is being measured?¶
- Whether the software includes details about dependencies.
Why should we measure it?¶
- A clear dependencies statement informs users about the additional software required to operate the main software effectively. This transparency helps ensure that all necessary components are installed, facilitating a smoother setup and experience.
How do we measure it?¶
- At least one dependency stated is valid.
Types it applies to¶
- all
Weight¶
- 0.33
I3.2. Availability of software dependencies¶
What is being measured?¶
- Whether the software includes its dependencies or mechanisms to access them.
Why should we measure it?¶
- Providing dependencies along with the software can significantly enhance user experience by minimising the steps needed for installation. This method helps to eliminate common setup obstacles, facilitating a more streamlined and error-free user experience.
How do we measure it?¶
- Bioconductor, Bioconda, or Galaxy Europey among the metadata sources of the software is considered valid.
Types it applies to¶
- all
Weight¶
- 0.33
I3.3. Availability through dependencies-aware systems¶
What is being measured?¶
- Whether the software is distributed via a dependencies-aware system.
Why should we measure it?¶
- Ensuring software availability through dependencies-aware systems like package managers enhances accessibility and ease of installation. This feature allows users to efficiently manage software and its dependencies, improving reliability and reducing compatibility issues across different environments.
How do we measure it?¶
- Bioconductor, Bioconda, or Galaxy Europey among the metadata sources of the software is considered valid.
Types it applies to¶
- all
Weight¶
- 0.33