I see things quite differently. Functional requirements change frequently. Non-functional requirements change infrequently. To be agile enough to respond to business changes, we can't let the architecture depend upon the domain. I lay out my argument in Keep functional and non-functional requirements separate.
E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).