Projects sometimes happen to deliver a product that meets every requirement specified but ultimately appears not to address important needs of the stakeholders. Certainly there are many possible causes for that. In this Advisor, I focus on one cause that I believe is not always properly understood -- partly because of the flawed notion of quality of IS systems. The problem I will address is that of requirements quality and responsibility for requirement analysis in the context of IS procurement.