|
Quality Assurance and Testing Brian Marick argues for using testers at the requirements analysis stage of a project. He says, "While QA is primarily about process, testing—my specialty—is about product. Whatever else a tester might do, she certainly eventually exercises the product with the aim of discovering problems a user might encounter. This essay is about that 'whatever else' the tester does."
|
|
|
Normal Processes Using a sociological theory as his starting point, Technical Editor Brian Marick shows how sometimes systems can encourage local problems to blossom into system-wide catastrophes.
|
|
|
Big Ball of Mud Much of recent systems theory revolves around applying ideal software development patterns. Big Ball of Mud, in contrast, is for those of us who live and work in the real world, where most systems emerge haphazardly from minimally controlled chaos under constrained development conditions. Bar Biszick recommends and describes the Big Ball of Mud Web site.
|
|
|
How to Survive the Software Swamp For a project to make long-term progress, it must build a platform of basic engineering practices. On this platform are set the ladders of advanced techniques that you select using risk analysis. Properly managed, these processes help you avoid falling back into the swamp whenever the project is under pressure.
|
|
|
Book Review: Mastering the Requirements Process Brian Lawrence points to Mastering the Requirements Process as a valuable reference book. The book presents a complete step-by-step method for gathering, modeling, and specifying requirements. Along the way the authors offer easy-to-understand and appropriate examples that nicely illustrate how to apply their techniques.
|
|
|
Finding Patterns in Software "Patterns" have caught on among software designers, especially those working on object-oriented systems. More recently, patterns have been applied to organizational behavior, including patterns for organizing independent test groups. Brian Marick provides Web resources on the study of patterns.
|
|
|
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."
|
|
|
Testing and Quality: Are You As Bored As I Am? The next time someone says to you something like, "You can't test quality into a software project," you might reply, "Well, you can't manage it in either." There may be a pregnant pause, but perhaps it will lead to thoughtful discussions about testing and quality. At the very least, it'll make those twin subjects a whole lot less (shh!) Dullsville and boring!
|
|
|
Finding Answers on the Net The Internet provides a wealth of information on software quality and testing. However, finding that information can be a challenge. In this first edition of Web Watch, Brian Marick tells you how to start your search.
|
|
|
Anticipating Human Error This article makes three points. First, errors happen. Second, systems can encourage errors. Third, a basic understanding of the kinds of errors humans make can help us design better systems. Here are some suggestions to help avert trouble.
|
|