|
|
This is part 2 of a 3 part
message.
#########
>>> see part 1 for
introduction and questions (1 - 6)
<<<<< 7. If a client has customized the code
extensively, is the client responsible in some way for identifying
non-vanilla-BPCS date fields, or is that the supplier's sole
responsibility?
8. The following questions pertain to the
time period beginning with the first delivery of the repaired
system:
a. Who is responsible
for repairing errors discovered during the detailed testing phase?
b. Who is responsible
for repairing errors (if any) discovered after cutover to live
production?
c. Will the supplier
repair errors during this post-delivery period at no charge? If so, is there a
time limitation on this no-charge repair policy?
d. How many errors are
typically discovered after delivery of the repaired code? (The answer should
include all errors in all facets of the application, including custom RPGLE
bolt-ons, Query definitions, etc., etc.)
e. Do any of the errors
stem from data/code not directly tied with a date value? Are the errors
easy to see or hard to see?
f. Will the
supplier provide multiple customer references who are willing to answer points
8.d. and 8.e. ?
9. Does the process require any
on-site help from the supplier? If so, who pays for travel
expenses?
10. What is the cost (including travel expense,
if any) per line of code submitted for repair? (Exclude from
the denominator those lines of code that the client is expected to repair, if
any).
11. What is the total elapsed time from contract
signature to cut-over to production?
12. Does the repair process and/or the
client's ongoing usage of the repaired application rest on any
patent?
>>> see part 3 for
additional questions (13-16) and concluding remarks
<<<<< |
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
