Process
Better Software Magazine Articles
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 |
|
Book Review: Adaptive Software Development Johanna Rothman recommends the book Adaptive Software Development by James Highsmith. She says, "Highsmith shows the reader how to recognize when development practices need to change and how to acquire the skills to adapt. For a fresh approach to software development, be sure to check it out." |
||
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 |
|
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 |
|
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 |
|
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 |
|
User-Driven Design It doesn't matter when you deliver, if you build the wrong product. Development entails inferences and assumptions about the user, which are supposed to guide the build-process. However, even if development successfully matches the inferences and assumptions about the user, if those criteria don't match the Real User, the product fails. This article talks about how to incorporate the user into the requirements and design phase. |
||
The Top 13 Mistakes In Load Testing Applications This is a no-holds-barred discussion of common load testing errors and consequences. Load testing can and should be done long before a system has a stable or complete user interface. One reason that people often schedule load testing as a final step in a test or development plan is the confusion linking load testing with functional testing. |
Mark D. Anderson
June 26, 2002 |
|
In Search of Defect Tracking Systems Defect tracking systems influence business-critical decisions. Building and installing a corporate-wide defect tracking system takes a small but well-balanced development team. Your implementation may be as simple as opening the package and typing "setup" or it may take months of programming. Here's how to find and implement the right system for your organization. |
Bob Johnson
June 26, 2002 |