ISO 2500 SQ quality definition goes as follows and I really do not understand the note with regards to ISO 9000:
capability of software product to satisfy stated and implied needs when used under specified conditions
Note 1 to entry: This definition differs from the ISO 9000:2005 quality definition mainly because the software quality definition refers to the satisfaction of stated and implied needs, while the ISO 9000 quality definition refers to the satisfaction of requirements.
I do not get it, because requirement itself is (in the same standard) defined as stated, generally implied or obligatory need or expectation. Therefore, if requirement is a need that might be implied, isnt both definitions the same? ISO 9000 reads the same except that instead of needs it reads requirements. But again, if requirements subsume needs (as stated in their definition), how these are different?
EDIT: I believe I got it - the main difference is that requirements are already translated needs that might have been misunderstood or captured incorrectly, while needs are in general abstract "wants" that users can assess while using the software. So physical products basically conform to certain set of requirements while software validation is more about perception and actual fitness for purpose from the user needs perspective.