Patterns for E-Business: A Strategy for Reuse

I had the distinct pleasure of working with Srinivas Koushik and Guru Vasudeva when "Patterns for e-business: A Strategy for Reuse" was published. I saw how they applied eBusiness patterns on real-world business solutions to reduce risk, improve quality, and accelerate time-to-market. "Patterns for e-business: A Strategy for Reuse"by Jonathan Adams, Srinivas Koushik, Guru Vasudeva, and George Galambos is a must-have reference book for enterprise architects. This well-structured and well-written book condenses the authors' many years of enterprise architecture experience into a concise framework. Specific chapters discuss groups of related eBuiness patterns for solving common architectural challenges. The authors provide descriptions, diagrams, and practical guidance for each eBusiness pattern. __Joseph Starwood

I work for a company that builds and extends enterprise applications for other companies. This book has really helped get our architecture practice in order. The best thing about this book is that it gives a methodology for designing an architecture based upon business requirements. This transition from the problem space (needs, features, requirements, etc.) to the solution space (architecture, design, tools, etc.) is glossed over or non-existant in most patterns books as they are oriented on starting at the architecture level (or lower) instead of the business requirements. We have found this methodology very useful for reducing project risk because we are building upon proven patterns and it has proven very useful for developing quick and concise proposals that demonstrate to our clients that we listened, understood, and have a roadmap for building their solution. Although the IBM e-business patterns website offers much more information than this book (and it's free), the book is a great asset because it steps you through the high levels of the methodology in a more approachable way.

The patience and persistence of the authors has resulted in a text that should soon be recognized as a work of a higher order than the classic "Design Patterns - Elements of Reusable Object-Oriented Software" by Gamma, et al. Higher order here indicates a higher position in the design process. The two works address different areas of the pattern domain, but, by addressing business leaders and solution designers, Adam's "Patterns for e-business" will have the effect of helping drive the use of patterns at all levels of the software construction ptocess. The pattern classifications, and the clear indication of business and IT drivers are excellent. No matter what your role, reading this work will make you a better participant in the systems design and construction process.The authors take the time to recommend, based on your role, which chapters to read, and it which order. My suggestion -- read them all, front to back. As someone who loves learning, I was especially drawn to the Composite patterns and discussions regarding the use of packages to provide the implementation of many parts of some patterns.Prior to the publication of this work, I attended Mr. Adams presentation on patterns and later used the Patterns Development Kit (PDK) that supports the patterns. The session was great, I felt more of an architect/designer and builder than on any project or engagement.The authors have made a great contribution to systems development by cataloging years of knowledge in a way that helps practitioners make sound design decisions.Adams, Gamma, and Booch/Rumbaugh are names to remember.

The patience and persistence of the authors has resulted in a text that should soon be recognized as a work of a higher order than the classic "Design Patterns - Elements of Reusable Object-Oriented Software" by Gamma, et al. Higher order here indicates a higher position in the design process. The two works address different areas of the pattern domain, but, by addressing business leaders and solution designers, Adam's "Patterns for e-business" will have the effect of helping drive the use of patterns to all levels of the software construction process. The pattern classifications, and the clear indication of business and IT drivers are excellent. No matter what your role, reading this work will make you a better participant in the systems design and construction process.The authors take the time to recommend, based on your role, which chapters to read, and it which order. My suggestion -- read them all, front to back. As someone who loves learning, I was especially drawn to the Composite patterns and discussions regarding the use of packages to provide the implementation of many parts of some patterns.Prior to the publication of this work, I attended Mr. Adams presentation on patterns and later used the Patterns Development Kit (PDK) that supports the patterns. The session was great; I felt more of an architect/designer and builder than on any project or engagement.The authors have made a great contribution to systems development by cataloging years of knowledge in a way that helps practitioners make sound design decisions.Adams, Gamma, and Booch/Rumbaugh are names to remember.

This is a highly readable book with a much needed holistic view of e-business.Anyone who has, or is, establishing enterprise architectural standards ought to consider this approach to layering assets i.e patterns.The book introduces a real insight into reuse! I have read "Objects, Components and Frameworks with UML" (The Catalysis Approach) by Desmond D'Souza/Alan Wills and "Software Reuse" by Ivar Jacobson/Martin Griss/Patrik Jonsson. I struggled with both these books to abstract the basic concepts of software reuse. "Patterns for e-business" helped enormously.If, like me, time is at a premium but you really need to understand a strategy for reuse...then read this book!