Books>
Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives
Addison Wesley Search Addison Wesley by Nick Rozanski Eóin Woods Search Nick Rozanski Eóin Woods
Customer Reviews:
A very good companion for system architects
This book will serve the new and experienced architects equally. For new architects, it provides an excellent guide to a fairly contemporary world of systems architecture and helps in looking at it from various "viewpoints" and "perspectives" used by the author. This will help enormously in finding a rationale for choice of methods in any part of architecture you are involved in, be it application, data, infrastructure, security, performance & scalability etc. For the experienced ones, it will help in focussing on a particular area and delve into it in more detail. I found the examples cited to be useful and author's usage of structure UML to illustrate the examples. I would also suggest to read the Bass, Clements' book on Documenting software architecture together with this book.
Every IT architect should read this book
My reason for buying this book was to hear what the authors had to say about handling cross-cutting architectural concerns (such as security), which they refer to as "perspectives". The authors offer refreshing insights into how such concerns should be interwoven with the architecture views/viewpoints with which many architects will already be familiar when documenting their software architectures.
But now that I've finally finished reading the book (500+ pages) I have to say that this book is so much more. This is essentially a "book of 2 halves". The first half discusses fundamental architecture concepts, and various elements of the architecture process. However, the second half of the book is dedicated to a catalog of viewpoints and a catalog of perspectives. These sections are, I think, the most valuable, and offer probably the best overview of different architectural concerns (such as concurrency, deployment, operations, security, availability etc.) I've come across. And the whole book is liberally sprinkled with pragmatic advice, and examples, based on the authors' experiences.
In summary, the book makes a great "handbook" for both novice and experienced architects.
Stop those arguments about what architecture actually is! 
Full disclosure: I used to work with Nick and Eoin in Sybase UK's consulting division. One of the ongoing arguments we would always have was, what exactly architecture, when applied to software systems, actually is. So, finally, I have a book that I can point to and say, the stuff that's in there is a pretty good basis for what architecture is for and more importantly how architects should do it. And (please believe me), these two guys definitely know how to do it.
The book builds on the old 4+1 viewpoints stuff, though Nick and Eoin rename some of them for clarity. They've also introduced one further one to end up with 6 in all. Then they've introduced a new concept - perspectives - that serves as a handle for all the cross-cutting stuff, eg security, i18n and so on. So we have a 2-dimensional space of things to think about.
Of course, it's impossible for any architect to fully explore this space before the building must begin, but in this book the authors help show how to prioritize work best to maximise success.
If there's one thing this book skirts around, it is how architecture fits into agile development processes. But if you are an architect who's always bluffed it, or a developer wanting to move into architecture, then I recommend you buy this book.
Listmania Lists:
IT Books
Top software design books
"Must-read" for any (aspiring) Software Architect
RELATED:
Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives & More...
related blog:
baker
book used in class: http://www.amazon.com/gp/product/0321112296 (if helpful) written assessment in this portion of the assessment we want you to tell us what you have learned by applying the skills and content covered in the ...
http://customwriting123.wordpress.com/2009/03/12/baker/
[本]software systems architecture: working with stakeholders using ...
isbn:0321112296:image ieeeのarchitecture modleを解説?解釈しているようです。買ったような気がするなぁ・・・
http://d.hatena.ne.jp/akon/20060921#1158798621
Em Portugal não são necessários Arquitectos de Software? « José ...
Eoin Woods, software architect, co-author of Software Systems Architecture : Working With Stakeholders Using Viewpoints and Perspectives ISBN:0321112296. “The software architecture of a program or computing system is the structure or ...
http://mdalab.wordpress.com/2007/09/02/em-portugal-nao-sao-necessarios-arquitectos-de-software/
求书：software systems architecture
software systems architecture: working with stakeholders using viewpoints and perspectives (hardcover) product details hardcover: 576 pages publisher: addison-wesley professional (april 30, 2005) language: english isbn-10: 0321112296 ...
http://www.itpub.net/viewthread.php?tid=1102639
[compro] software systems architecture
... senza contare che non è neanche sicuro che il libro rimanga quello. in ogni caso, fatemi sapere. autori nick rozanski e eoin woods titolo software systems architecture editore addison wesley, 2005. isbn 0321112296.
http://forum.studentidia.org/index.php?showtopic=11226
software systems architecture: working with stakeholders using ...
isbn: 0321112296. number of pages: 576. languages: original language: english unknown: english published: english. product description: software systems architecture is a practitioner-oriented guide to designing and implementing ...
http://textbooks-architecture.markettradeathome.com/2009/02/02/software-systems-architecture-working-with-stakeholders-using-viewpoints-and-perspectives/
