Determining Test Cases from a Requirements Definition Plan
Determining the scope, resources and effort required to test software is dependent on a set of requirements. These requirements, most often specified in a requirements definition plan, describes in detail the full functionality planned for the system. Because test cases are derived from these requirements, the plan must be written in a manner that is both specific and testable.
A requirements plan is also used by the software development team to identify the required features and functionality. Within agile, a requirements plan may be replaced by user stories, which are reviewed by both development and QA early in the product’s design phase and at the beginning of each sprint. This common understanding of requirements by your QA and development teams leads to a more successful and speedier development and test cycle.
Find out more about integrating a requirements plan or user stories into your test process by clicking on the image to the right. You’ll receive a FREE copy of the guide Fundamentals of Quality Assurance!