Thomas E. MurphyAs part of our research for the Integrated Quality Suites Magic Quadrant we have been looking at how people spend time in testing, the types of development processes and team structures used and I thought I would share one slice of that here. We ask what types of tools are being used for capturing various types of requirements.
As can be seen, the survey participants generally rely on generic tools more than application specific requirements tools. While there has been solid growth in the variety of tools and vendors in the market adoption still lags behind other tool categories in the SDLC. This while we still see in Capers Jones’ latest software quality report that Requirements are the largest source of Delivered Defects in an average organization with a rate of 0.23 per function point. The real question is what holds us back? Cost of tools? Usability of tools? We think somehow we are doing better? Maybe it is time for a change.
Category: ALM Quality Requirements Tags:
1 response so far ↓
1 Robin Goldsmith December 6, 2012 at 7:31 pm
No doubt a major reason requirements management tool adoption lags is because the far bigger issue with requirements is content, which these tools don’t really help with. Yes, these tools do help track and control changes to requirements; but most changes are due to the requirements not being right in the first place, which in turn is largely due to mistaken models.
Robin F. Goldsmith, Author of Discovering REAL Business Requirements for Software Project Success
Leave a Comment