Quality requirements, that form a major sub-category of requirements, define a broad set system-wide attributes such as security, performance, usability and scalability. Unfortunately, many organizations pay less attention to quality requirements & assume that the necessary qualities are implicitly understood & will naturally emerge as the product is developed.
In this paper, we would try to address important questions related to role of quality requirements in the software development lifecycle, and techniques for managing them effectively. Also, we would find out as to what happens when requirements are not managed? and suggest some practices to write quality requirements. The purpose is to make the community specifying the requirements understand requirements defects that have been made in the past. Hopefully, it also helps to avoid similar mistakes in the future.