Running Down Assumptions Do you think the assumptions you make about your software project are important? I do. One of the biggest sources of software project failure is hidden assumptions, especially about your requirements. These assumptions have a way of coming out of the woodwork–usually at the worst possible moment–to foil your projects. But there are ways to track down and expose assumptions. |
Brian Lawrence
November 3, 2000 |
|
Shhhhhh! You Can't Say That! Treating symptoms instead of the root cause of symptoms is a mistake that dates back millennia (just ask Socrates). The current-day workplace is no different. In Johanna Rothman's column, we get a glimpse at what happens when a company doesn't value its people. |
||
The Science and Art of Web Site Load Testing Web site load testing is very different from traditional load testing and requires new tools and new approaches. Most Web site load tests are wildly inaccurate and unrealistic and consequently useless or dangerously misleading. Useful load testing requires loading a Web site with different scenarios, at different load points, and monitoring all the key components. Approach Web site load testing as 80% science and 20% art. |
Alberto Savoia
October 20, 2000 |
|
The Indispensable Test Team Quite often in the world of software engineering, testers and Quality Assurance (QA) managers find themselves to be the "last hired" and the "first fired." In some IT shops, QA does not exist at all. In spite of this, recent years have brought major breakthroughs in the areas of software testing and quality assurance. |
Terrye Ashby
October 20, 2000 |
|
Relentless Application Development Relentless Application Development is our term for continuous, rapid development and deployment of mission critical applications in highly changeable environments. Time sensitive development; Rapidly evolving new technology and methods; Computing technology is changing very rapidly, giving more power for less money. |
||
Taking the Heat When testers are left with a mess on their hands, what should they do? When this column appeared during StickyMinds' first month, October 2000, it provoked several reader comments. In it, Bret Pettichord asks the question: "Is it the tester's fate to 'work the clean up crew?'" |
||
Weighted Stability Index (WSI) Metric Model Methods, such as McCabe's Cyclomatic Complexity, have proven that complexity is a reliable predictor of defects. Although several methods exist to measure current system complexity, by using the Weighted Stability Index (WSI) Metric Model the potential impact of design changes can be weighted and measured. This provides a method to judge and plan for the potential stability impact from system changes. |
Mike Libassi
October 20, 2000 |
|
The Living Creature - Testing Web Applications What do we mean by "Web Application"? There is an incredible range of sophistication in web applications from a simple company web site with "brochure ware" to sites like Yahoo or Amazon with complex search engines and order fulfillment. One way to look at the web application architecture is to take the model of a traditional business transaction application and to replace the user front end by the web site. A Customer acquires goods and/or services from your company, in exchange for money. There are mechanisms in place to facilitate that transaction between client and company. Instead of a sales rep, a clerk, a cashier, or such person, you have a browser pointing at a web site. The company is never closed! Customers can serve themselves. |
Andrea MacIntosh
October 18, 2000 |
|
Automating Test Case Generation in a Pattern-Based Development Environment "With deadlines tightening and workloads increasing, software engineers are constantly looking for ways to improve the process of software development. They are streamlining their customers' processes, so why not maximize their own efficiency? One way to do so is with automatic test case generation." |
Tim Van Tongeren
October 17, 2000 |
|
Cem Kaner's Bug Advocacy Slides Time is in short supply. If you want to convince the programmer to spend her time fixing your bug, you may have to sell her on it. (Your bug? How can it be your bug? The programmer made it, not you, right? It's the programmer's bug. Well, yes, but you found it so now it's yours too.) Sales revolves around two fundamental objectives: motivate the buyer (make her WANT to fix the bug); and overcome objections (get past her excuses and reasons for not fixing the bug). This presentation shows you how. (This presentation is available in PowerPoint and PDF format. Please read the usage and licensing information that precedes the content.) |
Cem Kaner
October 16, 2000 |
Pages
Upcoming Events
Oct 01 |
STARWEST Software Testing Conference in Anaheim & Online |
Nov 05 |
Agile + DevOps East The Conference for Agile and DevOps Professionals |
Apr 28 |
STAREAST Software Testing Conference in Orlando & Online |
Jun 02 |
Agile + DevOps West The Latest in Agile and DevOps |