When organizations focus on exposing errors in any kind of application, they
traditionally focus on testing. Once an application is finished, it's passed
to a QA team to find and report problems. There's some back and forth as the
QA team reports problems, development fixes them, QA retests the application,
and so on. Once that cycle has been repeated a few times (if there's time for
that), the application is released. This approach is problematic, however.
The quality of the application is assessed at the end of the project. By that
time, incorrectly implemented requirements or bugs may be firmly planted in
the application and have features built on top of them, and addressing the
problems can be very difficult and time-consuming, if not impossible. With no
way to dete... (more)