Add a comment

 

Keep functional and non-functional requirements separate.

I responded to Uncle Bob on his Posterous blog when he posted this opinion. Like you, I define an architecture as that which solves the non-functional requirements, independent of the domain. So I have to disagree when he asserts that the architecture should scream the domain.

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.


Keep functional and non-functional requirements separate.


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

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).