Beyond Software Architecture: Creating and Sustaining Win... und über 1,5 Millionen weitere Bücher verfügbar für Amazon Kindle. Erfahren Sie mehr
EUR 48,67
  • Alle Preisangaben inkl. MwSt.
Gewöhnlich versandfertig in 4 bis 7 Wochen.
Verkauf und Versand durch Amazon.
Geschenkverpackung verfügbar.
Menge:1
Beyond Software Architect... ist in Ihrem Einkaufwagen hinzugefügt worden
Ihren Artikel jetzt
eintauschen und
EUR 7,25 Gutschein erhalten.
Möchten Sie verkaufen?
Zur Rückseite klappen Zur Vorderseite klappen
Anhören Wird wiedergegeben... Angehalten   Sie hören eine Probe der Audible-Audioausgabe.
Weitere Informationen
Dieses Bild anzeigen

Beyond Software Architecture: Creating and Sustaining Winning Solutions (Addison-Wesley Signature) (Englisch) Taschenbuch – 30. Januar 2003


Alle 2 Formate und Ausgaben anzeigen Andere Formate und Ausgaben ausblenden
Amazon-Preis Neu ab Gebraucht ab
Kindle Edition
"Bitte wiederholen"
Taschenbuch
"Bitte wiederholen"
EUR 48,67
EUR 39,88 EUR 29,78
11 neu ab EUR 39,88 6 gebraucht ab EUR 29,78

Wird oft zusammen gekauft

Beyond Software Architecture: Creating and Sustaining Winning Solutions (Addison-Wesley Signature) + Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions
Preis für beide: EUR 91,62

Einer der beiden Artikel ist schneller versandfertig.

Die ausgewählten Artikel zusammen kaufen

Kunden, die diesen Artikel gekauft haben, kauften auch

Jeder kann Kindle Bücher lesen — selbst ohne ein Kindle-Gerät — mit der KOSTENFREIEN Kindle App für Smartphones, Tablets und Computer.


Produktinformation

  • Taschenbuch: 352 Seiten
  • Verlag: Addison Wesley Pub Co Inc (30. Januar 2003)
  • Sprache: Englisch
  • ISBN-10: 0201775948
  • ISBN-13: 978-0201775945
  • Größe und/oder Gewicht: 18,5 x 1,8 x 22,9 cm
  • Durchschnittliche Kundenbewertung: 4.0 von 5 Sternen  Alle Rezensionen anzeigen (2 Kundenrezensionen)
  • Amazon Bestseller-Rang: Nr. 118.225 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
  • Komplettes Inhaltsverzeichnis ansehen

Mehr über den Autor

Entdecken Sie Bücher, lesen Sie über Autoren und mehr

Produktbeschreibungen

Pressestimmen

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

Synopsis

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.

Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?


In diesem Buch (Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Hier reinlesen und suchen:

Kundenrezensionen

4.0 von 5 Sternen
5 Sterne
0
4 Sterne
2
3 Sterne
0
2 Sterne
0
1 Sterne
0
Beide Kundenrezensionen anzeigen
Sagen Sie Ihre Meinung zu diesem Artikel

Die hilfreichsten Kundenrezensionen

31 von 31 Kunden fanden die folgende Rezension hilfreich Von Wolfgang Keller am 3. März 2004
Format: Taschenbuch Verifizierter Kauf
ich hatte das Buch gekauft, weil mir der Titel suggeriert hatte, dass es da "um das nächste große Ding" nach Software-Architektur gehen würde. Es geht aber um Software-Architektur für Software-Produkte. Entwicklern von Individualsoftware, wie ich einer bin, wird das Buch also rein für den Job nicht viel bringen.
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
Kommentar War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback. Wenn diese Rezension unangemessen ist, informieren Sie uns bitte darüber.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen
Format: Taschenbuch
Ich habe mir das Buch gekauft, da ich aufgrund der vorhergehenden Rezension wusste, dass sich dieses Buch eben nicht mit den klassischen Architektur-Aspekten beschäftigt.

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 ;-).
Kommentar War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback. Wenn diese Rezension unangemessen ist, informieren Sie uns bitte darüber.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen

Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)

Amazon.com: 29 Rezensionen
31 von 33 Kunden fanden die folgende Rezension hilfreich
Depicts the Development Process in its fullness 8. Dezember 2003
Von Amazon Customer - Veröffentlicht auf Amazon.com
Format: Taschenbuch
There must be hundreds of books on the software developmental process, but I have yet to see a book that covers the business, technical marketing, sales cycle, deployment cycle, release cycle, licensing, installation, upgrade cycle, and everything in the middle all in one compact book. This book TRULY covers the life of a software application and everyone involved in it.
For us techies, this book starts with what we are familiar with: "Why software architecture matters?" The author starts with a general overview of the topic, but it goes much further into the non-technical details software architecture, such as the Social Structure aspect:
"A good architecture works for the team that created it. It leverages strengths and can, at times, minimize their weaknesses. ... Once created, the architecture in turn exhibits a strong influence on the team. No matter what language you've chosen, you have to mold the development team around it because it affects such as things as your hiring and training policies."
New comers to the architect world don't really think about such aspects, or at least it's not really high on priority on many people's lists. The author puts such things right next to profitability, stability of the architecture, and defining the technical boundaries. Granted that Social Structure aspect of the architecture is as important as the others, you can't really find many books out there that treat it as such. Personal experience teaches us that, but there are cases, many cases, that one doesn't have the luxury of "trial and error". The author takes great pride in his experience and has written this book like a personal assistance to a newbie to the job, and to the expert architect with topics such as branding issues, licensing affects on the overall architecture and more...
Tarchitecture and Markitecture are two words/concepts that are used frequently throughout this book. The author starts with the inception of software applications and explains the important rule that Market Architecture (Markitecture) and Product Management have in the overall picture of a software lifecycle. Why Business plan is important and how it should be written, how to release version 1.0 and subsequent versions, how customer input and interaction with the markitects play the most important rule in the subsequent releases of your software, and other such important questions are covered in chapters 2 and 3.
The chapter Software License and Licensing models is probably one of the most valuable chapter (chapter 4) in the entire book. The author describes the concept of licensing and how it fits into the overall architecture and how it affects the architecture very elegantly. Various licensing models and their pros and cons are described:
· Time based
· Transaction based
· OEM bases
· Metering style
· Hardware based
· Services based
· Revenue Obtained/Costs saved.
The author explains why it is important to select the right licensing model, and how and why it could have a negative effect on your architecture if the wrong one is chosen. Various options for choosing a model are then explained such as the Honor System, the homegrown license managers, and the third party tools available.
Another important aspect of software architecture - the-after-development-has-been-done-now-what aspect, is covered throughout the rest of the book. Deployment, installation, configuration and upgrades are the key topics. Other topics such as extensions to the current architecture, logging and branding are also covered in detail.
The chapter on installation is another well-covered chapter that talks about a topic not covered at all or well in other books out there. Various deployment architectures are covered; Customer site installation, ASP, Managed Service Provider, and Web services models make up the topics for this chapter. This chapter, just like all the other chapters, relates the topic at hand to the overall system architecture, and why and how it can have an effect on the overall architecture of the system.
Throughout the book, one theme screams out to the reader: "How every decision an architect makes affects the rest of the software life cycle, and what the architects need to think about and consider before coming up with their design?" The cycle - software life cycle, and how it is affected by the end user/customer, why it's the job of the market architects and business managers to gather the key points from their customers, what are some of the concerns that are common with any architecture (deployment issues, upgrade concerns, installation difficulties, logging and error reporting, security concerns), and tone of the most important aspect of all: Social aspects and how they have an important affect on the tarchitects, markitects and the overall application. I think the author says it best in the preface of the book:
"You need to move beyond software architecture and move toward understanding and embracing the business issues that must be resolved in order to create a winning solution"
12 von 12 Kunden fanden die folgende Rezension hilfreich
Very unique, yet not gripping 24. Januar 2006
Von Thomas Beck - Veröffentlicht auf Amazon.com
Format: Taschenbuch
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.
10 von 10 Kunden fanden die folgende Rezension hilfreich
News you can use, but a bit annoying 28. August 2006
Von Nathaniel Firethorn - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
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.
25 von 30 Kunden fanden die folgende Rezension hilfreich
AND? 13. August 2005
Von Steven W. Spadt - Veröffentlicht auf Amazon.com
Format: Taschenbuch
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.
10 von 11 Kunden fanden die folgende Rezension hilfreich
Beyond Everyday Architecture Issues 25. Februar 2003
Von Rob Purser - Veröffentlicht auf Amazon.com
Format: Taschenbuch
This book delivers on its promise to discuss the larger business realities of creating software products. If you're a software architect, or dream of being one, this is a must read book.
Appropriately, it eschews the details of implementation, and focuses mainly on the business issues an architect must focus on to succeed. It works from the assumption that the reader has done a fair bit of design work, and now wants to create software architectures that will last for multiple releases. Luke expands your horizons to include new areas you probably have not have considered.
The book is nicely segmented into logical chapters, making it an excellent reference. Although it covers classic architecture issues such as portability, usability, performance, layering, API design, and security, the truly valuable material is on the business and product management side of the fence, which often get ignored, or left till late in the process. For instance, the installation "out of the box" experience, planning your upgrade strategy, technology licensing, branding, and user community discussions are incredibly valuable, as they bring together the benefit of a lot of experience in the commercial software market. It is this focus on non-traditional architecture issues that makes the book so valuable.
My only issue with the book is the tone. I find it a little too academic, and I think that it detracts from the pragmatic advice given. However, the content more than makes up for this minor lack. If you're ready to move to the next level of architecture or pondering a new software product design, check this book out.
Waren diese Rezensionen hilfreich? Wir wollen von Ihnen hören.