- Taschenbuch: 346 Seiten
- Verlag: Addison-Wesley Professional; Auflage: 01 (30. Januar 2003)
- Sprache: Englisch
- ISBN-10: 0201775948
- ISBN-13: 978-0201775945
- Größe und/oder Gewicht: 18,3 x 2,5 x 23,1 cm
- Durchschnittliche Kundenbewertung: 2 Kundenrezensionen
- Amazon Bestseller-Rang: Nr. 64.290 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
- Komplettes Inhaltsverzeichnis ansehen
Beyond Software Architecture: Creating and Sustaining Winning Solutions (Addison-Wesley Signature) (Englisch) Taschenbuch – 30. Januar 2003
|Neu ab||Gebraucht ab|
Wird oft zusammen gekauft
Kunden, die diesen Artikel gekauft haben, kauften auch
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Wenn Sie dieses Produkt verkaufen, möchten Sie über Seller Support Updates vorschlagen?
Praise for Beyond Software Architecture "Luke Hohmann is that rare software technologist who views software development from the viewpoint of the end user. He passionately believes that one hour spent with an end user is worth many hours making software architectural choices or days documenting perceived user requirements. Most of what is written about software development focuses on methods used to design and develop robust software. Luke's latest effort, Beyond Software Architecture, illuminates the more mundane aspects of creating true business solutions by supporting the user throughout the lifecycle of the software product. By concerning himself with creating business value, Luke tightens the connection between a software application and the business function it performs." Bruce Bourbon General Partner, Telos Venture Partners ~"There are two kinds of people that read the Dilbert comic strip: folks that take a moment to marvel at how accurately it reflects life at their company before moving on to the next comic strip, and folks that think Dilbert is an amusing reminder that high tech companies can and should be better than Dilbert's world. Anyone in the first group should stick to reading comics. This book is for people in the latter group." - Tony Navarrete Vice President, Diamondhead Ventures ~"Luke brings a proven methodology to the challenge of software development. In Beyond Software Architecture, Luke provides practical and proven techniques that all development executives can employ to improve the productivity of their software organization." - G. Bradford Solso CEO, Taviz Technology ~"Beyond Software Architecture is the first book I have read which contains an insider's perspective of both the business and technical facets of software architecture. This is a great book to get marketers and software managers on the same page!" Damon Schechter CEO, LOC Global author of Delivering the Goods ~"There are books on technical architecture and books on product marketing, but few, if any, on how architecture and marketing information must be integrated for world class product development. Beyond Software Architecture provides this valuable bridge between technology and marketing it explains how to deliver quality products that are profitable in the marketplace." Jim Highsmith Director, Cutter Consortium author of Adaptive Software Development ~"Product development managers, marketing managers, architects, and technical leads from all functions should read this book. You'll see a pragmatic view of how to define and use a product architecture throughout a project's lifecycle and a product's lifetime." Johanna Rothman Rothman Consulting Group, Inc. ~"Luke Hohmann has captured the essence of product creation in his latest book. He cleverly discusses the need for both the marketing and engineering roles in product creation and ties the two together building a good foundation for understanding and executing successful product creation." Lee Sigler Principal, 360 Market View, Inc. ~"Finally a book that deals with those often ignored but critical operational issues like licensing, deployment, installation, configuration and support. Beyond Software Architecture is the "What they don't teach you at Harvard Business School" book for anyone who develops software products or buys them." Mary Poppendieck Managing Director, Agile Alliance President, Poppendieck LLC ~"Luke Hohmann delivers a passionate, articulate wake-up call to software architects: it ain't just technical any more! Technical architectures have profound business ramifications, and ignoring the business ramifications of portability, usability, configuration, upgrade and release management, security, and other architectural choices can not only lead to project failures, but ultimately to nasty lawsuits from disappointed customers. Beyond Software Architecture is a must-read for successful software product managers!" Ed Yourdon Author of numerous books and articles on software development ~"Beyond Software Architecture is not just for software engineering professionals! Executives and product managers will find that the book provides the necessary background to make informed decisions about the software that their companies build. I have found that the book is a useful tool for building consensus between management and engineering, because it discusses business and customer-related issues without delving too deeply into implementation details." David Chaiken Vice President Systems Architecture AgileTV Corporation
At last, a book that provides the software engineering community with a clearer understanding of the business value of software architecture. There are currently a significant number of books on creating, documenting, and implementing software architecture, but precious few resources have addressed how to build a software architecture that aligns with a customer's overall business goals. In this new book, Luke Hohmann borrows from his extensive experience managing successful enterprise software projects to provide practical wisdom on creating and sustaining winning software solutions. This book helps technologists grasp the business ramifications of their decisions, and provides business-oriented software professionals (e.g. sales people and marketers) with better knowledge of how robust software can be built and maintained.Alle Produktbeschreibungen
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
Es geht in dem Buch um alle die Dinge, die Entwicklungsmanager beachten müssen, die Software-Produkte für den Massenmarkt bauen und um die Wechselwirkung der durch dieses Geschäft bedingten Einflussfaktoren mit der Software-Architektur. Themen sind auch Produktmarketing, Technologiekurven oder Lizenmodelle.
Richtig technisch tief wird das Buch selten - aber dafür werden relevante Themen genannt und aufgezählt. Beispiel: das Thema Configuration wird auf 8 Seiten abgedeckt. Dazu allein gibt es ganze Bücher. Genauso Upgrades - 9 Seiten: da wollte ich immer mal wissen, wie Microsoft seine Patches baut - erfährt man aber auch nicht ... dafür aber mehr über Produktmarketing.
Nützlichkeit nach Zielgruppe:
* für Entwickler von Individualsoftware - nur zur Horizonterweiterung
* für Architekten von Produkten - eher das WAS, nicht das wie
* Techniker - werden enttäuscht sein. Das Buch ist praktisch codefrei
Und muss sagen, dass ich nicht enttäuscht wurde, es behandelt wichtige Punkte mit denen man im technischen Produktmanagement bzw. als PL/Architekt/Team Lead/Entwickler der auch mit den leider of vernachläßigten Business Qualities und operativen Attributen in der Realität konfrontiert wird.
Themen wie Versionierungs-Schemata (Patches, Maintenance bzw. Service Releases etc.), das Leid mit sich ändernden Marketing-Namen, Branding, Setup/Installation, Updates und das unglücklicherweise weit verbreitete Resume Driven Design werden meines Erachtens nach äußerst gelungen behandelt und decken sich mit meiner Erfahrung in der Entwicklung von Standardsoftware.
Ergo kann das nur für technische Produktmanager/Projektleiter und Seniors empfehlen, da es kompakt die wichtigsten Erfahrungen die man in der Praxis macht wiedergibt, ohne jeden Aspekt selbst durchlebt haben zu müssen und sich somit viel Schmerz erparen kann ;-).
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta) (Kann Kundenrezensionen aus dem "Early Reviewer Rewards"-Programm beinhalten)
Luke does a fabulous job of going beyond the many books written on software and technology and beyond the many books, classes, and seminars addressing how to create a successful startup and get funded.
Hohmann's keen insight and practical advice can make an enormous difference for any group of bright and knowledgeable software engineers and/or visionary entrepreneurs with the "killer" application - a difference that can mean success. He clearly defines the space between the technology and the market and draws them together so that technologist and business person alike can gain a necessary understanding for what it takes to bring to market and sustain a successful software product.
I wish that this book had been available ten years ago and that I had read it!
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.
I also feel it's written in a style that comes across as arrogant. It's seems like it's exactly what he says one should avoid - well, other people apparently. No wonder it got such good reviews from people high up in the management chain ... I think I should look for a book that software engineers like, rather than CEO's. I also found it cringe worthy that he quoted some software engineer wanting to send 650MB files as e-mail attachments. I don't know what illustration such an extreme example served other than to frame someone else as ridiculous.
Here is one thing I really hate this book for, though: the casual mentioning of a phase in the software development plan for letting engineers "catch up on missed sleep". Luke, FFS, if your project planning was so good, why do you need to drain people's sleep reserves? Is that conducive to the software quality you emphasize in your book?? Is that conducive to the quality of life of your engineers? Yes, I know all those tropes about committed engineers and how proud people feel when they have worked through the night just to make it for code complete the next day. I have proudly followed along that model for many years at Microsoft. To impose that on people or assume it to be normal is just so unbelievably arrogant! Your software project is so important?! Well, guess what: people's time with their family is important, too. And just because your estimates are not good enough that people do not have to work through the night does not mean people are not committed or you are not creating a "winning solution". Engineers are not just drones there to create revenue for people like you while you pretend to be "one of them" and to be "fighting along in the trenches". If you are okay to lose sleep over a badly thought out project plan, that's your decision - don't make that decision for other people.
It never seems like he takes a very broad view and explains why he chooses his approach over the alternatives. It always sounds like "Look, I have all this vast experience and this just happens to work best. Yeah, for other people other things work alright, but I'm not going to explain those other ways, 'cause I know mine work." It's very prescriptive. As a software engineer I don't just want to follow - I want to think along.
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.