Software Architect Bootcamp

Description

• Copyright 2001
• Edition: 1st

• Book
• ISBN-10: 0-13-027407-0
• ISBN-13: 978-0-13-027407-6

• Become a great software architect—hands-on!
• Define architectures that leverage today's best design patterns
• Maximize scalability and technical flexibility
• Lead your technical organization to successful implementation

Your hands-on "field manual" for becoming a great software architect!

This hands-on "field manual" gives developers the essential skills they need to survive and thrive as software architects! You'll find insightful, real-world coverage of everything from design patterns to prototyping, business case development to leadership.

Leading software architects Raphael Malveau and Thomas Mowbray share profound insights and practical solutions for all the key challenges of architectures using objects, components, and distributed Internet computing, showing how to avoid time-consuming pitfalls and costly errors. You'll master proven methods for:

• Identifying the best architectural model for any project
• Executing heavyweight or lightweight approaches to software architecture
• Addressing scalability and long-term business flexibility
• Making the most of abstraction, refactoring, and architectural prototyping
• Leveraging superior design patterns to improve your implementations

With hands-on exercises, real-life war stories, and a take-no-prisoners attitude, Software Architect Bootcamp won't just help you become a great software architect: it'll help you become a true technical leader of your organization.



Sample Content

Downloadable Sample Chapter

Click here for a sample chapter for this book: 0130274070.pdf

Table of Contents

Preface.


Acknowledgments.


1. Introduction.

Advice for Software Architects. Software Architecture as a Discipline. Design Patterns and Software Architecture. Conclusions. Exercises.

2. Software Architecture: Basic Training.

Software Paradigms. Open Systems Technology. Client Server Technology. Software Application Experience. Technology and Application Architecture. Applying Standards to Application Systems. Distributed Infrastructures. Conclusions. Exercises.

3. Software Architecture: Going to War.

Software Architecture Paradigm Shift. Doing Software Wrong. Doing Software Right: Enterprise. Bottom Line: Time, People, and Money. Conclusions. Exercises.

4. Software Architecture: Drill School.

Architecture versus Programming. Managing Complexity Using Architecture. Systems Integration. Making the Business Case. Architecture Linkage to Software Development. Architectural Software Notation. Conclusions. Exercises.

5. Leadership Training.

Leadership Is a Necessary, Learnable Skill. The Architect as Team Builder. Always Insist on Excellence in Deliverables. Architect's Walkthrough. Conclusions. Exercises.

6. Software Architecture: Jump School.

Process. Creating New Processes. Teamwork. Conclusions. Exercises.

7. Communications Training.

Communications Challenges. Responsibility-Driven Development. Communication Responsibilities. Handling Feedback. Exercises.

8. Software Architecture: Intelligence Operations.

Architecture Mining. Architecture Iteration. Architecture Judgment. Conclusions. Exercises.

9. Software Architecture: Psychological Warfare. Alternative Learning. Internal Control. Expectation Management. Psychology of Truth. Perception Is Not Reality. Exploiting Human Weaknesses. Example: Reference Selling. Psychology of Ownership. Psychological Akido: Guarding. Intellectual Akido. Conclusions. Exercises.


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.


Index.

Preface

Preface

Software architecture is an emerging discipline and an exciting career path for software professionals. We encourage both new and experienced practitioners to read this book as an aid to becoming better software architects. You may have noticed that most software books today do not say much about software architecture. Here, in this volume, we've concentrated the knowledge that you need to be the most effective architect possible.

As co-authors, we have lived through the experience of graduating from "member of technical staff" developers to becoming practicing software architects at the most senior levels of our respective companies. We are technical people, not managers, and we enjoy the technical nature of our work. We enjoy parity of salary and benefits with the senior managers at our respective firms. In other words, we are none-the-worse-for-wear as a consequence of choosing a software architecture career. We think that many of our readers would like to gain from our experience. Hence this book.

This is more than a book about software architecture. It is a field manual that can train you. We choose the pseudomilitary style, because it embodies an essential attitude. As a software architect, you need many survival skills—some technical, some political, some personal. While neither author has military experience, we have seen software architecture become a battleground in many ways. It is a battleground of ideas, as developers compete to forward their own comcepts. It is a battle ground for control of key design decisions that may be overruled by managers or developers, perhaps covertly. It is a battleground with many risks, since architects are responsible for a much wider range of technical and process risks than most managers or individual developers.

If you are a practicing software architect, we know that you are a busy professional. After buying this book, we would suggest that you peruse the table of contents and the index for topics that are new to you. Focus on those sections first. When you have time, we suggest that you attempt a cover-to-cover read-through, to familiarize yourself with all of the covered topics and terminology.

If you are new to architecture and want to become a software architect, we suggest that you do a cover-to-cover read-through beginning with the first chapter. Work the exercises provided, which will add an experiential learning element to your experience base.

Raphael Malveau
Thomas J. Mowbray, Ph.D.
McLean, Virginia, U.S.A.



Updates

Submit Errata

