Beyond software architecture creating and sustaining winning solutions download

There are many good books, reports, papers, and videos available in the software architecture world. Byrnes, The Secured Enterprise: Protecting your information assets. Software architecture : Foundations, theory, and practice. New York: Wiley.

Beyond software architecture : Creating and sustaining winning solutions. Garland, J. Large scale software architecture : Apractical guide using UML. Hohmann, L. AddisonWesley Longman Publishing. Hohmann L Beyond software architecture — creating and sustaining winning solutions. Addison-Wesley, New York Beyond software architecture — creating and sustaining winning solutions.

ISBN Hohpe, G. Enterprise integration patterns — designing, building, and deploying messaging 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.

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.

Integrity—Preventing Tampering and Alteration of Data. Pearson offers affordable and accessible purchase options to meet the needs of your students. Connect with us to learn more. Luke Hohmann is an independent consultant committed to coaching his clients to greater levels of performance in the areas of product management, software development, and organizational effectiveness.

Hohmann is the author of Journey of the Software Professional: A Sociology of Software Development Prentice Hall, , as well as numerous articles on software development. We're sorry! We don't recognize your username or password. Please try again. The work is protected by local and international copyright laws and is provided solely for the use of instructors in teaching their courses and assessing student learning.

You have successfully signed out and will be required to sign back in should you need to download more resources. Overview Contents Order Authors Overview. Description Luke Hohmann borrows from his extensive experience managing successful enterprise software projects to provide practical wisdom on creating and sustaining winning software solutions.

Series This product is part of the following series. Addison-Wesley Signature Series Fowler. Table of Contents Foreword by Martin Fowler. It would be useful when you first start a project as well as evaluating a current program for strengths and weakness, providing an evaluation checklist for each subject. Once you know where your project stands you will be able to know where you should concentrate your energies. I had higher expectations from this one.

Luckily I got it second hand and didn't cough up much. Only a few interesting insights, the rest common knowledge, nothing ground breaking, unless you are a complete novice. Robert Postill. Best described as a wearying trudge through the author's laundry list of things architects don't think about. Mikhail Filatov. This book is more about product management than Software Architecture. Strangely enough, Product Management is introduced in the beginning, but after that the author decides to split architecture into "marchitecture" marketing architecture and tarchitecture technical architecture.

Marchitecture is mostly used commonly as a synonym for "vaporware", while in author' terms it is about all external facing aspects of Software architecture: pricing, branding, release management, etc. Which is mostly the stuff PM should be taking care of. There are actually some interesting thoughts, especially about pricing which are not outdated. Any "tarchitecture" stuff is really from , if not from 90s. Christoph Kappel. I am not exactly sure about this one. The generell idea to separate architecture in a marketing and a technical is quite nice, especially if you use this metaphor to talk about the different aspects of both ways.

So the wording "marchitecture" and "tarchitecture" work pretty well. The book is generally focused about the complete product cycle, from creating it to brining it to the end customer which I normally never see, due to the nature of being rather a consultant. I must admit I sometimes had to force myself to go on, some parts were boring for me.