What type of software is it?

(cf. Catalogue 0.1.1)

On which platform runs the tool?

(cf. Catalogue 1.4)

For what purpose was the tool developed?

(cf. Catalogue 1.5)

Which is the financial model of the tool?

(cf. Catalogue 1.6)

What is the development stage of the tool?

(cf. Catalogue 1.5)

Which programming languages and technologies are used?

(cf. Catalogue 2.3)

Does the tool reuse portions of other existing software?

(cf. Catalogue 2.3)

Which input formats are supported?

(cf. Catalogue 2.4)

Which output formats are supported?

(cf. Catalogue 2.4)

Which character encoding formats are supported?

(cf. Catalogue 2.4)

Is a pre-processing conversion included?

Does the documentation list dependencies on other software, libraries or hardware?

(cf. Catalogue 3.2)

If yes, is the software handling the installation of dependencies during the general installation process (you don’t have to install them manually before the installation)?

Is documentation and/or a manual available? (tool website, wiki, blog, documentation, or tutorial)

(cf. Catalogue 3.4)

Which format has the documentation?

(cf. Catalogue 3.3)

Which of the following sections does the documentation contain?

(cf. Catalogue 3.3)

In what languages is the documentation available?

(cf. Catalogue 3.3)

Is there a method to get active support from the developer(s) or from the community?

(cf. Catalogue 3.4)

Which form of support is offered?

(cf. Catalogue 3.4)

Is it possible to post bugs or issue using issue tracker mechanisms?

(cf. Catalogue 3.4)

Grade how straightforward it is to build or install the tool on a supported platform:

(cf. Catalogue 3.6)

Is there a test suite, covering the core functionality in order to check that the tool has been correctly built or installed?

(cf. Catalogue 3.7)

On which platforms can the tool/software be deployed?

(cf. Catalogue 3.8)

On which devices can the tool/software be deployed?

(cf. Catalogue 3.8)

If the tool is web-based: On which browsers can the tool/software be deployed?

(cf. Catalogue 3.8)

If the tool is web-based: Does the tool rely on browser plugins?

(cf. Catalogue 3.8)

Is there an API for the tool?

(cf. Catalogue 3.8)

Is the source code open?

(cf. Catalogue 3.9)

Under what license is the tool released?

(cf. Catalogue 3.9)

Does the software make adequate acknowledgement and credit to the project contributors?

(cf. Catalogue 3.9)

Is the tool/software registered in a software repository?

(cf. Catalogue 3.9)

If yes, can you contribute to the software development via the repository/development platform?

Can the code be analyzed easily (is it structured, commented, following standards)?

(cf. Catalogue 3.10)

Can the code be extended easily (because there are contribution mechanisms, attribution for changes and backward compatibility)?

(cf. Catalogue 3.10)

Can the code be reused easily in other contexts (because there are appropriate interfaces and/or a modular architecture)?

(cf. Catalogue 3.10)

Does the software provide sufficient information about the treatment of the data entered by the users?

(cf. Catalogue 3.11)

Is there information available whether the tool will be supported currently and in the future?

(cf. Catalogue 3.12)

Does the tool supply citation guidelines (e. g. using the Citation File Format)?

(cf. Catalogue 3.13)

What kind of users are expected?

(cf. Catalogue 4.1)

What kind of user interactions are expected?

(cf. Catalogue 4.1)

What kind of interface does the tool provide?

(cf. Catalogue 4.2 and 0.1.1)

Does the tool provide a particular visualizations (in terms of analysis) of the input and/or the output data?

(cf. Catalogue 4.3)

Is the user allowed to customize the functioning of the tool and the output configuration?

(cf. Catalogue 4.4)

Does the tool provide particular features for improving accessibility, allowing „people with the widest range of characteristics and capabilities” to use it?

(cf. Catalogue 4.5)