|
|
Beyond Software Architecture: Creating and Sustaining Winning Solutions (Addison-Wesley Signature Series)
|
List Price:
$49.99
Buy Softwares Price:
$41.00
Your Savings: $ 8.99 ( 18% )
Subject To Change Without Notice
Availability: Usually ships in 24 hours
Manufacturer: Addison-Wesley Professional
|
Average Customer Rating:  
|
|
Binding: Paperback
Dewey Decimal Number: 005.1
EAN: 9780201775945
ISBN: 0201775948
Label: Addison-Wesley Professional
Manufacturer: Addison-Wesley Professional
Number Of Items: 1
Number Of Pages: 352
Publication Date: 2003-02-09
Publisher: Addison-Wesley Professional
Studio: Addison-Wesley Professional
|
|
|
|
|
|
Editorial Reviews:
|
Provides the software engineering community with a clearer understanding of the business value of software architecture. Helps technologists grasp the business ramifications of their decisions, and provides business-oriented software professionals with better knowledge of how robust software can be built and maintained. Softcover.
|
|
|
Spotlight customer reviews:
|
Customer Rating:
Summary: Useful book for Software Product Management
Comment: I'm not the kind of person who burns through business books or even likes reading them at all. I do, however, actively pursue information that will help me do my job better and more efficiently, which presents a bit of a problem when the information I need is stuck in a book somewhere. That's one of the reasons I like this book.
Being fairly new to software product management, I've read a couple of books on the topic but they all seem to be very far removed from what I actually do every day. Hohmann's book is different; it actually contains information about things that I find myself making decisions about every day. It's also written in such a way that I can jump to whichever chapter covers what I'm mulling over that day, like pricing or licensing third party technologies, without feeling like I've lost context. In almost every case, he writes about topics that I'm familiar with but covers them in more breadth than I've been able to have personal experience with. I've already found myself referencing the book to help in either my own day-to-day activity or when someone else asks for my advice. Hohmann sort of treats the reader like you're smart enough to go off and make your own decisions if he just outlines your options and potential pitfalls, which is nice because that sort of how I think of myself too.
Overall, he presents a very practical mix of marketing and technical information that I've found very useful as a software product manager.
Customer Rating: 
Summary: News you can use, but a bit annoying
Comment: Hohmann presents a fair amount of useful folk wisdom on enterprise software architecture. IMHO, this information is useful enough to try to struggle beyond the annoyances that Hohmann needlessly creates: (a) inventing annoying buzzwords like "tarchitecture" and misusing perjorative slang like "marketecture" (synonym: vaporware); (b) politocorrectoid smarm (all people in positions of responsibility are "she" and all low-level drones are "he"); and (c) Hohmann's very high opinion of himself.
I wish this book was on softcopy so that I could edit this stuff out. I'd have had an easier time reading it. As it is, I've had to take the book in small doses.
Customer Rating:
Summary: Reinventing the wheel
Comment: I had great hopes for this book, but for any industry veteran it is basically a repackaging of what many other "experts" have written before. The book is needlessly verbose, but yet glosses over key points with literary hand waving. The lack of significant examples, business cases, and real world process development gives one the feeling the book is merely the presentation of a thesis or philosophy devoid of concrete real world application.
For someone just starting out in the industry they may glean some basic concepts, but there are so many more publications that do a better job and do it cleaner.
Customer Rating:
Summary: Very unique, yet not gripping
Comment: One of the first things authors are asked by their agents, editors, or prospective publishers is to present an analysis of the other books in the genre that cover the same material as their books. Here, Luke must have had it very easy. He addresses a truly unique market niche (the interaction between technical architecture and marketing) in a way that really no one has done before or attempted to do since.
A book that handles both market segmentation and software product management in 300 odd pages is going to cover a whole lot of real estate and risks spreading the information pretty thin. Things important to folks in product management are not always the same things that are interesting to marketers. This facet of writing a book, target audience identification, is also frequently the subject of discussion with editors and publishes. Not having a clear target audience is where this book comes up a bit short.
Luke attempts to address such a breadth of software product concerns that it's hard for any one target group (technical architects or marketers) to get really interested. Although this book might be good for an entrepreneur or someone new to the field of software product management, it is, at best, a catalog of knowledge for tarchitects and marchitects and is unlikely to include anything that they haven't stumbled across in the field. A number of my colleagues have agreed with my final assessment that this is an easy book to peruse and become familiar with, yet a tough book to dive into and love.
Customer Rating:
Summary: AND?
Comment: Perhaps I'm missing something, but it seems that while this book might provide a nice skeleton for managers straddling the line between development (techitecture) and business strategy (marketecture), the meat is simply not present. So many opportunities for REAL examples went either unaddressed completely, or worse, were answered with meaningless little 2-paragraph sidebars filled with sentences like, "then we sat down to talk about things and we decided to approach things from a different angle, blah, blah, blah." Thanks. I can't say this book was a complete waste of time but it certainly wasn't the best use of my time, either, sadly. And the coining of these ridiculous terms like "techitecture" were truly hard to take.
|
|
|
|
|
|
|
|
