The Case for Policy-Driven Development , April 2012

Learn how policy-driven development can help businesses in the embedded systems space overcome the shortcomings of traditional software development.

SELEX Case Study , January 2012 - 714 KB PDF

SELEX wanted to eliminate software defects early in the SDLC. Learn how Parasoft static analysis helped them increase reliability while reducing reduced development time, costs, and resources.

Parasoft Concerto Ties Agile Development and Management to Automated Defect Prevention, End-to-End QA Testing , September 2010

Parasoft announced Parasoft Concerto for Agile, which ensures greater productivity and more predictable outcomes by extending flexible project & task management with a continuous quality process that spans across the entire SDLC

Cisco Case Study , April 2010 - 459 KB PDF

To comply with corporate quality and security initiatives, Cisco Systems adopted static analysis, unit testing and code review. Learn how they automated these practices and seamlessly integrated them into their existing processes to deliver compliant code without impeding productivity.

Rethinking Software , Forbes, July 2009

Explores why writing and fixing applications remains a persistent pain point for most companies.

How to Fix The Productivity Problem That's Killing the Software Industry , CIO, March 2009

Antiquated software development methods strangle innovation and hobble business recovery effort. It's time that IT departments boost development productivity–and it's not that hard.

The Next Leap In Productivity , February 2009

This book explains how to survive in today's economy by making IT more productive, then leveraging that into improved productivity at the enterprise level— resulting in dramatically reduced operating costs.

Software Quality Needs to be a Continuous Process , SearchSOA.com, November 2008

Explains how establishing a continuous process that helps the team build quality and security into the software not only reduces defects and debugging, but also optimizes QA time and significantly improves team productivity.

Automated Defect Prevention Introduction , December 2007 - 1,454 KB PDF

This booklet introduces the key concepts featured in the book Automated Defect Prevention: Best Practices in Software Development. It is designed to provide you an overview of what Automated Defect Prevention involves and how it can benefit your development team.

Defect Prevention , Visual Studio Magazine, December 2007

Use Automated Defect Prevention as a software management strategy that increases application quality through process improvement

Unlocking the Power of Automation: Exclusive Q&A with Dr Adam Kolawa , SOA World Magazine, December 2007

Discusses how Automated Defect Prevention (ADP) an approach to software development and management that makes quality a continuous process throughout the software development lifecycle gives developers more time to focus on the creative tasks they enjoy most.

Parasoft's Adam Kolawa: Software Quality is a Continuous Process , SearchSoftwareQuality.com, November 2007

As the diversity of tools used in software development has grown, best practices for managing the development process have often lagged. A more comprehensive infrastructure is needed for projects to regularly succeed.

Establishing an Infrastructure for Productive Development , Java Developer's Journal, September 2007

This article explains how five industry-standard practices reduce the amount of avoidable waste in the software development process, enabling developers to satisfy business goals without compromising their craft.

Automated Defect Prevention: Best Practices in Software Management , September 2007

This book introduces Automated Defect Prevention (ADP): a practical approach to software management through process improvement. This strategy is enabled by an infrastructure that automates repetitive tasks, tracks project status, and provides instant access to the information needed for informed decision making and process improvement.

Infrastructure for Productive Development , July 2007

Learn how to reduce the amount of avoidable waste in the software development process, enabling developers to satisfy business goals without compromising their craft.

TransCore Case Study , January 2006

TransCore needed a cost-effective way to ensure the reliability of their Java-based toll-road payment collection systems. Learn how static analysis and unit testing helped them achieve this by exposing defects early when they could be resolved with minimal rework and added costs.

Lehman Brothers: Outsourcing & Code Quality Management , November 2004

Learn how the adoption of unit testing and static code analysis allowed Lehman to control the quality of code delivered by outsourcers, enhance the productivity of its development staff, improve the overall reliability of its applications, and create consistent predictability of project release dates.

Prevention's the Cure , Software Development, August 2004

Explains how static analysis can help you shift focus from finding bugs to building quality into the code.

Location! Location! Location! , Better Software, May 2004

In real estate, it's not so much which house you buy as where you buy it. The same is true for bugs—the bug itself isn't as important as pinpointing where the bug lives and breeds. Learn one way to track down a bug's true source and prevent it from recurring.

Banish Security Blunders with an Error-prevention Process , DevX, April 2004

Traditionally, application security is an afterthought—we build our apps and try to poke holes in them later. Why not take potential security breaches into account from the very beginning? The Automated Error Prevention Methodology provides a framework you can use to integrate security concerns into your app development right from the start.

Getting the Most From Your Quality Initiatives , Computerworld, April 2004

Explores the real problem with process improvement initiatives there is no practical way to get them off the page and into your software development life cycle and proposes solutions.

Love Bugs? , SD Times, August 2003

Argues that bugs aren't so bad because they provide a prime opportunity to improve software quality.

Why Aren't We Doing More to Prevent Errors? , Computerworld, August 2003

Argues that the software industry can and must do more to prevent errors.

Automated Error Prevention; Preventing Errors in Business Systems , WebSphere Journal, July 2003

Explains how to prevent errors in business systems built upon WebSphere.

What Can Be Done about Software Reliability? , Stickyminds.com, May 2003

When an error is found in an application during development, the automated error prevention method helps you correlate that error to a specific point in the development process, and allows you to modify your processes to remove it, and more important, to prevent it from happening again. Preventing errors, rather than chasing them, dramatically improves software reliability. This way, you can stay competitive and not risk your valuable reputation on unforeseen bugs.

Reducing the 80/20 Rule and Increasing Developer Productivity , WebSphere Developer's Journal, April 2003

Explains that developers spend 80% of their time debugging applications and 20% writing new code..and offers tips for achieving a more productive ration of coding to debugging.

Building Solid Software , CIO, August 2002

Other industries have learned to incorporate better production methods into their manufacturing processes to ensure quality in their products why isn't the software industry doing the same?

Bulletproofing Web Applications , December 2001

"Bulletproofing" is a road map for how to integrate error prevention and detection into the development process to ensure that Web applications are robust, scalable, efficient and reliable.