Investigating Software Packages
By Russ Finney
Once the technological environment has been decided upon and all of the business requirements have been spelled out in the form of process, data, or object models, why plunge right into creating a new wheel where one may already exist? At this point in the process, the team has accumulated a wealth of information for performing a detailed package search and evaluation. Spending even a small amount of time examining the available options can not only provide some fresh perspectives on how the business problem has already been tackled, but the investigation may also actually turn up a viable system solution.
So where should the team start? Depending on the platform, the first stop may range anywhere from the local software store to the nearest professional level library. Whatever the case may be, some of the sources listed below can provide credible leads to aid in the creation of a first cut package list:
- Professional software package listing and evaluation publications (DataPro, etc.). These contain extensive categorized application listings for mainframes, midrange machines, and stand-alone or networked personal computers.
- Industry specific trade journals and publications. Many times these may contain software reviews, package advertisements, or compiled software indexes.
- Direct contact with some of the larger business software vendors. These folks are always happy to share information about their latest offerings.
- Computer trade journals and publications. Once again, some digging can usually turn up a few worthwhile leads.
- Professional contacts with people working within companies which are already utilizing packages similar to the defined requirements. Depending on the sensitivity of the software, good leads can sometimes be obtained through these personal references.
Once this list has been compiled, simply making a few phone calls can help to sort out likely candidate packages as well as picking up leads on further packages. Directly calling the vendor usually will result in the receipt of additional material through the mail to assist in a more complete qualification. These vendor write-ups can greatly assist in helping to line up a short list of potential packages which deserve a more formal evaluation.
Sometimes the result of the package survey is that simply no off-the-shelf software exists which will be close enough to the business requirements to merit attention. If that is the case then so be it, the team must move on the re-estimation of the project and in order to determine if the custom built option is still feasible from a cost/benefit perspective. Otherwise, if viable package candidates were found, the next step should be some type of matrix evaluation approach (See VBM Methodology).
Copyright © 1999, Russ Finney, All Rights Reserved