> For the complete documentation index, see [llms.txt](https://qatesting.gitbook.io/qa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://qatesting.gitbook.io/qa/manual-testing/sdlc/phase-2-requirement-analysis.md).

# Phase 2: Requirement Analysis

Requirements analysis is the crucial phase where the project team works to <mark style="background-color:yellow;">understand the needs and objectives of the product in order to define detailed requirements.</mark>

{% hint style="info" %}
Careful requirements analysis helps ensure the development team builds the right product that solves the right customer problems. It provides the necessary level of detail to estimate timelines, complexity, and resources needed for development.
{% endhint %}

## What are the properties of a good requirement according to the SMART principles?

{% tabs %}
{% tab title="Specific" %}
Requirements are clear, detailed, and targeted. No ambiguity.

* Avoids vague language like "easy to use"
* Uses specific, concrete terms
  {% endtab %}

{% tab title="Measurable" %}
Requirements can be quantitatively measured and tested.

* Specified in measurable terms (e.g. response time must be less than 2 seconds) • Includes explicit pass/fail criteria
  {% endtab %}

{% tab title="Attainable" %}
Requirements can realistically be implemented.

* Feasible with given resources and constraints
* Aligns with project scope and goals
  {% endtab %}

{% tab title="Relevant" %}
Requirements serve an actual purpose for stakeholders.

* Directly tied to user needs and business objectives
* Adds value for stakeholders
  {% endtab %}

{% tab title="Time-bound" %}
Requirements have clear deadlines.

* Includes target completion dates
* Deliverables are specified
  {% endtab %}
  {% endtabs %}

In summary, good requirements follow the **SMART** principles by being:

✔️**S**pecific and detailed&#x20;

✔️**M**easurable and testable&#x20;

✔️**A**ttainable and realistic&#x20;

✔️**R**elevant to stakeholders' needs&#x20;

✔️**T**imelines

{% hint style="info" %}
The **SMART** principles help guide writing requirements that inform design, development, and testing activities in an objective, measurable way.
{% endhint %}