|
|
It’s Not About the Clicks: Understanding the Other 90% of ePayments Testing Activity
- Discovery – Gaining knowledge of an upcoming event that will require ePayments testing
While discovery may occur during conversations in meetings (or with colleagues at the water cooler), more often discoveries are triggered by the release or pending implementation of one the following. The key to successful discovery is to secure information on these occurrences soon enough to adequately test and minimize the risks to your organization.
- Network mandates
- Software updates
- Regulatory change
- Mergers and acquisitions
- New payment instrument or new transaction
- Database changes
- Disaster recovery changes
- Research – Finding resources for more information about the event and the testing requirements
Research should not be limited to printed resources, but should also involve contacting knowledgeable personnel from which to gain insight and expertise. Be sure to identify areas that will experience the greatest impact from the event and involve those personnel during this phase. Note that the people you draw on as resources may be inside your organization (database administrators, systems engineers, network administrators, key settlement personnel, etc.) or outside your organization (vendors, networked peers, etc.).
- Personnel resources
- Resources from Development, Operations, Accounting, Card Management, QA, and Production (oftentimes accessing resources such as developers, QA specialists, system analysts, and others across departmental boundaries)
- Vendor contacts
- Contacts at card associations, financial networks, etc. (as determined by the upcoming event)
- Networked peers (former co-workers, members of professional associations or societies)Contacts at card associations, financial networks, etc. (as determined by the upcoming event)
- Printed resources
- Specifications, technical notices, network publications
- Product documentation
- Product support sites (knowledge bases, FAQs, etc.)
- Internet searches
Copyright © 1996-2010, Paragon Application Systems
|