Embed Size (px)
Citation preview
Susan Thompson, CBAP
A Business Context for Acceptance Testing
Susan Thompson, CBAP, PMP, CSQA, CSTE
Presented to SCQAA-OC April 20, 2010
Susan Thompson, CBAP
What’s your experience…
• In what ways have you been involved with acceptance testing?
• What seems to work well?• What doesn’t work well (or is a
poor use of resources)?• What would you do differently?
4/20/2010
Susan Thompson, CBAP4/20/2010 Susan Thompson, CBAP 3
Summary• The V-model• What acceptance testing should do• Case study: Cell phone billing and
administration system–Context diagram–Business events–Enhancement #1–Enhancement #2
Susan Thompson, CBAPSusan Thompson, CBAP 4
V-Model
Source: QAI CSBA CBOK ver 9-1
4/20/2010
What acceptance testing should do
• Test the system in ways that actual users would use it
• Demonstrate how the system fulfills the business requirements
• Demonstrate how the system addresses business risk
Susan Thompson, CBAP 54/20/2010
Case study: business background
• Company had been doing custom development of a cell phone billing and administration systems using a “clone the last one and change it approach”
• Wanted to “productize” things as much as possible, both to have more consistent code and quality and to speed up the development/customization cycle for existing and new customers
Susan Thompson, CBAP 64/20/2010
Susan Thompson, CBAPSusan Thompson, CBAP 7
Case study: context diagram
4/20/2010
Susan Thompson, CBAP4/20/2010 Susan Thompson, CBAP 8
Case study: business events…Phone number administration events• Request numbers from numbering plan administration• Receive notice of numbers transferred to other providers
Customer-initiated events• Customer requests new phone service• Customer requests additional feature• Customer requests removal of feature• Customer pays bill• Customer disputes bill
Susan Thompson, CBAP4/20/2010 Susan Thompson, CBAP 9
Case study: … business eventsTime-initiated events• Bill customers• Send 30-day notice• Send 60-day notice• Send 90-day disconnect notice• Disconnect service
Susan Thompson, CBAP4/20/2010 Susan Thompson, CBAP 10
Case study: enhancement #1Phone numbers stored in “warehouse”• One customer had a customization that allowed
a user to move phone numbers from one warehouse to another
• Another customer had a customization in which a warehouse could be set up only to allow the user who added a phone number to remove it from the warehouse
• Goal was to include both customizations in the standard product
Susan Thompson, CBAP4/20/2010 Susan Thompson, CBAP 11
Case study: enhancement #2• Many customizations added to enhance new customer
setup, and improve account usability and changeability• A robust test suite was developed to ensure that each
customization worked, both in isolation and together for account setup and account change.
• Another test suite demonstrated that the correct commands were sent to the telephone switch for these areas
Susan Thompson, CBAP
References• A Guide to the Business Analysis Body of
Knowledge® (International Institute of Business Analysis)
• Guide to the CSBA Common Body of Knowledge v9-1 (Quality Assurance Institute)
• Robertson, Suzanne and Robertson, James, Mastering the requirements process
• Robertson, Suzanne and Robertson, James, Requirements-Led Project Management: Discovering David's Slingshot
• www.volere.co.uk
4/20/2010
Susan Thompson, CBAPSusan Thompson, CBAP 13
Questions?
Susan Thompson contact information:[email protected]@[email protected]: 714-308-9464
4/20/2010
