- The requirement phase that development groups skip most often, and the results
- Proactive test design best practices teams could use to catch and define requirements early in the development process
- The requirements phases that are best handled using automated tools
- The pros and cons of using use cases to define requirements
You must have Adobe Flash Player 7 or above to view this content.See https://www.adobe.com/products/flashplayer to download now.
Download for later:
• Internet Explorer: Right Click > Save Target As
• Firefox: Right Click > Save Link As
Robin F. Goldsmith, JD, has been president of Go Pro Management Inc. consultancy since 1982. He works directly with and trains business and systems professionals in requirements analysis, quality and testing, software acquisition, project management and leadership, metrics, and process improvement. He partners with ProveIT.net in providing ROI Value Modeling tools, training, and advisory services.
Looking for more expert advice on determining requirements for software projects? Robin Goldsmith can answer your questions via SeachSoftwareQuality.com's Ask the Expert, and you can read his answers to other software pros' requirements questions, too.