🔍Phase 2: Requirement Analysis

Requirements analysis is the crucial phase where the project team works to understand the needs and objectives of the product in order to define detailed requirements.

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.

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

Specific

Requirements are clear, detailed, and targeted. No ambiguity.

• Avoids vague language like "easy to use"

• Uses specific, concrete terms

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

Attainable

Requirements can realistically be implemented.

• Feasible with given resources and constraints

• Aligns with project scope and goals

Relevant

Requirements serve an actual purpose for stakeholders.

• Directly tied to user needs and business objectives

• Adds value for stakeholders

Time-bound

Requirements have clear deadlines.

• Includes target completion dates

• Deliverables are specified

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

✔️Specific and detailed

✔️Measurable and testable

✔️Attainable and realistic

✔️Relevant to stakeholders' needs

✔️Timelines

The SMART principles help guide writing requirements that inform design, development, and testing activities in an objective, measurable way.