This book presents the influence of architecture in the software development process. The interesting aspect of this book is that is it a thoroughly presentation of the architecture role in the software development activities, not only at initial analytic stage but also at the subsequent tasks like software testing or configuration management. The book is very well structured and is certainly an excellent text book for students or for developers that are interested in getting an extensive presentation of software architecture. What I missed in the book is the presence of more “real life user stories” examples that could relate the different topics presented in the book. There is a case study used to implementing the practices, but it remains abstract to me. People looking to have more insight of what is “enough architecture” will not find some ideas on how to get the answer in this book.
Website of the book: http://www.processofsoftwarearchitecting.com/
Reference: “The Process of Software Architecting”, Peter Eeles and Peter Cripps, Addison-Wesley, 405 pages,
Get more details on this book or buy it on amazon.com
Get more details on this book or buy it on amazon.co.uk
I am really surprised that the book gets that positive comments. Not only here but also at some ohter places. I am reading it at the moment. I’ve read the first five chapters now, so the rest of the book might be better, but thát good? The first 100 pages of the book all full of vague definitions, which are on the one hand ‘open doors’, like things that are already known to all who know software development, on the other hand still to abstract to be useful. Now I am hoping that the case studies starting from page 100 are more interesting, but I am not screaming from the roof how good this book is now.