The software system’s quality hinges on meeting specified requirements, ensuring customers’ satisfaction. Inadequate requirements engineering leads to system issues and higher maintenance costs. Project failures often stem from mishandling non-functional requirements (NFRs) throughout the project life cycle. This paper conducts a systematic literature review (SLR) on integrating NFRs in model-driven software development (MDSD). Utilizing seven scholarly databases, Google Scholar, and Google, 1,605 records were screened, with only 7 studies meeting inclusion criteria. The review shows that the UML profiles have been largely solicited to extend existing models with annotations describing non-functional properties or NFRs specified using other methods such as NFR framework, MARTE, etc. Aspects-Oriented concept has also been used to describe NFRs considered, for instance, as crosscutting concerns for software services.