| |
| Table of Contents | |
| Index |
| Beyond Software Architecture: Creating and Sustaining Winning Solutions | |
| By Luke Hohmann | |
| Publisher | : Addison Wesley |
| Pub Date | : January 30, 2003 |
| ISBN | : 0-201-77594-8 |
| Pages | : 352 |
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 Lewin,Corporate 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. Lancashire,CEO, 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.
| |
| Table of Contents | |
| Index |
| Beyond Software Architecture: Creating and Sustaining Winning Solutions | |||
| By Luke Hohmann | |||
| Publisher | : Addison Wesley | ||
| Pub Date | : January 30, 2003 | ||
| ISBN | : 0-201-77594-8 | ||
| Pages | : 352 | ||
| | Copyright | ||
| | Advance praise for Beyond Software Architecture | ||
| | The Addison-Wesley Signature Series | ||
| | Foreword by Martin Fowler | ||
| | Foreword by Guy Kawasaki | ||
| | Preface | ||
| | Acknowledgments | ||
| | Chapter 1. Software Architecture | ||
| | Defining Software Architecture | ||
| | Alternative Thoughts on 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 | ||
| | Chapter Summary | ||
| | Check This | ||
| | Try This | ||
| | Chapter 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 | ||
| | Chapter Summary | ||
| | Check This | ||
| | Try This | ||
| | Chapter 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 | ||
| | Chapter Summary | ||
| | Check This | ||
| | Try This | ||
| | Chapter 4. Business and License Model Symbiosis | ||
| | Common Software Business Models | ||
| | Rights Associated with Business Models | ||
| | Tarchitectural Support for the Business Model | ||
| | Enforcing Licensing Models | ||
| | Market Maturity Influences on the Business Model | ||
| | Chapter Summary | ||
| | Check This | ||
| | Try This | ||
| | Chapter 5. Technology In-Licensing | ||
| | Licensing Risks/Rewards | ||
| | ContractsWhere the Action Is | ||
| | 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 | ||
| | Chapter 6. Portability | ||
| | The Perceived Advantages of Portability | ||
| | The Business Case for Portability | ||
| | Creating Portable Applications | ||
| | The Matrix of Pain | ||
| | Beware the Promises You Make | ||
| | Chapter Summary | ||
| | Check This | ||
| | Try This | ||
| | Chapter 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 | ||
| | Chapter Summary | ||
| | Check This | ||
| | Try This | ||
| | Chapter 8. Integration and Extension | ||
| | Customer ControlThe Driving Force | ||
| | Layered Business Architectures: Logical Structures | ||
| | Creating Layered Business Architectures | ||
| | Integration and Extension at the Business Logic Layers | ||
| | Integration and Extension of Persistent Data | ||
| | Business Ramifications | ||
| | Managing APIs over Multiple Releases | ||
| | Chapter Summary | ||
| | Check This | ||
| | Try This | ||
| | Chapter 9. Brand and Brand Elements | ||
| | Brand Elements | ||
| | Managing In-License Brands | ||
| | Brand Element Customizations | ||
| | Changing Brand Elements | ||
| | Chapter Summary | ||
| | Check This | ||
| | Try This | ||
| | Chapter 10. Usability | ||
| | Usability Is about Money | ||
| | Mental Models, Metaphors, and Usability | ||
| | Tarchitectural Influences on User Interface Design | ||
| | The Need for Speed | ||
| | Chapter Summary | ||
| | Check This | ||
| | Try This | ||
| | Chapter 11. Installation | ||
| | The Out of Box Experience | ||
| | Ouch! That Might Hurt | ||
| | Installation and Architecture | ||
| | How to Install | ||
| | Finishing Touches | ||
| | Chapter Summary | ||
| | Check This | ||
| | Try This | ||
| | Chapter 12. Upgrade | ||
| | Like Installation, Only Worse | ||
| | Making Upgrades Less Painful | ||
| | Market Maturity and Upgrades | ||
| | Chapter Summary | ||
| | Check This | ||
| | Try This | ||
| | Chapter 13. Configuration | ||
| | ConfigurabilityAn Element of Usability | ||
| | The System Context | ||
| | Initialization versus Execution | ||
| | Setting the Value | ||
| | Setting the Right Value | ||
| | Configuration Parameter Heuristics | ||
| | Chapter Summary | ||
| | Check This | ||
| | Try This | ||
| | Chapter 14. Logs | ||
| | I Want to Know What's Happening | ||
| | Not Just the Facts | ||
| | Log Format and Management | ||
| | Postprocessing Log Data | ||
| | Logging Services | ||
| | Chapter Summary | ||
| | Check This | ||
| | Try This | ||
| | Chapter 15. Release Management | ||
| | Yes, You Really Need This | ||
| | Establishing a Baseline | ||
| | Release Management | ||
| | Release Identification | ||
| | SKUs and Serial Numbers | ||
| | Release Management Influences on Tarchitecture | ||
| | Chapter Summary | ||
| | Check This | ||
| | Try This | ||
| | Chapter 16. Security | ||
| | Viruses, Hackers, and Pirates | ||
| | Digital Identity Management | ||
| | Transaction Security | ||
| | Software Security | ||
| | Information Security | ||
| | Secret Algorithms or Secret Keys? | ||
| | Back Doors | ||
| | Security and Marketecture | ||
| | Chapter Summary | ||
| | Check This | ||
| | Try This | ||
| | Appendix A. Release Checklist | ||
| | Tracking Information | ||
| | Engineering/Development | ||
| | Quality Assurance | ||
| | Technical Publications | ||
| | Core Product Management | ||
| | Knowledge TransferProfessional Services | ||
| | Knowledge TransferSales and the Channel | ||
| | Knowledge TransferTechnical Support | ||
| | Release Activities | ||
| | Appendix B. A Pattern Language for Strategic Product Management | ||
| | Applying The Patterns | ||
| | Capturing and Sharing the Result | ||
| | Market Map | ||
| | Market Events/Market Rhythms | ||
| | Feature/Benefit Map | ||
| | The Tarchitecture Roadmap | ||
| | References | ||
| | Bibliography | ||
| | Software DevelopmentPeople and Project Management | ||
| | Software DevelopmentConfiguration Management | ||
| | Software DevelopmentCode and Selected Technologies | ||
| | Product Management / Marketing | ||
| | Business Classics | ||
| | Software Architecture | ||
| | About Luke Hohmann | ||
| | Index |

