Software Architect Bootcamp / Edition 2 by Thomas J. Mowbray, Raphael Malveau, Raphael Malveau | | 9780131412279 | Paperback | Barnes & Noble
Software Architect Bootcamp / Edition 2
  • Alternative view 1 of Software Architect Bootcamp / Edition 2
  • Alternative view 2 of Software Architect Bootcamp / Edition 2

Software Architect Bootcamp / Edition 2

4.0 1
by Thomas J. Mowbray, Raphael Malveau, Raphael Malveau

ISBN-10: 0131412272

ISBN-13: 9780131412279

Pub. Date: 11/06/2003

Publisher: Prentice Hall

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


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.

Product Details

Prentice Hall
Publication date:
Edition description:
Second Edition
Product dimensions:
7.00(w) x 9.12(h) x 0.72(d)

Table of Contents


1. Introduction.

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.


Customer Reviews

Average Review:

Write a Review

and post it to your social network


Most Helpful Customer Reviews

See all customer reviews >

Software Architect Bootcamp 4 out of 5 based on 0 ratings. 1 reviews.
Guest More than 1 year ago
Of the various software tasks, like writing in assembly, writing in a third generation language,..., the highest level can offer the greatest value added or subtracted. This is the level of architecture, which is covered in this book, recently updated to reflect the latest industry practices. The book tries to help you make strategically correct decisions EARLY in a project. Should you go for a client-server architecture, for example. If so, then it shows how you probably need familiarity with Remote Procedure Calls and the Distributed Computing Environment and with CORBA. Or maybe you should use an Object Oriented technology? Helpfully, the book guides you towards Java and J2EE as a development platform to do this. But it also suggests C# and .NET as an alternative platform. The authors are thoughtful enough to suggest that you steer away from a procedural paradigm if you have a commercial project, though they do give a careful, respectful description of what that approach is. The book covers more topics than just the above. I mentioned those because they may well be the most useful to you. Other important topics are the solidying of UML as the industry's standard design notation, and the use of XML as the most robust format for data interchange. Malveau and Mowbray write in a clear, down to earth style. Yes, they describe the standard jargon, because you need to know this. But the prose thankfully minimises the interspersed sprinkling of acronyms. In other words, you can read entire sections fluidly, and understand them, without having to constantly refer to a glossary of obscure acronyms.