| 1. |
Program Testing Methodology Part One: Preparing for Testing (4 Pages)
by Dr. Edward J. Moskal
Aug 6, 2004
Abstract : Program testing and debugging is one of the most critical aspects of implementing a computer system. Without programs which properly work, the system will never process information and produce the output for which it was designed. Testing procedures should be established and testing roles should be demarcated between the programmer and the analyst. Once this is done, test data that can test the limits of the program should then be created.
|
| 2. |
Web Testing Has Changed the Testing Landscape (3 Pages)
by C. Lisle
Dec 8, 2000
Abstract : Software testing vendors are forming alliances and partnerships with the vendors who actually service and support the delivery of Internet content. Thus do the realities of testing Internet applications sink in. Two instances: Mercury Interactive formed a strategic alliance with Akamai Technologies, and Segue signed NaviSite as its first Hosted Services Partner.
|
| 3. |
E-learning Course Design (6 Pages)
by Don McIntosh, Ph.D
Feb 23, 2006
Abstract : This article provides hints for the design of e-learning courses with regard to target audience, navigation, objectives, motivation, media, interactivity, assessment, aesthetics, tool selection, and evaluation.
|
| 4. |
Program Testing Methodology Part Two: Running Tests and Getting Approval (6 Pages)
by Dr. Edward J. Moskal
Aug 7, 2004
Abstract : After testing procedures have been created and the type of test data has been determined, link or string testing, and system testing must be executed to ensure the job stream is correct and to locate errors before production. Backup and restart testing must be also be conducted to ensure that the restart points within the system are accurately defined. Finally, to demonstrate the benefits and functionality of the system, management and user approval should be received.
|
| 5. |
CRM Testing Throughout Implementation (7 Pages)
by James Lyndsay
Oct 13, 2004
Abstract : In terms of strategic partnerships, the acquirer is responsible for judging how well customer relationship management (CRM) software will function on the equipment and at the site, and with staff, customers, and third-party applications. Acceptance testing involves three basic flavors: user acceptance, operational acceptance, and contractual acceptance. While it is not the only step involved when implementing a CRM system, testing is a fundamental way of finding information and will help you judge a system’s returns and pitfalls.
|
| 6. |
Quality Reassurance: How To Get What You Need from Acceptance Testing (3 Pages)
by James Lyndsay
Jul 4, 2006
Abstract : Integrating a new system with your organization places new opportunities, and new risks, at the heart of your business. We look at the thinking and negotiation that shape acceptance testing, and how it influences your assessment of the new system.
|
| 7. |
Quality reassurance - how to get what you need from acceptance testing (3 Pages)
by James Lyndsay
Dec 26, 2005
Abstract : Integrating a new system with your existing organization places new opportunities, and new risks, at the heart of your business. This article outlines the thinking and negotiation that shape acceptance testing, and how it influences your assessment of the new system's effect on your business.
|
| 8. |
Quality reassurance - how to get what you need from acceptance testing (3 Pages)
by James Lyndsay
Jul 7, 2005
Abstract : Integrating a new system with your existing organization places new opportunities, and new risks, at the heart of your business. This article outlines the thinking and negotiation that shape acceptance testing, and how it influences your assessment of the new system's effect on your business.
|
| 9. |
The Case Against Modifying Your Enterprise Software (3 Pages)
by Jeff Kugler
Nov 22, 2006
Abstract : The case against modifying enterprise software is a strong one. Standard software offerings are the products of millions of dollars of research, development, and extensive testing for consistent performance. For this and various other reasons, modifications almost never make sense.
|
CART 
