Software UAT Case study - Finserv

User Acceptance Testing
(A Case Study)

Oak Systems Pvt. Ltd. 2
Background
• A B2E application was to go live within a few weeks.
It was a ‘mission critical project’ for the customer-
ASP (Application service provider) who was involved
in servicing Financial activities to a large number of
its clientele.
• Margin of error had to be very low in the software.
• System was unstable and Reliability was low.
• Morale of the user was low.
IT WAS A CRISIS HOUR

What Next ?
Need for an external V & V service !!!
OAK SYSTEMS STEPPED IN

Project Status .. as we saw it
• Complex processes of Financial services
• Software developed by a third party vendor
• No acceptance criteria defined
• Inadequate/No Documentation
• No SCM in place
• Untested software being delivered
• Incomplete/Partial deliveries
• Lack of communication mechanism (in terms
of bug reporting and fixes) between parties

Our Mission
• To Draw an extensive user acceptance criteria.
• Provide technical inputs on missing processes.
• To Draw a plan for testing using domain
expertise
• To evaluate the software in terms of its
capabilities (applying FURPS+)
• To evaluate the performance.
• To evaluate usability of the software.
• To evaluate software (exe, docs, …) as per
pass/fail criteria.

Our Role
• System testing – The software was tested
extensively based on the configuration and business
requirements
• Usability testing – GUI testing spanning the
entire application was carried out with a stringent
usability requirements (guidelines). These
guidelines were prepared for the web scenario.
• Documentation review – All the documents were
verified for completeness, traceability.
• Unit testing – Each unit was tested in terms of
workflow requirement, data validation.

Modus Operandi
• Identified critical processes and fixed tolerance limits
for acceptability.
• Developed detailed test plan as to What functions to
be carried out and when it has to be carried out.
• Designed test cases based on configuration and
domain knowledge
• Adopted phased testing approach in synchronization
with delivery
• Identified bottle necks in the delivery in terms of
technical requirements.
• Established a seamless communication between the
software vendor and the user (ASP).

Project Statistics (Testing)
• Entry Phase: UAT;; Exit Phase: UAT
• Duration: 5 months
• Test team size: 10
• Effort spent: 30 person months
• Project development effort: 25 person years
• Number of Screens: 350
• Number of Reports: 100
• Environment: Solaris, Websphere, Oracle,
Actuate

• Number of Functional Test cases: 800
• Number of defects: 220 (25% of test cases)
• Number of Unit test cases: 5900
• Number of defects: 1006 (15% of test cases)
• Number of Usability defects: 2250
• Number of showstopper defects: 58

Percentage of Failed Test cases- M odulewise
0
10
20
30
Global Suite
Global Suite IT
Company Suite
HR Suite
HR Suite( Health
and welfare)
HR Suite
Attendence.
Pay suite
JV suite
Loan Suite
Transaction
Arrears
Bonus
Gratuity
Process

Far reaching effects
• Extensive testing uncovered bugs and also
limitations in terms of features. This enabled
product positioning in the Market.
• The documents in right shape meant that the
maintainability of software was made easier.
• Enhanced usability feature meant return on
investment (ROI) (less effort and time to
accomplish the same volume of work)
• Increased confidence in product meant more
business.

Contact for more information
Oak Systems Pvt Ltd
#27, NGEF Lane, Off 100 Feet Road,
Indiranagar 1st Stage,
Bengaluru – 560 038 INDIA
Email: contact@oaksys.net
Ph: +91-80-41267681
http://oaksys.net

Software UAT Case study - Finserv

More Related Content

What's hot (20)

Similar to Software UAT Case study - Finserv (20)

More from OAK Systems Pvt Ltd (6)

Recently uploaded (20)

Software UAT Case study - Finserv