9780131412279

The completely updated "field manual" for becoming a better software architect!The crucial skills you need to survive and thrive as an enterprise software architect! Fully updated for the latest techniques-from lightweight methods and architectural layers to Model-Driven Architecture and UML 2.0!In this book, Raphael Malveau and Thomas J. Mowbray share up-to-the-minute insights and practical solutions for all the key challenges of building enterprise software systems with objects, components, and Internet technologies. You'll master today's best technical and business practices for the entire project lifecycle as you discover how to avoid crucial pitfalls and costly errors. Coverage includes: Choosing the right architectural model for your project Executing heavyweight and lightweight approaches to software architecture Understanding the architectural issues associated with open source development Managing complexity, scalability, reliability, security, latency, and flexibility Making the most of abstraction, refactoring, and architectural prototyping Leveraging proven design patterns and anti-patterns Effective prototyping, business-case development, and project leadership Coordinating smoothly with project managers and teams Managing your own career as a software architect With hands-on exercises, real-life war stories, and a take-no-prisoners attitude, Software Architect Bootcamp, Second Edition , won't just help you become a great software architect: it'll help you become a true technical leader of your organization.

RAPHAEL MALVEAU, a software architect and consultant based in Alexandria, VA, currently serving as Technical Director for SRA International working to modernize several mission-critical enterprise systems in the Federal government. Previously, as Chief Scientist and Strategic Architect at both startup and major established IT companies, he engineered advanced component architecture best practices that led to the creation of several industry-leading software products.

DR. THOMAS J. MOWBRAY is the Chairman of the Component Management Group and Founding Board member of the Worldwide Institute of Software Architects. He is the author of four books on distributed components and software architecture.

Preface
Introduction
Defining Software Architecture
The Need for the Software Architect
Goals
Military History
Software Architecture Approaches
The Architectural Paradigm Shift
The Need for Software Architecture
Zachman Framework
Reference Model for Open Distributed Processing
Enterprise Architecture Standards
Design Patterns
AntiPatterns
Software Design-Level Model
Conclusions
Software Architecture: Basic Training
Object-Oriented Technology
Component-Oriented Technology
Technology Ownership
Client-Server Technology
Internet Technology
Architectural Layers and When to Use Them
Software Application Experience
Technology and Application Architecture
Applying Standards to Application Systems
Distributed Infrastructures
Conclusions
Software Architecture: Going to War
Software Architecture Paradigm Shift
Doing Software Incorrectly
Doing Software Correctly: Enterprise Architecture Development
Bottom Line: Time, People, and Money
Conclusions
Software Architecture: Drill School
Architecture Versus Programming
Managing Complexity Using Architecture
Systems Integration
Making the Business Case
Architectural Linkage to Software Development
Conclusions
Leadership Training
Leadership Is a Necessary, Learnable Skill
The Architect as Team Builder
Always Insist on Excellence in Deliverables
Architect's Walkthrough
Project Management Basics
Architect's Role Versus Project Management
Conclusions
Software Architecture: Jump School
Process
Creating New Processes
Teamwork
Conclusions
Communications Training
Communications Challenges
Responsibility-Driven Development
Communication Responsibilities
Handling Feedback
Evolution of Software Design Notations
Unified Modeling Language Notation
Model-Driven Architecture
Conclusions
Exercises #
Software Architecture: Intelligence Operations
Architectural Mining
Architectural Iteration
Architectural Judgment
Conclusions
Software Architecture: Psychological Warfare
Alternative Learning
Internal Control
Expectation Management
Psychology of Truth
Software Envisioning
Reference Models and Human Psychology
Example: Reference Selling
Psychology of Ownership
Psychological Akido
Conclusions
Software Architecture: Career Advice
Read, Read, Read
Word of Caution
Making a Name
Becoming an Expert
Conclusions
Architecture Example: Test Results Reporting System
Design Templates and Examples
Glossary of Software Architecture Terminology
Acronyms

Bibliography
Index
Table of Contents provided by Publisher. All Rights Reserved.

What is included with this book?

The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.

The Used, Rental and eBook copies of this book are not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.

PrefaceWhy have a second edition of Software Architecture Bootcamp ? It is safe to say that there have been sweeping changes in the IT industry since the release of the first edition. The era of limitless demand for IT talent is over. The balance of power has shifted away from IT shops and back toward the business and financial areas. No longer will a nifty technical idea spur large investments without a sound business plan and proven management expertise.Companies no longer race to make IT investments to gain competitive edge. Such thinking has been replaced by the need to justify IT investments by demonstrating how greater efficiencies and return on investments will be achieved . Corporations are more willing now than ever to alter their business processes in order to make better use of commercial products or outsourcing.Few people will be successful in the current IT environment for very long simply by developing software. Now, more than ever before, it is absolutely imperative to create additional value. Corporations have also realized that speed in developing software solutions is not beneficial to them if the software does not meet their business needs and if it is not of sufficient quality to be dependable. The business community has come to realize that quality matters, planning matters, and technical leadership that incorporates both matters. Rather than having business analysts and marketing departments rack their brains to figure out how to use their IT group to achieve business advantage, the burden has shifted to the IT group and the expectation that it will have the business acumen to align its focus with that of the organization. While this is not new for some organizations, it is very different than the way IT business was conducted at the height of the IT boom when the "new economy" IT gurus would advocate rushing something to market first in the hope that a market could be identifed or developed for it down the road.In addition to the business environmentthe mainstreammost relevant technologies have changed considerably. Interestingly, while it is a different world, it is also, in many respects, a far simpler world than it was a few years ago. While there have been a number of new technologies introduced, they have been offset by the rapid consolidation of technical approaches and supporting products. Internet technologies are the undisputed king, especially for interoperability between corporations. Microsoft has been wildly successful in its efforts to develop an enterprise platform that rivals the developments occuring in the Java community. During the lengthy recession at the start of this century, IT companies either consolidated or they failed, leaving a more managable number of solutions, most of which were interoperable with one or both of the major enterprise platforms. To a large degree, innovative solutions escaped the middleware layer of the enterprise and focused more on meeting specific business needs where a larger financial payoff exists. In order to maintain technical leadership, software architects need guidance on new technological areas not addressed in the first edition, such as enterprise architecture and model-driven development. The second edition also gives greater emphasis to working with project management to satisfy business objectives.Finally, we felt that there was an opportunity to do a better job with the timeless topics by providing more specifics and introducing greater clarity to the material presented. We were concerned that the first edition might have been misperceived as focusing too much on career advancement. We hope this new edition will make it clear that our primary purpose is to equip software architects with the tools to deliver greater value to projects. Few people remember the architects of the cornerstones of civilizationEgypt, Rome, and New York. However, all remember the

Amazon no longer offers textbook rentals. We do!

Software Architect Bootcamp

Software Architect Bootcamp

0131412272

Summary

Author Biography

Table of Contents

Supplemental Materials

Excerpts