Beyond Brute Force: Testing Financial Software

Abstract

Large software development projects that follow formal processes generally divide the work among separate roles on structured teams that tend to employ development staff whose technical expertise is domain-neutral. This is especially true of large outsourcing vendors. Yet, the end users' needs are expressed in the applied domain's specific concepts, terms, and logic. Testing financial software's functionality requires deep subject expertise and an understanding of quality assurance methods and processes. Thorough domain analysis, efficient test designs, specific methods, and well-prepared quality assurance staff are key elements for success.