Home > Store

Beyond Software Architecture: Creating and Sustaining Winning Solutions

Register your product to gain access to bonus material or receive a coupon.

Beyond Software Architecture: Creating and Sustaining Winning Solutions

Best Value Purchase

Book + eBook Bundle

  • Your Price: $64.79
  • List Price: $107.98
  • Includes EPUB and PDF
  • About eBook Formats
  • This eBook includes the following formats, accessible from your Account page after purchase:

    ePub EPUB The open industry format known for its reflowable content and usability on supported mobile devices.

    Adobe Reader PDF The popular standard, used most often with the free Acrobat® Reader® software.

    This eBook requires no passwords or activation to read. We customize your eBook by discreetly watermarking it with your name, making it uniquely yours.

More Purchase Options

Book

  • Your Price: $47.99
  • List Price: $59.99
  • Usually ships in 24 hours.

eBook (Watermarked)

  • Your Price: $38.39
  • List Price: $47.99
  • Includes EPUB and PDF
  • About eBook Formats
  • This eBook includes the following formats, accessible from your Account page after purchase:

    ePub EPUB The open industry format known for its reflowable content and usability on supported mobile devices.

    Adobe Reader PDF The popular standard, used most often with the free Acrobat® Reader® software.

    This eBook requires no passwords or activation to read. We customize your eBook by discreetly watermarking it with your name, making it uniquely yours.

Description

  • Copyright 2003
  • Dimensions: 7-3/8" x 9-1/4"
  • Pages: 352
  • Edition: 1st
  • Book
  • ISBN-10: 0-201-77594-8
  • ISBN-13: 978-0-201-77594-5

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.

Extras

Related Article

Surviving Product Management

Author's Site

Click for the Author's Web Site related to this title.

Sample Content

Online Sample Chapter

Software Architecture: The Difference between Marketecture and Tarchitecture

Downloadable Sample Chapter

Click below for Sample Chapter(s) related to this title:
Sample Chapter 4

Sample Pages

Download the sample pages (includes Chapter 3 and Index)

Table of Contents



Foreword by Martin Fowler.


Foreword by Guy Kawasaki.


Preface.


1. Software Architecture.

Defining Software Architecture.

Alternative Thoughts on Software Architecture.

Subsystems Are Designed to Manage Dependencies.

Subsystems Are Designed According to Human Motivations and Desires.

Give in to Great Architectures.

Beauty Is in the Eye of the Beholder!

Why Software Architecture Matters.

Longevity.

Stability.

Degree and Nature of Change

Profitability.

Social Structure.

Boundaries Defined.

Sustainable, Unfair Advantage.

Creating an Architecture.

Patterns and Architecture.

Architectural Evolution and Maturation: Features versus Capabilities.

Architectural Care and Feeding.

Technological Currency.

Technological Debt.

Known Bugs.

License Compliance.

Principles First, Second, and Third.

Encapsulation.

Interfaces.

Loose Coupling.

Appropriate Granularity.

High Cohesion.

Parameterization.

Deferral.

Creating Architectural Understanding.

The Team.

Chapter Summary.

Check This.

Try This.



2. Product Development Primer.

What Is Product Management?

Why Product Management Matters.

Product Development Processes: Creating Release 1.0.

Concept Proposal.

Product Proposal/Business Plan.

Development Plan.

Development.

Final Quality Assurance.

Prelaunch.

Launch.

It Isn't Like That.

It Is a Waterfall Process and Those Don't Work.

It Presents All Stages as If They Were of Equal Importance.

It Doesn't Detail Any Time.

Where Is the Iteration?

It Doesn't Prescribe a Development Process.

It Doesn't Identify the Level of Collaboration Between Groups within Stages.

The Business Plan.

Product Development Processes: Creating Release n.n.n.

Augmenting the Product Development Process.

Successive Freezing.

Change Management Protocols.

Recycle Bin.

Crucial Product Management Concepts.

The Four Ps of Marketing.

Total Available Market, Total Addressable Market, and Market @BHEADS = Segmentation.

The S-Shaped Curve of Adoption.

The Whole Product.

Technical versus Market Superiority.

Position and Positioning.

Brand.

The Main Message.

Chapter Summary.

Check This.

Try This.



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.

Reaching Agreements.

Making Data Available.

Context Diagrams and Target Products.

Chapter Summary.

Check This.

Try This.



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.

The Client.

Market Maturity Influences on the Business Model.

Choosing a Business Model.

Chapter Summary.

Check This.

Try This.



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.

Chapter Summary.

Check This.

Try This.



6. Portability.

The Perceived Advantages of Portability.

The Business Case for Portability.

Creating Portable Applications.

Use an Interpreted Language.

Use Standards-Based Persistent Storage.

Make Business Logic Portable.

Closer to the User Means Less Portability.

Use XML for Standardized, Interoperable Communications between Subsystems.

Avoid Hiding The Power of a Specific Platform in the Name of Portability.

The Matrix of Pain.

Step 1: Remove Configurations.

Step 2: Rank-Order Configurations.

Step 3: Make the Final Cut.

Beware the Promises You Make.

Chapter Summary.

Check This.

Try This.



7. Deployment Architecture.

Deployment Choices.

Customer Site.

Application Service Provider.

Managed Service Provider.

Transactional (Web Service).

Customer Influences on Deployment Architectures.

Control and Integration.

Data Security/Privacy and Peak Loads.

Costs and Vendor Confidence.

Customer Skills and Experiences and Geographic Distribution.

Corporate Influences on Deployment Architecture.

Sales Cycle.

Infrastructure Investment.

Cash Flow.

Flexibility.

Geographic Distribution.

Service, Not Price.

Choosing a Software Deployment Architecture.

Deployment Architectures and the Distribution of Work.

The Information Appliance.

Deployment Choice Influences on Software Architecture.

Flexible, Parameterized, or No Integration Options.

Upgrade Policies.

Data Protection and Access.

Migration Options.

The Future of Consumer Software.

Chapter Summary.

Check This.

Try This.



8. Integration and Extension.

Customer Control—The Driving Force.

Motivations for Integration/Extension.

Layered Business Architectures: Logical Structures.

The User Interface Layer.

The Services Layer.

The Domain Model Layer.

The Persistent Data Layer.

Variations on a Theme.

Creating Layered Business Architectures.

Integration and Extension at the Business Logic Layers.

Technologies and Locus of Control.

Integration through APIs.

Extension through Registration.

Integration and Extension of Persistent Data.

Views.

User Fields.

Hook Tables.

Spreadsheet Pivot Tables.

Extract, Transform, and Load Scripts.

Tell Them What's Going On.

Business Ramifications.

Professional Services.

Training Programs.

Certification.

User Community.

License Agreements.

Managing APIs Over Multiple Releases.

Techniques.

Chapter Summary.

Check This.

Try This.



9. Brand and Brand Elements.

Brand Elements.

Names.

Graphics, Slogans, and Other Brand Elements.

When to Use the Trademark (™) Symbol.

Managing In-License Brands.

Brand Element Customizations.

Changing Brand Elements.

Product Areas to Change.

QA and Change.

Chapter Summary.

Check This.

Try This.



10. Usability.

Usability Is about Money.

Mental Models, Metaphors, and Usability.

Tarchitectural Influences on User Interface Design.

Areas of Influence.

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.

Chapter Summary.

Check This.

Try This.



11. Installation.

The Out of Box Experience.

Ouch! That Might Hurt.

Customer Fears.

Installation and Architecture.

Forces and Choices.

How to Install.

Installation Data Collection and Precondition Verification.

Installation.

Postinstallation Confirmation.

Finishing Touches.

They Don't Read the Manual.

Test the Install and Uninstall.

Chapter Summary.

Check This.

Try This.



12. Upgrade.

Like Installation, Only Worse.

Upgrade Fears.

Making Upgrades Less Painful.

Choices for Painless Upgrades.

Market Maturity and Upgrades.

Chapter Summary.

Check This.

Try This.



13. Configuration.

Configurability—An Element of Usability.

The System Context.

Contextual Information.

Initialization versus Execution.

Setting the Value.

Setting the Right Value.

Configuration Parameter Heuristics.

Chapter Summary.

Check This.

Try This.



14. 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.

Chapter Summary.

Check This.

Try This.



15. Release Management.

Yes, You Really Need This.

Establishing a Baseline.

Release Management.

What You're Releasing.

Who You're Targeting.

Why They Want It.

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.

Chapter Summary.

Check This.

Try This.



16. Security.

Viruses, Hackers, and Pirates.

Managing Risk.

See No Evil, Speak No Evil.

Digital Identity Management.

Authorization—Defining Who Can Do What.

Authentication—Proof of Identity.

Transaction Security.

Auditability—Proof of Activity.

Integrity—Preventing Tampering and Alteration of Data.

Confidentiality—Keeping Data Away from Those Not Entitled to It.

Accountability—Holding People Responsible for Their Actions.

Software Security.

Software Security Techniques.

Software Security Costs/Benefits.

Information Security.

Secret Algorithms or Secret Keys?

Back Doors.

Security and Marketecture.

Areas of Interaction.

Chapter Summary.

Check This.

Try This.



Appendix A. Release Checklist.


Appendix B. A Pattern Language for Strategic Product Management.

Applying The Patterns.

Capturing the Result.

Market Map.

Market Events/Market Rhythms.

Feature/Benefit Map.

The Tarchitecture Roadmap.



References.


Bibliography.


About the Author.


Index. 0201775948T01212003

Preface

Many excellent books have been written about software architecture. These books, among other things, define, classify, and describe software architectures, define notations for representing and communicating architectural choices, and provide guidance on making good architectural decisions; each has its own enduring value. Unfortunately, even though any one of these books may help you build a successful architecture, they fall short of the goal of helping you create a winning solution. To create a winning solution, you need to move beyond subsystems and interfaces; beyond architectural patterns, such as Front Controller or Pipes and Filters; and beyond creating third-normal form relational databases. You need to move beyond software architecture toward understanding and embracing the business issues that must be resolved to create a winning solution.

An example of one business issue to resolve concerns technical support. It is inevitable that a customer will have a problem with your software. When someone contacts you for assistance, choices you've made long ago in such areas as log file design, how the system is integrated with other systems, how the system is configured, or how the system is upgraded will determine how well you can meet customers' needs. By discussing a wide range of business issues and their interrelationship with architectural choices, Beyond Software Architecture helps you move beyond software architecture and toward creating winning solutions.

This book presents a unique perspective which was developed and informed by my experience in creating everything from single-user programs costing less than $50; to software systems used in academic research; to utilities for diagnosing and fixing problems associated with internally developed systems; to distributed, enterprise-class platforms costing millions of dollars. Along the way, I've played a variety of roles, including being an individual contributor, a direct manager, and a senior member of the corporate executive staff. At various times I've either worked in or led engineering, product marketing and product management, quality assurance, technical publications, and first- and second-line support organizations. I've managed teams and projects in more than one city and across continents.

The common thread that ties all of the software together is that all of it was created to provide value to some person. Research software, for example, serves the needs of the researchers who are trying to understand some phenomenon. Enterprise application software, dealing with everything from customers to supply-chain management, on the other hand, is designed to serve the needs of a well-defined set of users and the businesses who license it in a sustainably profitable manner. Similar comments apply to every other kind of software, from games to personal contact managers, inventory management systems to graphic design tools.

The issues identified and discussed in this book affect every kind of software. The presentation and discussion of these issues occurs most often in the context of enterprise application software, where I have spent most of my professional career. While there is no universally accepted definition of an enterprise application, enterprise applications typically meet one or more of the following characteristics:

  • They are designed to support the needs of a business, at either a departmental or larger organizational unit
  • They are relatively expensive to build or license ($50,000 to $5,000,000+)
  • They have complex deployment and operational requirements;
  • The needs of the business are often best served when they are integrated with other enterprise applications even though some can be operated as independent applications

Even if you're not creating an enterprise application, you will find this book useful. Creating sustainable software solutions to meet customers' needs over a long period of time, through multiple releases, is a challenging, enjoyable, and rewarding endeavor; and it certainly is not limited to the domain of enterprise applications!

Although I will often refer to software architecture, and describe things that are technical in nature, my discussions won't be focused on the best ways to diagram or document your architecture or the deeper design principles associated with creating robust, distributed, Web-based component systems. As I said earlier, there are plenty of books that address these topics. In fact, there are almost too many books on these topics, with the unfortunate side-effect that many people become so focused on technical details that they lose sight of the business value they're trying to provide.

Instead of concentrating on purely technical choices, Beyond Software Architecture helps you create and sustain truly winning solutions by focusing on a wide variety of practical, nuts-and-bolts choices that must be made by the development team. I have found that focusing on practical matters, such as how you should identify a release or how you should integrate branding elements into your solution, often reduces the artificial barriers that can exist between developers and the business and marketing people with whom they work.

These barriers prevent both groups from creating winning solutions. I cringe when engineers profess to taking only a technology point of view without considering the "business issues," or when marketing people make get-me-this-feature demands without considering the underlying technical ramifications of the feature they want. When either side takes a position without due consideration of the request's impact, the likelihood of creating and sustaining a winning solution drops dramatically.

What is especially troubling is that these arguments seem to be made in support of the idea that technical issues can be somehow separated from business issues, or that business issues can be somehow separated from technical issues. At best this is simply wrong; at worst it can be a recipe for disaster. Developers are routinely asked to endure the hardships of design extremes, such as a low-memory footprint, in order to reduce total system cost. Entire companies are started to compete in existing markets because investors are convinced that one or more technological breakthrough will provide the competitive advantage necessary for success. Not surprisingly, investors are even more eager to invest when the technological breakthrough is accompanied by a similar breakthrough in the business model being offered to customers.

How to manage the interrelationship between technology and business is a recurring theme throughout this book. Handle only the former and you may have an interesting technology or, perhaps, an elegant system, but one that ultimately will wither because no one is using it. Handle only the latter, and you'll have a paper solution that excites lots of people, and may even get you funding, but it doesn't deliver any sustainable value. Handle both and you'll have a winning solution. Although creating new technologies or elegant systems can be fun, and designing sophisticated new software applications or business models can be exciting, both pale in comparison to the deep satisfaction that comes from creating and sustaining winning solutions.

Luke Hohmann
luke@lukehohmann.com



0201775948P10112002

Foreword

Click below for Foreword(s) related to this title:
Martin Fowler Foreword

Guy Kawasaki Foweword

Index

Click below to download the Index file related to this title:
Index

Updates

Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020