Our Corporate motto:

"We do not sell hardware or software, we sell expert advise"

• Are you considering issuing a request for proposal or quotation for the purchase, or outsourced development of applications software for your organization?

  Before selecting a solution or beginning your applications implementation and integration effort, it is critically important that sufficient requirements are clearly and accurately defined.

   

• The primary reason most organizations tend to shortcut this phase is the belief that it will take too long or that the spec will not be useful for the developers/vendors.  This is certainly an understandable premise given the common lack of effective requirements definition processes in most organizations.

• A business requirements document provides the blueprint for the system and the basis for the selection, design or functional specification of the software. Very often, skipping this essential step inevitably results in budget overruns, missed project and implementation deadlines and missing or incorrect software functionality. Cesar Ortiz follows a set of core software selection best practices that are focused on business requirements (vs. product features).

Return to Home Page