XPRS Testing Methodology
Original Publication Date: 2004-Mar-25
Included in the Prior Art Database: 2004-Mar-25
The XPRS (Cross-Application Performance Reliability Stress) Testing methodology is the implementation of two decision points: XPRS Testing Exemption in the Design phase and XPRS Testing Waiver Review toward the end of the Development phase, and the execution of an XPRS Test which occurs as the last step in the pre-Deployment phase.
XPRS Testing Methodology
Disclosed is the XPRS (Cross-Application Performance Reliability Stress) Testing methodology that addresses application performance issues throughout the application development lifecycle. The XPRS Testing methodology, designed to be cost effective and efficient without sacrificing effectiveness, is comprised of two decision points and a XPRS Test positioned at critical points in the application lifecycle. The first decision is at the Design phase where the question is asked, "Is the architecture of the application in-line with corporate guidelines?" while the second is near the end of the Development phase where the question is asked "Is the application ready to be categorized as 'gold' code, ready for deployment into production?" XPRS test prior to the end of the Deployment answers the question "Can the application be installed in production and support the end-users?"
The first decision point, XPRS Testing Exemption, is designed such that applications implemented via well-known straightforward architectures can be exempt from the expenses of time and labor of an XPRS Test. This exemption is evaluated during the Design Review in the Design Phase. The exempted application owners will not have to prepare a submission to the XPRS Testing Waiver Review Board or submit to testing at the XPRS Testing center.
The XPRS Testing Waiver Review Board, the second decision point, is positioned toward the end of the Development phase to service those application owners who took it upon themselves to XPRS Test the application in their environment. The board's charter is to review the results of the performance and stress testing. A question and answer session is then called between the application owners and the board members to determine if the test conditions were production-like, the test scripts were representative of the end-user activities, and performance statistics gathered during the tests were sent to the Capacity Planning organization. The board is made up of representatives from the XPRS Test center, Service Delivery, Capacity Planning, and other such deployment organizations. Application owners who receive a wavier will not have to go to the XPRS Testing center prior to the end of the Deployment phase.
Finally, the XPRS Testing center executes XPRS Testing, whi...