This paper describes Experian’s efforts to reduce schedule risk and to improve system quality by instituting a formal testing methodology, both for building a large replacement system and for long term ongoing evolution of that system. Successful testing depends, among other things, on thorough and relatively stable requirements.
Members-Only Content
This content is restricted to members only.
You must be logged in with an active membership to access this page.
Please click the link below to log in. If you do not have an account or your membership is inactive, you may need to register or renew it.