Beyond Software Architecture: Creating and Sustaining Winning Solutions View Larger Image | Luke Hohmann
Addison-Wesley, Paperback, Published January 2003, 314 pages, ISBN 0201775948 | List Price: $49.99
Our Price: $38.95
You Save: $11.04 (22% Off)
| | | Availability: Out-Of-Stock |
Customer Reviews: 2 Average Customer Rating:  Write a Review and tell the world about this title! People who purchase this book frequently purchase: - Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions; Gregor Hohpe, et al, $50.50, 22% Off!
- Patterns of Enterprise Application Architecture; Martin Fowler, $50.50, 22% Off!
- Head First Design Patterns; Eric Freeman, et al, $26.95, 40% Off!
- Refactoring to Patterns; Joshua Kerievsky, $46.50, 22% Off!
Books on similar topics, in best-seller order:Books from the same publisher, in best-seller order:
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.
Table of Contents
Preface.
Acknowledgments.
1. Software Architecture.
Defining Software Architecture.
Alternative Thoughts of Software Architecture.
Why Software Architecture Matters.
Creating an Architecture.
Patterns and Architecture.
Architectural Evolution and Maturation: Features versus Capabilities.
Architectural Care and Feeding.
Principles First, Second, and Third.
Creating Architectural Understanding.
The Team.
2. Product Development Primer.
What Is “Product Management” ?
Why Product Management Matters.
Product Development Processes: Creating Release 1.0.
It Isn't Like That.
The Business Plan.
Product Development Processes: Creating Release N.N.N.
Augmenting the Product Development Process.
Crucial Product Management Concepts.
The “Four Ps” of Marketing.
Total Available Market, Total Addressable Market, and Market Segmentation.
S-Shaped Curve of Adoption.
Whole Product.
Technical versus Market Superiority.
Position and Positioning.
Brand.
The Main Message.
3. The Difference between Marketecture and Tarchitecture.
Who Is Responsible for What?
Early Forces in Solution Development.
Creating Results in the Short Run while Working in the Long Run.
Projecting the Future.
Harnessing Feedback.
Generating Clarity.
Working In Unison.
Context Diagrams and Target Products.
4. Business and License Model Symbiosis.
Common Software Business Models.
Time-Based Access or Usage.
Transaction.
Metering.
Hardware.
Services.
Revenue Obtained/Costs Saved.
Rights Associated With Business Models.
Tarchitectural Support for the Business Model.
General Issues.
Time-Based Access or Usage.
Transaction.
Metering.
Hardware.
Enforcing Licensing Models.
The Honor System.
Home Grown License Managers.
Third-Party or Professional License Managers.
Market Maturity Influences on Business Model.
Choosing a Business Model.
5. Technology In-Licensing.
Licensing Risks/Rewards.
Contracts—Where the Action Is.
Contract Basics.
License Terms.
When Business Models Collide, Negotiations Ensue.
Honoring License Agreements.
Managing In-Licensed Technology.
Open Source Licensing.
License Fees.
Licensing Economics.
6. Portability.
The Perceived Advantages of Portability.
The Business Case For Portability.
Creating Portable Applications.
The “Matrix of Pain” .
Beware the Promises You Make.
7. Deployment Architecture.
Deployment Choices.
Customer Influences on Deployment Architectures.
Corporate Influences on Deployment Architecture.
Choosing a Software Deployment Architecture.
Deployment Architectures and the Distribution of Work.
The Information Appliance.
Deployment Choice Influences on Software Architecture.
The Future of Consumer Software.
8. Integration and Extension.
Motivations.
Layered Business Architectures: Logical Structures.
Creating Layered Business Architectures.
Integration and Extension at the Business Logic Layers.
Integration through APIs.
Extension through Registration.
Integration and Extension of Persistent Data.
Views.
Hook Tables.
Spreadsheet Pivot Tables.
Extract, Transform, and Load Scripts.
Tell Them What Is Going On.
Business Ramifications.
Professional Services.
Training Programs.
Certification.
User Community.
License Agreements.
Managing APIs over Multiple Releases.
9. Brand and Brand Elements.
Brand Elements.
Names.
Graphics, Slogans, and Other Brand Elements.
When to Use “TM” .
Managing In-License Brands.
Brand Element Customizations.
Changing Brand Elements.
10. Usability.
Usability Is About Money.
Mental Models, Metaphors, and Usability.
Tarchitectural Influences on User Interface Design.
The Need for Speed.
- Let's Be Clear on What We're Talking About.
- What a Marketect Really Wants with Respect to Performance.
- Responding to the User.
- Performance and Tarchitectural Impact.
11. Installation.
Out of Box Experience.
Ouch! That Might Hurt.
Installation and Architecture.
How to Install.
Installation Data Collection and Precondition
Verification.
Installation.
Postinstallation Confirmation.
Finishing Touches.
They Don't Read the Manual.
Testing the Install and Uninstall.
12. Upgrade.
Like Installation, Only Worse.
Making Upgrades Less Painful.
Market Maturity and Upgrades.
13. Configuration and Customization.
Configurability, an Element of Usability.
The System Context.
Initialization versus Execution.
Setting the Value.
Setting the Right Value.
Configuration Parameter Heuristics.
14. Let There Be Logs.
I Want to Know What's Happening.
Not Just the Facts.
Log Format and Management.
Log Format.
Log Management.
Logging Standards and Libraries.
Postprocessing Log Data.
Logging Services.
15. Release Management.
Yes, You Really Need This.
Establishing a Baseline.
Release Management.
Release Identification.
Full or Complete Releases.
Partial Releases.
Patch Releases.
Variations.
SKUs and Serial Numbers.
SKU Management.
Serial Numbers, Registration, and Activation.
Release Management Influences on Tarchitecture.
Appendix A. Release Checklist.
A Pattern Language for Strategic Product Management.
Applying the Patterns.
Capturing the Result.
Appendix B. Market Map.
Context.
Problem.
Forces.
Solution.
Resulting Context.
Related Patterns.
Appendix C. Market Events/Market Rhythms.
Context.
Problem.
Forces.
Solution.
Resulting Context.
Related Patterns.
Appendix D. Feature/Benefit Map.
Context.
Problem.
Forces.
Solution.
Resulting Context.
Related Patterns.
Appendix E. Tarchitecture Roadmap.
Context.
Problem.
Forces.
Solution.
Resulting Context.
Related Patterns.
Index
Customer Reviews
Customer Reviews: 2 Average Customer Rating: Mar 8, 2005 SV from Cambridge, MA
Phenomenal book - every software engineer should buy this book
I had to come back here and plug this book after reading it. I typically buy software books for specific problems but this book piqued my interest. This is one of the few software books I've read from cover to cover. As I read it, I found myself saying a couple of things over and over:
1. This is why X didn't work for us and Y worked so well.
2. I wish we had done things this way.
Hohmann does an excellent job capturing on paper many industry paradigms that have been poorly documented in the past. Although the subject matter can be dry at times, he writes in a manner that holds the reader's interest. As I read the book, I realized that many of the questions I had over the course of my career are answered in this book. My favorite sections are the grey subsections where Hohmann provides an experience from his own past to supplement the current text.
This is probably the best book I've read on commercial software products, it is singly focused on producing a great deliverable. Other books in this category often lose sight of this and get lost along the way.
Dec 1, 2003 Steve from Silicon Valley, CA
An excellent book with bigger picture beyond engineering
It opens an excellent perspective on software engineering with a bigger picture that involves business side. It definitely helps different teams in software business to understand and effectively communicate with each other.
|
