Features
- Cover Type: Paperback with 336 pages
- Published by: Wiley
- Edition: 1st Edition March 28, 2003
- Written in: English
- ISBN 10 Number: 0471228869
- ISBN 13 Number: 978-0471228868
-
Book Dimensions:
9.1 x 7.4 x 0.9 inches
- Weighs: 1.3 pounds
Reader Reviews
Ever since "The Mythical Man-Month", it has been clear that lack of strong architecture will sink a software project. (It was probably true before TMMM, but that was before my time.) Architecture, implying an architect, is a requirement for any major piece of software. I can agree with Albin only to a point: architecture is not implementation, analysis, or software engineering. It's different even from "design", as the word is usually used. An architect really does a different job than other members of a software team (but the architect may design and implement, also). That said, I didn't quite make out how to go about - - training someone as a software architect, - developing a sound and appropriate architecture, - measuring its success in objective and repeatable ways, - making it a part of the project plan and documentation, or - preserving it across generations of maintenance. Most importantly, I did not see any discussion of adapting an existing architecture to new needs, or of extending an archtecture beyond its original bounds. Typical software spends 10% of it's life in design and implementation, and 90% in maintenance. The initial 10% is the fun part. I have real reservations about authors who choose not to discuss the other 90% of the problem. The book has value to the extent that it opens the topic for discussion. Too often, though, it confuses the skill of architecture with the tools of an architect - sort of like looking at a pencil drawing by Rembrandt and saying "Wow, if I get a pencil like his, I'll be able to draw like that too." I've been looking for books and articles about software architecture. This one has some value, but I'm still looking.
Comment | |
(Report this)
Search for books at
