Top-quality software architecture should consider both functional and non-functional aspects of systems and their association. In the the existing literature, considerable efforts have been directed at functional requirement analysis and design, regardless of the non-functional aspects. This disassociation makes architecture comprehension and evolution hard. This paper proposes a strategy on how to elicit non-functional requirements and incorporate them into the design models of functions. We aim at bridging the gap between functionality and non-functionality and constructing high quality software systems.