A major flaw in the way most code is designed allows you to break the code by exploiting the flaw. Learn how this "trick" can force software into a state from which it produces incorrect results. Observe live demonstrations on applying this "trick" to popular software programs and code. Discuss ways to build test automation that methodically searches for these flaws.

The Internet can be a less-than-secure place to conduct business. So how do you make sure your Web site is secure from attack? Is a firewall the only line of defense you need? This presentation provides insight into the different attack points that a hacker could seek to exploit. It teaches you what to look for when testing the security of a Web site and delivers a simple, ten-step process for testing the security of a Web site.

"This isn't what I need," states Customer Bob. "But it's what you said you wanted," replies Engineer Joe. "It's not right. I need something else." We've all encountered this classic users-don't-know-what-they-want scenario. The fact that software professionals continue to have this same experience over and over again suggests that we're overlooking the real reasons for the user/engineer disconnect. This presentation contrasts the different uses of the term "requirements" as it explores the possible solutions to improving understanding between business people and technical people.

Dan Downing's experience with stress testing projects has revealed a handful of common denominators present in most Web site performance problems. These include memory starvation; a CPU-gobbling database access; improperly sized heaps, caches, and pools; poor application design; and load balancing that doesn't balance. This presentation uses actual B2C and B2B project examples to show you a symptom-measurement-diagnostic approach to understanding, exposing, and documenting these common problems.