Buy new:
-35% $38.74$38.74
Delivery Friday, June 28
Ships from: Amazon Sold by: WorldPrime
Save with Used - Good
$19.28$19.28
Delivery Tuesday, July 2
Ships from: Amazon Sold by: Bucketlist Store
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Beyond Software Architecture: Creating and Sustaining Winning Solutions 1st Edition
Purchase options and add-ons
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.
- ISBN-100201775948
- ISBN-13978-0201775945
- Edition1st
- PublisherAddison-Wesley Professional
- Publication dateJanuary 30, 2003
- LanguageEnglish
- Dimensions7.25 x 0.75 x 9 inches
- Print length352 pages
Frequently bought together

Customers who bought this item also bought

Enterprise Integration Patterns: Designing, Building, and Deploying Messaging SolutionsHardcover$14.31 shippingOnly 18 left in stock (more on the way).
Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise (Agile Software Development Series)Hardcover$13.37 shippingGet it as soon as Friday, Jun 28Only 1 left in stock - order soon.
Become an Effective Software Engineering Manager: How to Be the Leader Your Development Team NeedsDr. James StanierPaperback$11.46 shipping
Editorial Reviews
From the Back Cover
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 BourbonGeneral 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 NavarreteVice 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 SolsoCEO, 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 SchechterCEO, 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 HighsmithDirector, 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 RothmanRothman 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 SiglerPrincipal, 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 PoppendieckManaging 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 YourdonAuthor 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 ChaikenVice President, Systems Architecture
AgileTV Corporation
“Product marketing influences product architecture. This shouldn’t be a surprise, yet most texts on software architecture are silent on this fact. This may be because we lack the language for distinguishing between the technical aspects of an architecture and the marketing aspects. Beyond Software Architecture provides the language to draw this important distinction, and provides strategies for overall architectural success.”
― Dave W. Smith“Beyond Software Architecture, as the title implies, successfully addresses the often neglected aspects of developing total solutions. Hohmann demonstrates both passion and depth for the broad set of topics discussed.”
― Craig PriessDirector Product Management, Resonant Software
“Looking through my technical library, it’s apparent that many books are obsolete, casualties of technical innovation and change. There are a few, however, that remain and continue to be relevant. Adding Luke Hohmann’s new book, Beyond Software Architecture: Creating and Sustaining Winning Solutions expands that selection and fills an important gap. It is the first book that I recall presenting a holistic approach to software creation. Going beyond the technical aspects by weaving together and linking critical business and marketing development in such a way to elevate and show how both technical and marketing processes must coalesce to create a winning solution. The topic's importance extends beyond programmers, designers and other technical staff, just as does its content. For marketing professionals, it shows how their decisions and strategies can impact technical decisions. For consumers, it can give them insight on the best ways to work with software manufacturers. For the software entrepreneur, it offers a plan for creating a successful venture. The content, at just the right amount of detail, is presented in easy-to-understand language and in such a way that the information is easy to retain and apply. The topics are timeless. The book will be relevant for a long time.”
― Clay Miller“I highly recommend this book. As a former software company CEO and founder I have worked with many software engineers and had a number of VPs of engineering report to me. Luke was and is one of the best. He is not only a great engineer, but has a keen grasp of the strategic business issues that must drive good code and architectural decisions. I consider Beyond Software Architecture required reading for anyone building software systems.”
― Kevin RivetteExecutive Advisor, BCG Consulting
author of Rembrandts In The Attic
“Perhaps you’ve met, or worked with, or heard speak at events, or read the writings of someone who expects reverence because he commands academic knowledge of the latest software patterns, technologies, or development processes and tools. So what, you say. Suppose you take such knowledge for granted. Suppose that knowledge is the minimum qualification for a member of your team. Then what? What separates a real contributor to the success of your project and organization, from the average bookish expert of the day? In Beyond Software Architecture, Luke Hohmann writes of the stuff that makes up those answers. Installation and upgrade. Configurability and customization of your software. Integration with other software. Usability. Logging. Interdepartmental processes and release management. Business models, licensing, and deployment choices. The stuff that makes software development much bigger, and much messier, than UML diagrams of some pattern implemented with components. The stuff that makes software development real. Luke knows because he’s been in the trenches, trying to make businesses successful. He spends his time doing it more than writing and talking about it. But now he distills his insights and shares the benefit of his experience. If you’re like me, you’ll find yourself nodding your head and underlining passages as you read this book. Luke’s observations will resonate with you. Your organization, and the software development profession as a whole, can benefit from using the vocabulary and ideas in this book. So you’ll want to recommend it to others, which is exactly what I’m doing here.”
― Randy StaffordChief Architect, IQNavigator, Inc.
“Hohmann’s book provides a unique perspective on how the many and subtle technology decisions shape the economic and strategic landscape. Corporate strategists in many industries will find these insights enormously valuable.”
― Martha AmramStrategic Advisor and Consultant
author of Value Sweep and co-author of Real Options
“Luke put his tremendous experience to good use by eliminating the us versus them approach of marketing and engineering departments. This book is a must for every senior engineer, software architect, and product manager. With the practical advice in this book they can concentrate on beating the competitors.”
― Heinrich Gantenbein“I once was a QA manager for Luke Hohmann. I can tell you the guy knows competitive software development. He was in the trenches with us, working through technical problems and sweating the difficult business decisions. He’s uniquely qualified to write about both the business and technical side of software architecture, and this book successfully bridges both worlds. The result is a seminal handbook for product managers and directors of software engineering.”
― James BachFounder, Satisfice, Inc.
“Too many times my firm is asked to resolve a dispute that could have been avoided had the companies involved with the dispute more clearly defined their business and licensing models before the contract was signed. In Beyond Software Architecture, Luke Hohmann clearly explains how to avoid unnecessary and costly disputes regarding business and licensing models. This is a must read book for senior product managers and technical executives.”
― Rob SterneFounder, Sterne, Kessler, Goldstein and Fox
International Authority in Intellectual Property
“Luke Hohmann’s excellent BSA communicates essential hard-won insights from a rare individual―both architect and business leader―who shows us that architecture is more than describing layers; it’s about creating winning solutions through understanding, and resolving the market, business, and technical forces.”
― Craig Larmanauthor, Applying UML and Patterns: An Introduction to OOA&D and the Rational Unified Process
“By stepping back and evaluating the interaction between business drivers and software development, Beyond Software Architecture provides the perspective to create a winning solution. This book is a practical guide for achieving quick time to market solutions through the identification of pitfalls and suggests pragmatic alternatives to effective solution development. Real life examples provide an instructional view of the life cycle phases, including clear roles and responsibilities, as seen by the entire project team. Knowing when to give up the ghost, seek the help of others, or simply leverage a proven model, Beyond Software Architecture explores the alternatives and identifies key decision points. A must read for software architects and product managers seeking an understanding of the challenges and dynamics of a successful software development effort, and a winning solution―the first time.”
― Mark WelkeHigh Availability Marketing Manager, Hewlett Packard
“The thing you need to consider when creating a great application is “Everything.” Great applications do not usually come from a single great idea, great architecture, or great appreciation of the customer’s need. Instead they come out of a unique confluence of a large number of factors encompassing marketing, technology, psychology, support, economics, legal factors, and more. While many books address individual aspects of software application development, Luke Hohmann’s book, Beyond Software Architecture, addresses a very broad range of topics, all of which should be addressed in the creation of every application, but often aren’t. I would recommend that anyone involved in the creation of a software application read this book as a guide to the things that need to be considered in the process. No book can cover “everything,” but this one is a laudable attempt.”
― Jim GayOne Jump Consulting
“A successful software product’s technical architecture must align with the realities of the marketplace. While the goal is obvious, marketers and technologist often find themselves in two warring camps, separated by a chasm of incompatible attitudes and expectations. If you want to close this gap and focus on product success, this book is required reading for both sides.”
― Dave QuickArchitect, Integrated Solutions Development Group, Microsoft, Inc.
“As a technologist who has transitioned to product team leadership, this book distils many of the lessons I’ve learned through study, trial, and error. As someone who still bridges the gap between software development and executive management, I found this book a great refresher and filled with little “oh yeah!” insights. And, as I continue to work with teams to manage and develop new products, I’m sure I’ll use it as a reference and a teaching resource, bringing the “big picture” into view and avoiding costly pitfalls. Anyone managing product development or marketing, aspiring to manage, or unhappy with current management should definitely read Hohmann’s work.”
― Todd GirvinPresident, Optiview Inc.
“Over the years, I’ve seen many projects that have failed, or struggled, to cross the bridge between new product invention and creating a winning solution. This book provides a practical set of guidelines―it’s a useful, and usable, book.”
― Dan'l LewinCorporate Vice President of Microsoft .NET Business Development
“The real magic happens where business and technology ideas meet. This book will help you make the connection.”
― David A. LancashireCEO, Geniant
Successfully managing the relationship between business and technology is a daunting task faced by all companies in the twenty-first century. Beyond Software Architecture is a practical guide to properly managing this mission-critical relationship. In our modern economy, every software decision can have a significant impact on business; conversely, most business decisions will influence a software application's viability. This book contains keen insights and useful lessons about creating winning software solutions in the context of a real-world business.
Software should be designed to deliver value to an organization, but all too often it brings turmoil instead. Powerful applications are available in the marketplace, but purchasing or licensing these technologies does not guarantee success. Winning solutions must be properly integrated into an organization's infrastructure.
Software expert Luke Hohmann teaches you the business ramifications of software-architecture decisions, and further instructs you on how to understand and embrace the business issues that must be resolved to achieve software success. Using this book as a roadmap, business managers and development teams can safely navigate the minefield of important decisions that they face on a regular basis. The resulting synergy between business and technology will allow you to create winning technology solutions, and ensure your organization's success--now and in the future.
About the Author
Luke Hohmann is an independent consultant committed to coaching his clients to greater levels of performance in the areas of product management, software development, and organizational effectiveness. He has worked in and lead development, product marketing/management, quality assurance, support, and business development functions in both public and private companies. He has created software ranging from single-user programs costing less than $50 to distributed, enterprise-class software platforms costing multiple millions of dollars. Mr. Hohmann is the author of Journey of the Software Professional: A Sociology of Software Development (Prentice Hall, 1997), as well as numerous articles on software development.
0201775948AB01132003
Product details
- Publisher : Addison-Wesley Professional; 1st edition (January 30, 2003)
- Language : English
- Paperback : 352 pages
- ISBN-10 : 0201775948
- ISBN-13 : 978-0201775945
- Item Weight : 1.6 pounds
- Dimensions : 7.25 x 0.75 x 9 inches
- Best Sellers Rank: #624,221 in Books (See Top 100 in Books)
- #24 in Computer Hardware Design
- #74 in Software Design & Engineering
- #146 in Computer Hardware Design & Architecture
- Customer Reviews:
About the author

Luke Hohmann is Chief Innovation Officer of Applied Frameworks, a boutique consulting form helping companies create more profitable software-enabled solutions through our unique Profit Streams™ framework.
A serial entrepreneur, Luke founded, bootstrapped, and sold Conteneo, an enterprise software company that helped global companies manage investment portfolios using Participatory Budgeting.
Luke is one of six people in the world recognized as a Principal Contributor to the Scaled Agile Framework, one of the world’s most widely adopted Agile Software Development frameworks.
A prolific author and creator, Luke’s contributions to the global agile community include five books, Profit Streams™, Innovation Games®, and a pattern language for market-driven roadmapping.
Luke is also co-founder of Every Voice Engaged Foundation, where he partnered with The Kettering Foundation to create Common Ground for Action, the world’s first scalable platform for deliberative decision-making.
Luke is a former National Junior Pairs Figure Skating Champion and has an M.S.E. in Computer Science and Engineering from the University of Michigan. Luke loves his wife and four kids, his wife’s cooking, and long runs in the California sunshine and Santa Cruz mountains.
Check it out: www.appliedframeworks.com, www.profit-streams.com, www.everyvoiceengaged.org
Customer reviews
Our goal is to make sure every review is trustworthy and useful. That's why we use both technology and human investigators to block fake reviews before customers ever see them. Learn more
We block Amazon accounts that violate our community guidelines. We also block sellers who buy reviews and take legal actions against parties who provide these reviews. Learn how to report
-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
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!
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"
In this excellent and timely book, Hohmann takes that desire for customer responsiveness a quantum step further, asking that every aspect of a software product (internal or external), from business model to architecture, be aligned with business purpose and business reality.
To put it another way, he widens the software "project team" to include everybody and anybody who must dream up, define, design, market, sell, build, test, maintain, extend, support, and ultimately retire a system. It helps to systematize the hard and institutionally complex work of taking all of that input into account throughout the lifecycle.
So the book talks about taking into account the customer-related input from all of the above roles. But it also asks us to keep the system responsive to all of the knowledge workers in those roles, and their continuing human needs. As hard as it is to do, it is not enough that a system be easy to extend for its programmers. It's not even enough that it provides the optimal feature set, on-time within budget. There is more hard work for it to do. Some systems are a hell of a lot easier to support than others, or easier to market and sell than others. And on and on.
Hohmann shows us how the systems we build will inevitably end up responding to a wide range of needs and roles one way or another, and asks us to anticipate them all, embrace them all, and respond to them up-front, purposefully and systematically. I really, really like that. I can put these insights to use immediately.
I think of the Agile practice revolution as an essentially humanizing revolution in software development, but at a fairly low institutional level. Agile practices largely help us only with the building of the system. And to the extent that Agile methods humanize that building process, they are great.
But I think Hohmann's book gives us the start of a higher-tier, larger view of a humanizing movement, not just in building software systems, but in the entire lifecycle, the entire arc from conception to death. A humanized view of the lifecycle is a fabulous thing, to my mind. I think it really could change the software world permanently. We could all end up (gasp) loving our jobs.
This is an important book, full of Aha! insights. If you have responsibility in any of the above roles I mention, I think you need to 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.
Top reviews from other countries
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
