Book description
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.
Table of contents
- Copyright
- About Prentice Hall Professional Technical Reference
- Preface
- One. Introduction
-
Two. Military History
- 2.1. Software Architecture Approaches
- 2.2. The Architectural Paradigm Shift
- 2.3. The Need for Software Architecture
- 2.4. Zachman Framework
- 2.5. Reference Model for Open Distributed Processing
- 2.6. Enterprise Architecture Standards
- 2.7. Design Patterns
- 2.8. AntiPatterns
- 2.9. Software Design-Level Model
- 2.10. Conclusions
- 2.11. Exercises
-
Three. Software Architecture: Basic Training
- 3.1. Object-Oriented Technology
- 3.2. Component-Oriented Technology
- 3.3. Technology Ownership
- 3.4. Client-Server Technology
- 3.5. Internet Technology
- 3.6. Architectural Layers and When to Use Them
- 3.7. Software Application Experience
- 3.8. Technology and Application Architecture
- 3.9. Applying Standards to Application Systems
- 3.10. Distributed Infrastructures
- 3.11. Conclusions
- 3.12. Exercises
-
Four. Software Architecture: Going to War
- 4.1. Software Architecture Paradigm Shift
- 4.2. Doing Software Incorrectly
-
4.3. Doing Software Correctly: Enterprise Architecture Development
- Architecture-Centered Process
- Step 1: System Envisioning
- Step 2: Requirements Analysis
- Step 3: Mockup Prototype
- Step 4: Architectural Planning
- Step 5: Architectural Prototype
- Step 6: Project Planning
- Step 7: Parallel Development
- Step 8: System Transition
- Step 9: Operations and Maintenance
- Step 10: System Migration
- 4.4. Bottom Line: Time, People, and Money
- 4.5. Conclusions
- 4.6. Exercises
- Five. Software Architecture: Drill School
- Six. Leadership Training
- Seven. Software Architecture: Jump School
- Eight. Communications Training
- Nine. Software Architecture: Intelligence Operations
-
Ten. Software Architecture: Psychological Warfare
- 10.1. Alternative Learning
- 10.2. Internal Control
- 10.3. Expectation Management
- 10.4. Psychology of Truth
- 10.5. Software Envisioning
- 10.6. Reference Models and Human Psychology
- 10.7. Example: Reference Selling
- 10.8. Psychology of Ownership
- 10.9. Psychological Akido
- 10.10. Conclusions
- 10.11. Exercises
- Eleven. Software Architecture: Career Advice
-
A. Architecture Example: Test Results Reporting System
- A.1. Introduction
- A.2. Component Interoperability Challenge
- A.3. Target Architecture for the TRRS
- A.4. Target Enterprise Viewpoint
- A.5. Target Information Viewpoint
- A.6. Target Technology Viewpoint
- A.7. Prototype Implementation
- A.8. Prototype Computational Viewpoint
- A.9. TRRS Terminology
- A.10. Use Case Definitions
- A.11. Core Workflows
- A.12. Information Model
- A.13. Conclusions
-
B. Design Templates and Examples
-
B.1. Conceptual Design
- Section 1 Goal
- Section 2 Conceptual Overview
- Section 3 Responsibilities
- Section 4 Architectural Level
- Section 5 Classes and Objects, Class Semantics, and Class Relationships
- Section 6 Description of Features, Data Types, and Constraints
- Section 7 How the Design Addresses Relevant Use Cases and Requirements
-
B.2. Relationship Service Conceptual Design
- Section 1 Goal
- Section 2 Conceptual Overview
- Section 3 Responsibilities
- Section 4 Architectural Level
- Section 5 Classes and Objects, Class Semantics, and Class Relationships
- Section 6 Description of Features, Data Types, and Constraints
- Section 7 How the Design Addresses Relevant Use Cases and Requirements
- B.3. High-Level Design
- B.4. Relationship Service High-Level Design
-
B.1. Conceptual Design
- C. Glossary of Software Architecture Terminology
- D. Abbreviations
- E. Bibliography
Product information
- Title: Software Architect Bootcamp, Second Edition
- Author(s):
- Release date: December 2003
- Publisher(s): Pearson
- ISBN: 0131412272
You might also like
book
Software Architect Bootcamp
Become a great software architect—hands-on! Define architectures that leverage today's best design patterns Maximize scalability and …
book
12 Essential Skills for Software Architects
Master the Crucial Non -Technical Skills Every Software Architect Needs! Thousands of software professionals have the …
book
Software Architecture by Example: Using C# and .NET
Design system solutions using modern architectural patterns and practices. This book discusses methods to keep a …
video
Software Architecture Superstream Series: Soft Skills Are the Hardest Part
Developers and architects like to solve technical problems, not people problems. However, as Gerald Weinberg was …