Requirements-driven testing: The first step to automation

Requirements-driven testing: The first step to automation Poor requirements lead directly to poor application quality. When business requirements are ambiguous, missing or just plain wrong, it is impossible for testers to confidently build a test plan that truly validates an application's business functionality. Instead, testers are force to "fly blind" and try to guess what the business expects the application to do. The results of this approach are disastrous: IDC research indicates that 70-80% of project failures stem directly from poor business requirements. The approach --called Requirements-driven testing--is specifically designed to address this problem. Requirements-driven testing improves application quality by enabling teams to capture better business requirements and directly leverage them in the testing process.

Managing User Requirements

Pre-Conference Tutorial – a STeP-IN Theme Conference: Usability Testing & Engineering (May 2006)
Muralidhar Koteshwar - Head, Tools and Competency Development, Celstream Technologies.

Well begun is half done – Anonymous.Documenting a clear set of user requirements ensures a good start for a project. It helps project managers estimate better, prevent defects and deliver products that meet customer expectations and helps companies succeed in the competitive marketplace.Identifying the right set of users for a software product, the environment they use it in, setting priorities and then a mechanism to deliver the product that meets user requirements is critical for success in today’s cutthroat market scenario. Product Developers, Designers and Architects focus more on technical aspects and tend to overlook the user perspective. This workshop will help them get this much-needed perspective thus ensuring that their products have a higher acceptance in the marketplace.

Collaborating Testable Requirement Identification with Test Scenario – A step towards Early & Effective Involvement

In present dynamics of time to market, test team role is also evolving. On one side, test team is really expected to play a role of an Analysts who can conceptualize the requirements, derive the correlation with product deployment so that the product evolution can happen during requirement & design phase itself & on other side it also has to ensure testing effectiveness & efficiency by performing optimization at all possible levels especially in outsourcing environment.

In well deployed products with new enhancements getting implemented, understanding the existing functionality without prior knowledge, identifying testable requirements of newly implemented functionality, defining optimize test coverage for regression and feature interaction scenarios is a real challenge.