|
Trust Everyone, but Cover Your Assets Need a place to go to get the solutions you've been craving? Management Fix is what you've been looking for. In this issue, find out how to manage when you suspect someone on your team may have been stealing from the company.
|
|
|
A Killer Bug for the New Millenium We're pleased to bring you technical editors who are well respected in their fields. Get their take on everything that relates to the industry, technically speaking. In this issue, find out why our guest editor thinks he's found the bug that will once again bring testers to the forefront—a bug that dwarfs Y2K and could put big, rich software companies out of business.
|
|
|
Case Your Own Joint Hackers are going to probe your system looking for weak spots and holes. What will they find? Learn how to uncover your own security vulnerabilities before the bad guys do.
|
|
|
Warning: Security Storm Brewing For too long now, consumers have been bailing, patching, and plugging their software each time a new security hole is discovered. And they've been absorbing the damage done by the leaks. A wave of security-conscious buyers is rising, demanding software that is sound and secure by design. Are you ready to give it to them? Find out why you should be.
|
|
|
Source Code, Power Source, and Outsourced Get the software engineering slant on items from the recent news.
|
|
|
Pay No Attention to the Quality Behind the Curtain To continue our series exploring what it means to care about quality and to build better software, we spoke with Compuware executive David Kapelanski, who says that true quality is invisible.
|
|
|
The Liar's Contest Politics is a game we're asked to participate in each and every day. But when your project's future is on the line, do you want to play around? The penalties and risks surely outweigh any reward. Discover how to extricate yourself from these losing battles.
|
|
|
(Not So) Trivial Pursuits How one tester learned the hard way that quality is in the eye of the pocketbook holder.
|
|
|
Problem Resolution Optimization No matter how well we plan and execute software development, defects are generated and can escape to the customers. Failure to quickly resolve software problems leads to negative consequences for our customers and increases internal business costs. A quick deterministic
method to prioritize problems and implement their solution helps to reduce cycle time and costs. Achieving this goal requires several steps. The first is to determine a model that links problem resolution performance to institutional variables and problem characteristics. Statistical Design of
Experiments (DOE) is a tool that provides data requirements for estimating the impacts of these variables on problem resolution. Once data has been gathered, the results of statistical analysis can be input into a mathematical optimization model to guide the organization.
This paper describes such an analysis.
|
|
|
Product Risk Analysis Clarifies Requirements This presentation re-emphasizes that requirements are important. The difference between functional and nonfunctional requirements will be covered. Then, Product Risk Analysis will be described, along with the elements of the analysis and steps toward performing the analysis.
|
|