Requirements Based Testing
Executive Guide to Business and Software Requirements
By: Keith Ellis
This paper is designed as an executive briefing on the issues surrounding getting business and software requirements right. The white paper is structured so that each page is its own 'mini-white-paper' but each is also part of a total look at better structuring requirements documents, processes and content completeness.
Click here to view a list of IAG Consulting's Whitepapers
The Requirements Networking Group: A review of the past year’s articles
The Requirements Networking Group (RQNG) is celebrating its fourth birthday. In that time it has grown to be an important forum for the requirements engineering practice and a valuable resource for its members. I am excited about what the future holds in store for RQNG.
As we enter our fifth year of operation I’d like to take the opportunity to revisit the past year’s articles. (I promised myself I would not let another three years go by until the next retrospective!) Our article contributors have provided us with some great content and it’s definitely worth a second (or third) look.
A lifecycle approach to systems quality: because you can’t test in quality at the end
Markets are continually demanding smarter products and systems, which in turn leads to more complexity in those products and systems. Whilst advanced functionality is an important competitive differentiator, quality has become part of the ‘price of entry’ to the marketplace. Quality isn’t an attribute that can be tested into products at the end of the development lifecycle, it's a guiding principle that drives all stages of the lifecycle from concept through analysis, design, deployment and acceptance, then through service and finally end-of-life retirement. The management of quality must therefore take account of all key systems engineering disciplines, including requirements engineering, systems design and testing, and change and configuration management.
