Application Lifecycle Management
Better Software Magazine Articles
Faults of Omission Brian Marick is obsessed with faults of omission in software code, and he thinks you should be too. In this Bug Report, Marick describes coding omissions, design omissions, and requirements omissions, and offers some ways to prevent (or at least test) them. |
Brian Marick
June 26, 2002 |
|
A Look at Cost Xpert John Magill found Marotz's Cost Xpert 2.0 to meet his requirements, offer some important relevant program factors, and permit him to change or adjust the factors to establish an estimating window or boundaries, all at a competitive price. |
John Magill
June 26, 2002 |
|
A Look at e-Test Suite 301 by RSW RSW Software’s e-Test Suite contains four main components. The reusable scripts recorded with RSW e-Tester (the functional testing tool) feed RSW e-Load (the performance and stress-testing tool). For reporting and analysis purposes, results gathered during performance testing feed to RSW e-Reporter. The final tool, RSW e-Monitor, is responsible for monitoring the status of Websites by sending periodic page requests and validating them against previously recorded results. |
Christopher Nolan
June 26, 2002 |
|
Learning to Love Unit Testing Unit testing can become a developer's best friend. Find out how and why from two programmers who now rely on this practice to improve development. |
||
A Study in Failures Examples of mistakes, manifestations, and problems help us understand all parts of the software. Brian Marick suggests Web resources that examine software failures. |
Brian Marick
June 26, 2002 |
|
The Two Bugs Brian Marick applies the philosophical concept of "ready-to-hand" to software programming and describes two bugs that illustrate problems caused by mismatched reuse of ideas. |
Brian Marick
June 26, 2002 |
|
Measuring Up You measure because you want to make better-informed decisions. But even simple, harmless-looking measures can be dangerous. For example, they can give you a nice, clear picture of an illusion. Do you want to base your decisions on illusions? Technical Editor Brian Lawrence advises that, before you dive into measuring anything, ask yourself, "Will measuring do more harm than good?" |
Brian Lawrence
June 26, 2002 |
|
Welcome to Software Testing and Quality Engineering Technical Editor Brian Marick introduces the first issue of STQE magazine. He says the magazine "is for people who get their hands dirty, whether by writing tests, cranking out code, managing others, or--perhaps the hardest task of all--being the internal QA consultant who has no direct authority but must somehow persuade ten projects with impossible deadlines to think strategically." |
Brian Marick
June 26, 2002 |
|
What's in a Name? Technical Editor Brian Marick outlines a goal for the magazine and its readers: gradual process improvement, driven by immediate needs. |
Brian Marick
June 26, 2002 |
|
Calculating the Value of Testing From an executive's perspective, software testing is not a capital investment in the physical plant, an acquisition, or another readily accepted business expense. A Quality Assurance Manager describes how to present testing as a business-process investment. |
James Bullock
June 26, 2002 |
Pages
Recommended Web Seminars
On Demand | Building Confidence in Your Automation |
On Demand | Leveraging Open Source Tools for DevSecOps |
On Demand | Five Reasons Why Agile Isn't Working |
On Demand | Building a Stellar Team |
On Demand | Agile Transformation Best Practices |