| 1. |
A Guide to Software Test Tools ( Pages)
by James Lyndsay
Apr 27, 2005
Abstract : Testing a system well is harder than building it. In the face of new risks introduced by the ever-increasing complexity of software and hardware, test tools may be your only practical way to be confident that you've got just what you paid for. From gathering the initial requirements to supporting the system after it has been deployed, test tools are available to support all phases of a project. This article looks at the ways that test tools can be used to design, code, and (of course) test a system.
|
| 2. |
A Guide to Software Test Tools (0 Pages)
by James Lyndsay
Dec 15, 2008
Abstract : Testing a system well is harder than building it. In the face of new risks introduced by the ever-increasing complexity of software and hardware, test tools may be your only practical way to be confident that you've got just what you paid for. From gathering the initial requirements to supporting the system after it has been deployed, test tools are available to support all phases of a project. This article looks at the ways that test tools can be used to design, code, and (of course) test a system.
|
| 3. |
A Guide to Software Test Tools (9 Pages)
by James Lyndsay
Jul 16, 2004
Abstract : Testing a system well is harder than building it. In the face of new risks introduced by the ever-increasing complexity of software and hardware, test tools may be your only practical way to be confident that you've got just what you paid for. From gathering the initial requirements to supporting the system after it has been deployed, test tools are available to support all phases of a project. This article looks at the ways that test tools can be used to design, code, and (of course) test a system.
|
| 4. |
Best of Breed Versus Fully Integrated Software: The Pro's and Con's ( Pages)
by Joseph J. Strub
Aug 8, 2003
Abstract : After dealing with the over-hype of Y2K, companies have started to reconsider the best of breed as a viable solution to satisfy their software needs. This comes as a shock to the corporate systems culture when user communities were told that fully integrated software such as ERP, SCM, and EAM were the only way to meet their software needs. After developing a level playing field, this article examines the pro’s and con’s of one alternative over the other. Read on to see if you agree with the merits of the best of breed or fully integrated software approach to software selection.
|
| 5. |
Ways of Finding Software Vendors: The Pro’s and Con's ( Pages)
by Joseph J. Strub
Jul 30, 2003
Abstract : So you are looking for software to support the critical functions of your company. Unfortunately, you can't go to your local Software'R'Us. This article discusses several sources and methods for identifying potential software vendors. It also examines the pro's and con's of each method.
|
| 6. |
ERP Showdown—Round 2! Exact Macola ES vs. Infor SyteLine vs. QAD MFG/PRO ( Pages)
by Dylan Persaud
Apr 11, 2007
Abstract : I'm Dylan Persaud, senior analyst at Technology Evaluation Centers. Due to the overwhelming response to our first ERP Showdown, we're pleased to present another head-to-head discrete enterprise resource planning (ERP) comparison. Here, then, is ERP Showdown, Round 2!—featuring Exact Macola ES vs. Infor SyteLine vs. QAD MFG/PRO.
|
| 7. |
They Test Web Sites, Don’t They? ( Pages)
by D. Geller
Jun 7, 2000
Abstract : RSW Software upgrades one product and releases a second. The products enable companies to test the function and load carrying capability of websites and middle tier applications.
|
| 8. |
Progress Offers a Test Drive ( Pages)
by A. Turner
Apr 10, 2000
Abstract : Progress Software offers customers the opportunity to test drive applications via the Internet.
|
| 9. |
Program Testing Methodology Part One: Preparing for Testing ( 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.
|
CART 
