|
Hung Nguyen on Testing Web Applications Here is a list of sources on Web testing, with descriptions, that Hung Nguyen has collected over the years. While most of these resources are on the Internet in the form of useful links and articles, some are training courses and books that Mr. Nguyen finds helpful.
|
|
|
A Defining Moment People use the word "accountable" a lot lately. But what do they mean? Sometimes "You're accountable" really means "You're to blame for this!" Technical Editor Esther Derby takes a look at what's often the coded meaning behind the word "accountable."
|
|
|
A Blueprint for Success: Implementing an Architectural Review Process The most costly product defects are often a problem of software architecture. Testing your architecture is a crucial, but often overlooked, step in product development. Learn how to create apply a Systems Architecture Review Board for your own architectural review process.
|
|
|
Mission Made Possible: Harnessing Tools and Procedures to Test a Complex, Distributed System Automating unit, component, and integration testing can sometimes seem like an impossible mission. Read how one team of programmers combined the right tools and processes to make their test mission not just possible, but successful.
|
|
|
Adopting XP Extreme Programming (XP) takes practices that are known to be good and combines and applies them in a revolutionary way. Before you turn your team on to XP, check out the steps to take, and pitfalls to avoid, to make your project an "Xtreme" success.
|
|
|
Focused Improvement Improving processes takes planning, time, and effort. A formal improvement project that applies the best practices of development to process improvement can help focus your team and effect real and lasting change.
|
|
|
Preparing to Choose a CM Tool Do your homework when shopping for a CM tool. This article teaches you how to bypass the marketing hype to select the tool that will work best with your company's processes and tasks.
|
|
|
Why Nobody in Our Business Can Estimate Tim Lister gives three examples of software project failures that resulted from poor estimates. The main problem? Software practitioners often don't understand the difference between an estimate and a goal. Here is some advice on how to be better estimators.
|
|
|
Managing Technical People (When You're No Techie) There's a lot more to managing software teams than understanding the technology. Do you know how to elicit requirements from users? Do you work well with management? Do you have a knack for asking the right questions at the right time? Not knowing where to put the semicolons in a line of code isn't a big deal. Knowing how to lead people–that's a big deal. Elisabeth Hendrickson explains how to bring your own unique talents and skills to the table.
|
|
|
A Look at Rational's RequisitePro Creating requirements involves tracking and documenting all of the criteria for a system's success. A requirements management tool, such as IBM Rational's RequisitePro, can support this effort. While the tool won't verify that the requirements are consistent, correct, complete, relevant, coherent, and testable, it can help manage the task more efficiently by allowing you to document, track, and maintain the requirements in an automated fashion.
|
|