Synopses & Reviews
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.
A hands-on manual to becoming a software architect and improving your craft. The text has been updated to reflect the latest trends in software architecture, allowing you to execute heavyweight or lightweight approaches to architecture and identify the best architectural mode
About the Author
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.
Table of Contents
Defining Software Architecture. The Need for the Software Architect. Goals.
2. 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.
3. 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.
4. 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.
5. Software Architecture: Drill School.
Architecture Versus Programming. Managing Complexity Using Architecture. Systems Integration. Making the Business Case. Architectural Linkage to Software Development. Conclusions.
6. 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.
7. Software Architecture: Jump School.
Process. Creating New Processes. Teamwork. Conclusions.
8. 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 #.
9. Software Architecture: Intelligence Operations.
Architectural Mining. Architectural Iteration. Architectural Judgment. Conclusions.
10. 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.
11. Software Architecture: Career Advice.
Read, Read, Read. Word of Caution. Making a Name. Becoming an Expert. Conclusions.
Appendix A. Architecture Example: Test Results Reporting System.
Appendix B. Design Templates and Examples.
Appendix C. Glossary of Software Architecture Terminology.
Appendix D. Acronyms.
Appendix E. Bibliography.