Beyond Software Architecture Creating and Sustaining Winning Solutions

Note: Supplemental materials are not guaranteed with Rental or Used book purchases.

ISBN: 9780201775945 | 0201775948
Cover: Paperback
Copyright: 1/30/2003

Buy Used

Usually Ships in 2-4 Business Days

$44.09
eBook

Available Instantly

Online: 1825 Days

Downloadable: Lifetime Access

$62.09

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 readwhich 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 G

Foreword	p. xxi
Foreword	p. xxiii
Preface	p. xxv
Software Architecture	p. 1
Defining Software Architecture	p. 1
Alternative Thoughts on Software Architecture	p. 2
Subsystems Are Designed to Manage Dependencies	p. 2
Subsystems Are Designed According to Human Motivations and Desires	p. 2
Give in to Great Architectures	p. 3
Beauty Is in the Eye of the Beholder!	p. 4
Why Software Architecture Matters	p. 4
Longevity	p. 4
Stability	p. 4
Degree and Nature of Change	p. 5
Profitability	p. 5
Social Structure	p. 5
Boundaries Defined	p. 7
Sustainable, Unfair Advantage	p. 7
Creating an Architecture	p. 7
Patterns and Architecture	p. 9
Architectural Evolution and Maturation: Features versus Capabilities	p. 9
Architectural Care and Feeding	p. 16
Technological Currency	p. 16
Technological Debt	p. 16
Known Bugs	p. 17
License Compliance	p. 17
Principles First, Second, and Third	p. 17
Encapsulation	p. 18
Interfaces	p. 18
Loose Coupling	p. 18
Appropriate Granularity	p. 19
High Cohesion	p. 19
Parameterization	p. 19
Deferral	p. 19
Creating Architectural Understanding	p. 20
The Team	p. 21
Chapter Summary	p. 22
Check This	p. 23
Try This	p. 23
Product Development Primer	p. 25
What Is Product Management?	p. 25
Why Product Management Matters	p. 26
Product Development Processes: Creating Release 1.0	p. 26
Concept Proposal	p. 28
Product Proposal/Business Plan	p. 28
Development Plan	p. 28
Development	p. 30
Final Quality Assurance	p. 30
Prelaunch	p. 32
Launch	p. 33
It Isn't Like That	p. 33
It Is a Waterfall Process and Those Don't Work	p. 33
It Presents All Stages as If They Were of Equal Importance	p. 33
It Doesn't Detail Any Time	p. 34
Where Is the Iteration?	p. 34
It Doesn't Prescribe a Development Process	p. 35
It Doesn't Identify the Level of Collaboration Between Groups within Stages	p. 35
The Business Plan	p. 35
Product Development Processes: Creating Release n.n.n	p. 37
Augmenting the Product Development Process	p. 37
Successive Freezing	p. 38
Change Management Protocols	p. 38
Recycle Bin	p. 40
Crucial Product Management Concepts	p. 40
The Four Ps of Marketing	p. 40
Total Available Market, Total Addressable Market, and Market Segmentation	p. 41
The S-Shaped Curve of Adoption	p. 42
The Whole Product	p. 44
Technical versus Market Superiority	p. 45
Position and Positioning	p. 45
Brand	p. 47
The Main Message	p. 47
Chapter Summary	p. 48
Check This	p. 49
Try This	p. 49
The Difference between Marketecture and Tarchitecture	p. 51
Who Is Responsible for What?	p. 51
Early Forces in Solution Development	p. 53
Creating Results in the Short Run while Working in the Long Run	p. 57
Projecting the Future	p. 58
Harnessing Feedback	p. 59
Generating Clarity	p. 60
Working in Unison	p. 62
Reaching Agreements	p. 63
Making Data Available	p. 63
Context Diagrams and Target Products	p. 64
Chapter Summary	p. 65
Check This	p. 65
Try This	p. 66
Business and License Model Symbiosis	p. 67
Common Software Business Models	p. 69
Time-Based Access or Usage	p. 71
Transaction	p. 74
Metering	p. 76
Hardware	p. 78
Services	p. 79
Revenue Obtained/Costs Saved	p. 79
Rights Associated with Business Models	p. 81
Tarchitectural Support for the Business Model	p. 82
General Issues	p. 83
Time-Based Access or Usage	p. 84
Transaction	p. 85
Metering	p. 86
Hardware	p. 87
Enforcing Licensing Models	p. 87
The Honor System	p. 88
Home-Grown License Managers	p. 88
Third-Party or Professional License Managers	p. 89
The Client	p. 89
Market Maturity Influences on the Business Model	p. 93
Choosing a Business Model	p. 93
Chapter Summary	p. 94
Check This	p. 95
Try This	p. 95
Technology In-Licensing	p. 97
Licensing Risks/Rewards	p. 98
Contracts--Where the Action Is	p. 101
Contract Basics	p. 101
License Terms	p. 102
When Business Models Collide, Negotiations Ensue	p. 106
Honoring License Agreements	p. 107
Managing In-Licensed Technology	p. 108
Open-Source Licensing	p. 108
License Fees	p. 109
Licensing Economics	p. 111
Chapter Summary	p. 112
Check This	p. 113
Try This	p. 113
Portability	p. 115
The Perceived Advantages of Portability	p. 115
The Business Case for Portability	p. 116
Creating Portable Applications	p. 119
Use an Interpreted Language	p. 119
Use Standards-Based Persistent Storage	p. 120
Make Business Logic Portable	p. 120
Closer to the User Means Less Portability	p. 120
Use XML for Standardized, Interoperable Communications between Subsystems	p. 120
Avoid Hiding The Power of a Specific Platform in the Name of Portability	p. 121
The Matrix of Pain	p. 121
Remove Configurations	p. 122
Rank-Order Configurations	p. 123
Make the Final Cut	p. 123
Beware the Promises You Make	p. 126
Chapter Summary	p. 126
Check This	p. 127
Try This	p. 127
Deployment Architecture	p. 129
Deployment Choices	p. 130
Customer Site	p. 130
Application Service Provider	p. 130
Managed Service Provider	p. 130
Transactional (Web Service)	p. 131
Customer Influences on Deployment Architectures	p. 132
Control and Integration	p. 132
Data Security/Privacy and Peak Loads	p. 133
Costs and Vendor Confidence	p. 133
Customer Skills and Experiences and Geographic Distribution	p. 134
Corporate Influences on Deployment Architecture	p. 136
Sales Cycle	p. 136
Infrastructure Investment	p. 136
Cash Flow	p. 137
Flexibility	p. 137
Geographic Distribution	p. 137
Service, Not Price	p. 138
Choosing a Software Deployment Architecture	p. 138
Deployment Architectures and the Distribution of Work	p. 138
The Information Appliance	p. 140
Deployment Choice Influences on Software Architecture	p. 140
Flexible, Parameterized, or No Integration Options	p. 141
Upgrade Policies	p. 141
Data Protection and Access	p. 141
Migration Options	p. 141
The Future of Consumer Software	p. 142
Chapter Summary	p. 142
Check This	p. 143
Try This	p. 143
Integration and Extension	p. 145
Customer Control--The Driving Force	p. 145
Motivations for Integration/Extension	p. 145
Layered Business Architectures: Logical Structures	p. 147
The User Interface Layer	p. 147
The Services Layer	p. 149
The Domain Model Layer	p. 149
The Persistent Data Layer	p. 150
Variations on a Theme	p. 151
Creating Layered Business Architectures	p. 151
Integration and Extension at the Business Logic Layers	p. 154
Technologies and Locus of Control	p. 155
Integration through APIs	p. 155
Extension through Registration	p. 158
Integration and Extension of Persistent Data	p. 159
Views	p. 159
User Fields	p. 160
Hook Tables	p. 161
Spreadsheet Pivot Tables	p. 162
Extract, Transform, and Load Scripts	p. 162
Tell Them What's Going On	p. 163
Business Ramifications	p. 163
Professional Services	p. 164
Training Programs	p. 165
Certification	p. 166
User Community	p. 167
License Agreements	p. 168
Managing APIs Over Multiple Releases	p. 169
Techniques	p. 170
Chapter Summary	p. 170
Check This	p. 171
Try This	p. 172
Brand and Brand Elements	p. 173
Brand Elements	p. 173
Names	p. 173
Graphics, Slogans, and Other Brand Elements	p. 177
When to Use the Trademark Symbol	p. 177
Managing In-License Brands	p. 178
Brand Element Customizations	p. 179
Changing Brand Elements	p. 179
Product Areas to Change	p. 180
QA and Change	p. 181
Chapter Summary	p. 181
Check This	p. 181
Try This	p. 182
Usability	p. 183
Usability Is about Money	p. 183
Mental Models, Metaphors, and Usability	p. 185
Tarchitectural Influences on User Interface Design	p. 187
Areas of Influence	p. 187
The Need for Speed	p. 193
Let's Be Clear on What We're Talking About	p. 193
What a Marketect Really Wants with Respect to Performance	p. 195
Responding to the User	p. 197
Performance And Tarchitectural Impact	p. 198
Chapter Summary	p. 201
Check This	p. 201
Try This	p. 202
Installation	p. 203
The Out of Box Experience	p. 203
Ouch! That Might Hurt	p. 205
Customer Fears	p. 205
Installation and Architecture	p. 206
Forces and Choices	p. 206
How to Install	p. 209
Installation Data Collection and Precondition Verification	p. 209
Installation	p. 210
Postinstallation Confirmation	p. 212
Finishing Touches	p. 212
They Don't Read the Manual	p. 212
Test the Install and Uninstall	p. 213
Chapter Summary	p. 214
Check This	p. 214
Try This	p. 215
Upgrade	p. 217
Like Installation, Only Worse	p. 217
Upgrade Fears	p. 217
Making Upgrades Less Painful	p. 221
Choices for Painless Upgrades	p. 221
Market Maturity and Upgrades	p. 224
Chapter Summary	p. 225
Check This	p. 225
Try This	p. 225
Configuration	p. 227
Configurability--An Element of Usability	p. 227
The System Context	p. 228
Contextual Information	p. 228
Initialization versus Execution	p. 230
Setting the Value	p. 230
Setting the Right Value	p. 231
Configuration Parameter Heuristics	p. 232
Chapter Summary	p. 233
Check This	p. 234
Try This	p. 234
Logs	p. 235
I Want to Know What's Happening	p. 236
Not Just the Facts	p. 237
Log Format and Management	p. 239
Log Format	p. 239
Log Management	p. 241
Logging Standards and Libraries	p. 242
Postprocessing Log Data	p. 243
Logging Services	p. 243
Chapter Summary	p. 244
Check This	p. 245
Try This	p. 245
Release Management	p. 247
Yes, You Really Need This	p. 247
Establishing a Baseline	p. 248
Release Management	p. 249
What You're Releasing	p. 249
Who You're Targeting	p. 250
Why They Want It	p. 250
Release Identification	p. 251
Full or Complete Releases	p. 251
Partial Releases	p. 252
Patch Releases	p. 253
Variations	p. 255
SKUs and Serial Numbers	p. 256
SKU Management	p. 256
Serial Numbers, Registration, and Activation	p. 258
Release Management Influences on Tarchitecture	p. 259
Chapter Summary	p. 261
Check This	p. 261
Try This	p. 262
Security	p. 263
Viruses, Hackers, and Pirates	p. 264
Managing Risk	p. 265
See No Evil, Speak No Evil	p. 265
Digital Identity Management	p. 266
Authorization--Defining Who Can Do What	p. 266
Authentication--Proof of Identity	p. 266
Transaction Security	p. 269
Auditability--Proof of Activity	p. 269
Integrity--Preventing Tampering and Alteration of Data	p. 269
Confidentiality--Keeping Data Away from Those Not Entitled to It	p. 270
Accountability--Holding People Responsible for Their Actions	p. 270
Software Security	p. 271
Software Security Techniques	p. 271
Software Security Costs/Benefits	p. 273
Information Security	p. 273
Secret Algorithms or Secret Keys?	p. 274
Back Doors	p. 275
Security and Marketecture	p. 276
Areas of Interaction	p. 276
Chapter Summary	p. 278
Check This	p. 279
Try This	p. 280
Release Checklist	p. 281
A Pattern Language for Strategic Product Management	p. 285
Applying The Patterns	p. 286
Capturing the Result	p. 287
Market Map	p. 288
Market Events/Market Rhythms	p. 289
Feature/Benefit Map	p. 291
The Tarchitecture Roadmap	p. 292
References	p. 295
Bibliography	p. 297
About the Author	p. 301
Index	p. 303
Table of Contents provided by Syndetics. All Rights Reserved.

Please wait while the item is added to your bag...

FREE SHIPPING

Amazon no longer offers textbook rentals. We do!

Beyond Software Architecture Creating and Sustaining Winning Solutions

Summary

Author Biography

Table of Contents

Supplemental Materials