The Latest
|
Houston, We Have a Problem[magazine] Errors start with individuals, and a primary job of testers/QA people is to prevent those errors in the first place. But an equally important part of the job is to find them once they are there, understanding that errors will happen. Jon Hagar asks, "What can we do personally, above and beyond the normal day-to-day jobs that we testers and developers have?" |
||
|
I am a Bug, and Refactoring[magazine] Our editors recommend the books I am a Bug (a children's book written by a software development manager and tester to explain his job to his children) and Refactoring: Improving the Design of Existing Code (by Martin Fowler, with contributions by Kent Beck, John Brant, William Opdyke, and Don Roberts). |
Brian Marick
June 26, 2002 |
|
 |
Network Testing with Shunra's STORM[magazine] STORM is a software-driven combination of hardware and software that recreates multiple, real-life, WAN links in terms of bandwidth limitations, packet loss, latency, jitter, and more–all in a local area network (LAN) lab. By providing a test bed that brings the WAN into a controlled and repeatable LAN environment, we can test and evaluate the performance and robustness of IP applications or devices before wide-scale deployment, or compare new technologies before field testing. |
Ron Ioszpe
June 26, 2002 |
|
The Wonderful World of Software[magazine] Former STQE magazine Technical Editor Brian Lawrence shares a tale about why a commitment to quality and paying close attention to detail are critical elements in building better software. It’s all about careful planning and anticipating customer behavior. Go with Brian on a stroll through one of the oldest, best-known amusement parks to find out more. |
Brian Lawrence
June 26, 2002 |
|
|
Reference Point: The Software Project Manager's Handbook[magazine] The Software Project Manager's Handbook is an excellent reference for the experienced or moderately experienced project managers who are looking to expand their "bag of tricks." Use this book as a reference to bone up on a specific topic, or use the case studies and questions to help you design and implement a feasible project plan. |
Maureen A. O’Hara
June 26, 2002 |
|
|
How Do You Build the Right Software Right?[magazine] Technical Editor Brian Lawrence explains his top-three list of things to do to deliver the right software right: risk-based planning, problem definition and modeling, and congruent leadership. |
Brian Lawrence
June 26, 2002 |
|
 |
Making Numbers Count[magazine] Numbers count—no two ways about it. But any numbers you include in a bug report should also include the appropriate units of measure. In an example from their experience, David Wilson and Leonidas Hepis explain the importance of using consistent terminology and units of measure. |
|
|
I Think, Therefore I Prototype[magazine] Prototypes can help you deliver the right software. Here, Technical Editor Brian Lawrence gives examples of prototypes and some guidelines for prototyping. |
Brian Lawrence
June 26, 2002 |
|
|
A Cautionary Tale[magazine] Technical Editor Brian Marick uses a fairy tale format to warn software professionals against using easy-to-acquire numbers in place of human judgment. |
Brian Marick
June 26, 2002 |
|
|
Software Requirements[magazine] Brian Lawrence and Johanna Rothman recommend Software Requirements by Karl Wiegers, a "readable, practical book about gathering and managing requirements, focused on best practices." |
||
|
My Next Mission (And How You Might Benefit from It)[magazine] Technical Editor Brian Marick proposes organizing a public effort to test a real software product. |
Brian Marick
June 26, 2002 |
|
 |
EXtreme Documentation[magazine] The kind of collaboration that Extreme Programming engenders can benefit both publications and development. Writing, like programming, is a naturally iterative, revisionary process. Dana De Witt Luther shares what she's learned about documenting an Extreme Programming project, using iterative planning meetings and story cards. |
Dana De Witt Luther
June 26, 2002 |
|
Interesting Times[magazine] Technical Editor Brian Lawrence offers some troubling trends he sees in the world of software development and testing, including software produced in "Web Time" and mainline business functions being moved onto Web-based systems. |
Brian Lawrence
June 26, 2002 |
|
|
When Your Manager Is No Techie[magazine] It's a pretty good bet that at some point in your career you and your work will be managed by someone who doesn't really understand what you do. Here are some ways to close the communication gap when you have a nontechnical manager. |
Alyn Wambeke
June 26, 2002 |
|
|
Measuring Up[magazine] 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 |
Pages
CMCrossroads is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.