Quipoz

Ultimately the decision on which way to go when considering the future of business applications will boil down to whether to rewrite, transform/modernise, replace or re-use the current system. The factors associated with this consideration are numerous, but can be summarised as per the table below.

Rewrite	Transform
Unsatisfactory business fit and technology deficient Quality of code is poor High operating and maintenance costs High level of pending enhancements best included in re-write No suitable replacement package is available Willing to fund the cost of redevelopment Willing to undertake the BPR to fit the new environment	Satisfactory business fit but technology deficient Code quality is reliable High operating and maintenance costs Medium level of enhancements pending Not prepared to carry the cost of redevelopment or package Not willing to undertake the BPR to accommodate package or a new system
Replace	Reuse
Unsatisfactory business fit and technology deficient Quality of code is poor Suitable package is available Prepared to stand the cost of tailoring the package Willing to undertake the BPR to fit the package Willing to fund the cost of redevelopment Willing to undertake the BPR to fit the new environment	Satisfactory business fit but technology deficient Low operating costs Maintenance resources are available Low level of enhancements in the pipeline Not prepared to bear the cost of redevelopment Not willing to undertake the BPR Wrapping could provide acceptable Web access Prepared to accept temporary solution

It can therefore be seen from the table that transformation will generally considered to be the best option where:

• The existing application has a good fit with the current and future business needs
• "Off-the-Shelf" software not viable
• Web services are a current or future requirement
• New and/or extended functionality is desirable
• The current application is resistant to change

Comparison of time, cost and risk of transformation

This table clearly illustrates the advantages of the Quipoz solution when Buy, Build or Manual options are considered using the standard parameters of Time, Cost and Risk.

Time	Quipoz Q-TE	Buy	Build	Manual
Project (Elapsed)	4 months	10 months	24 months	9 months
User Acceptance Testing	2 months	3 months	3 months	4 months
Training Requirement	N	Y	Y	N
Cost (relative)
Services & Software	$4	$15-20	$10-15	$8-12
Risk
Business Fit	N	Y	N	N
Integration	N	Y	N	N
Training	N	Y	N	N

This comparison is based on actual project information from recent Quipoz projects.

Contact Quipoz for more information

We would be pleased to send you a copy of any of the following documents. All we ask is that you provide some basic information in return. We may contact you after supplying you with your requested documents. Our Privacy Policy explains how we will use any information you provide.

Quipoz: Quipoz Transformation Engine (Q-TE) White Paper

Transforming Enterprise Information

Quipoz: Database Migration Services using Q-TE

Moving to UDB/DB2

Quipoz: Database Migration Services using Q-TE

IMS to Relational

Quipoz: Database Migration Services using Q-TE

Teradata to DB2 EEE

Quipoz: Business Systems Documentation (Q-BSD)

The Importance of Complete Documentation

Quipoz: Data Cleansing using Q-TE