Generic process involved in selecting packaged software

Here is a generic process to follow when you are tasked with selecting utility packaged software.

The first thing to do is to determine the mission of the software.  E.g. it might be to 'lower time between lead generation and the close of a sale.'.

Then:

1. Identify Alternatives
2. Collect a feature list that these products support.   There are likely features to the product that you are not even aware of.
3. Identify features that are or might be of interest to you -- perhaps even prioritize them.
4. Evaluate/Compare three (you can choose a smaller or larger number) of the alternatives -- (these are not in any order):
1. Cost
2. Licensing terms
3. Performance
1. Identify one or more metrics -- say 'Transactions per second'.
2. Graph CPU, Memory, Latency and Disk I/O against the metric.
3. Platforms (e.g. Windows/Linux) supported
4. Databases required/supported (Oracle, DB2, MS-SQL Server etc.)
5. Viability of the product and the selling organization
6. Clustering: Distribution and Failover including rejoining by failed servers
7. Ease of install, support, upgrade etc.
8. Security
9. Audit Logging
10. Support for performance and network monitoring tools (e.g. SNMP).
11. Any other specific to your requirements.  E.g. you may have some need to have the software be stateless.
5. Summary and Conclusion/Recommendation, taking special and specific care to document how your selection supports the mission.