Quality requirements such as security, usability and performance should be defined in the early stage of the software development because they give large effects to the costs and efforts of the following stages. In addition, we have to confirm such quality requirements are correctly considered in the intermediate software artifacts such as design documents to avoid unnecessary redo of work. In this paper, we propose a method for confirming quality requirements considerations in a design document. The method enables software designers to avoid the oversight and the overabundance about the design related to quality requirements. To evaluate the method, we applied the method to several commercial software systems, and confirmed the method worked well.