Lesson 3. Testing requirements

The main thing in the lesson

•

Requirements are any document compiled by the customer and provided to the developer for the implementation of the product. For example, the technical task and the description of the tasks.
•

To understand why you need to test the requirements, it is important to understand the causes of errors, since most of these causes can be cut off at the start.
•

The requirements should be simple and clear to all participants in the process, extremely accurate and should not contradict the moderation of the VKontakte>
•

Requirements can be tested for completeness, uniqueness, consistency, value, feasibility and testability.
•
The main components of the technical task:
- •
  The goal is the main context of the project.
- •
  Success rates are a simple and measurable value.
- •
  Requirements are clear and complete.
- •
  The design and user path is a clear vision of the product.
- •
  Roadmap — the timing and sequence of tasks.
- •
  Technical details.
•

The main goal of testing requirements is to form a common understanding of the concept and technical implementation of the future product, as well as saving time in the future.

:::