Interesting post by Uncle Bob on software architectures and what they should or should not be: http://blog.8thlight.com/uncle-bob/2011/09/30/Screaming-Architecture.html
Although I'm a "fan" of Robert Martin, I don't completely agree with him on this one: an architecture doesn't have any value on a piece of paper, or on a slide or in the thin air. Architectures need to be materialized at some point and for that it's hard nowadays to avoid using frameworks or hardware topologies for that matter.
I'm not saying a framework should be the architecture, but unless you reinvent the wheel each time, you might find an architecture having to be tailored in certain areas so that "it fits". I just don't think you can define and document the architecture without thinking how that architecture is going to be implemented.