Knowing the requirements for a system means understanding the problem to be solved. If the problem isn't understood, the solution can't address it. Not taking time for requirements discovery at the beginning will cost far more time and money in the end. This paper explains requirements gathering techniques.

This paper discusses implementing METS (Minimal Essential Testing Strategy) for your test team. METS is a strategy to help get the essential testing for your project done within the time frame allowed. Step by step instructions for using this methodology are included.

In this article, the author discusses how to deliver more function, in less time, and with fewer resources while maintaining a high level of quality. He details how poorly written requirements can lead to major system errors. This paper also explains why good requirements are a critical part of any successful project.

Use cases are an industry-standard method of specifying user interaction with the system, and hence have become part of the requirements definition phase of many software projects. They're used to derive, construct, and validate interfaces, classes, relationships, and processes in an application. This session introduces participants to a testing methodology called, use case path analysis. This technique has proven to be an extremely powerful way to create accurate, realistic test cases based on the use cases. Usable in any environment, with any tool set, use case path analysis not only saves time and money, it also helps you to control risk.