1

I understand the difference between functional and non functional requirements.

  • What I never understood is, why do we make this differentiation?

  • (Rephrased) When I design a solution, why is it useful to distinguish between these two?

PKL
  • 95
  • 7
  • It's just a way to structure and organize the requirements. You don't need to follow it if you have another good structure. – Codo May 16 '22 at 11:12
  • Maybe, but it is such a widespread approach, I kinda expect there to be a really good reason why we use exactly this method. – PKL May 16 '22 at 11:15
  • 2
    Non-functional requirements are often forgotten. So there's an emphasis on them. It's less about the differentiation and more about ensuring that non-functional requirements are not forgotten. – Codo May 16 '22 at 11:24

1 Answers1

1

They are usually raised by different stakeholders. The quality attributes (what you called non-functionals) are mostly raised by the technology people and are somehow assumed by business owners

Arnon Rotem-Gal-Oz
  • 25,469
  • 3
  • 45
  • 68