Couple of things that you can answer for me on the architecture frame.
Page 79: Quality Attributes: Why is this not aligned with the Qualities of Service that MSF pushes? They look more complete as they properly decouple the overloaded term "Performance", for us is all about responsivenss, concurrency and efficiency.
Some customers are trying to push the MSF and this document looks a bit different in this area.
Chapter 3, Architecture frame: it is good to present the frame here but after a couple of pages you start describing the considerations. This considerations are not general enough, some of them apply to the different layers. indeed, on each layer on part III
you repeat some of these entries, looks confussing and repeatitive.
Page 61: Communication: you are stating to use unmanaged code for communications across AppDomain Boundaries, I don't get it, why unmanaged?
Page 61: Composition: the document state that we should avoid dynamic layouts, but there is a technology called Dynamic data released in .NET 3.5 SP1 that promotes this.
I will continue reading and post more comments.