What is the difference between the requirements of the solution and the needs of the user?

Sev­en years ago (2015), I ended an art­icle about require­ments and trace­ab­il­ity with the words: So the busi­ness require­ments may be dozens. The required sys­tem ser­vices (use cases) in a large pro­ject may also be dozens. But hun­dreds or thou­sands of ?require­ments? is an expres­sion of los­ing con­trol of the pro­ject scope? Here I would like to point out that a require­ment (a sys­tem ser­vice) could be, for example, a VAT invoice pro­duced in com­pli­ance with the reg­u­la­tions. The fea­tures of this invoice (list of fields) are not sep­ar­ate require­ments, they are fea­tures (para­met­ers, attrib­utes) of a single require­ment. No fea­ture of the VAT invoice has any value on its own so it can­not be a sep­ar­ate use case, just as our require­ment can be a car but its col­our or auto­mat­ic trans­mis­sion are fea­tures of the car, it makes no sense to require ?red col­our? without expect­ing a car (and how to jus­ti­fy that this col­our sup­ports the busi­ness object­ive). The use case for a car is the jour­ney and not the inser­tion of the key into the igni­tion, because this is just one ele­ment of the scen­ario of start­ing a car journey.Source: Why is require­ments tra­cing import­ant in a pro­ject? – Jarosław Żeliński IT-Con­sult­ingThere are pub­lic­a­tions about require­ments, their man­age­ment and imple­ment­a­tion. There are applic­a­tions avail­able on the mar­ket to col­lect them and man­age such a col­lec­tion. And we are con­stantly con­fron­ted with their – require­ments – ambi­gu­ity (Šen­kýř & Kroha, 2019). It turns out that their import­ance becomes cru­cial for pro­jects, also from a leg­al per­spect­ive (PZP and the concept of need defined in the recom­mend­a­tions of the Pub­lic Pro­cure­ment Office). This time I will focus on the con­cepts of «require­ment» and «need» in rela­tion to the solu­tion design.

Source: What is the dif­fer­ence between solu­tion require­ments and user needs? – Jarosław Żeliński IT-Con­sult­ing.