It is advocated that “buy-in” may be better than “built-in”. There are many many reasons. One of them is the handy available choices in the market. But as far as there are choices, someone, you or your supervisor, has to make decision. This article from DMReview lead you through the evaluation process.
In summary, there are somethings you have to prepare by your own :
- Business Driver – e.g. saving in human resource in particlar areas, improved productivity …etc.
- Project Objective – e.g. target deliverable, target cost, and the priority of all these parameters …etc.
Something, you may obtain from the vendor :
- Architecutre – you need to know how the tool interactive with other tools ….
- Performance benchmark – please be aware that those information from vendor may not neccessarily reflect the truth, but better than nothing ….
- Funcationaliy – you have to sort out which is critical to you project ….
Sample table form you better to include in the evaluation report :
- Requirement Specification
- Evaluation Matrix
To complete the evaluation report, you also need the following :
- Executive Summary
- Business Drivers
- Project Objectives
- Implementation Timeline
- Multi-Year Acquisition Plan
- Vendor Evaluation Matrix
The original article talks about the evaluation for ETL tools, but the ideas do apply to many other areas.