Table 1 The feature groups identified by the workshop participants
Feature | Definition | Bought? | Example competency question |
|---|---|---|---|
Software | The software itself | Yes | What is the name of the software? |
Data | Data that the software consumes and produces | Yes | Will it render a gif format image? |
Function | The task the software is used to do, sometimes called objective | Yes | Does this software provide XML editing? |
Algorithm | The specific instructions as part of software to perform a given task | No | What is the normalization algorithm used in this software? |
Configure parameters | Parameters required to run the software; settings | No | What are setting needed to run this analysis? |
Life cycle | Stage of maturity of a piece of software | No | Does the software meet the ISO-4 standard? |
Version | The version information | Yes | What is the latest version of this software? |
Supplier | Developer and/or maintainer of software | Yes | Who developed this software? |
Dependencies | Other pieces of software or libraries required to run it | No | What are the dependencies for using OWL-API? |
Interface | Modes of interaction with the software | Yes | Is there a Web API for Blast? |
Source code location | URL or otherwise of source code | Yes | Where can I get the code? |
Cost of ownership | Cost to purchase but also to run | No | Is it free? |
Platform | Which platform is required to run software | No | Will the software run on Ubuntu? |
License | What license and usage restrictions exist for a given software | Yes | What software can I use for my task which is under the Apache 2 license? |
Architecture | Architectural structure of the software, such as peer-to-peer | No | Is the software client-server? |