Mastering Software Architecture: Roles, Patterns, Evaluation, and Risk Management

Software Architecture Overview

Software architecture design covers the whole system from requirements to design, aiming for high efficiency, easy development, maintainability, and simple upgrades.

1. Responsibilities of a Software Architect

Architects are classified into business, domain, technical, project (e.g., J2EE, .NET), and system architects. Their duties include designing the system's foundational structure, bridging business and technology, assisting project planning, guiding system analysis, organizing technical research, providing training, leading innovation, managing technical support teams, defining overall frameworks, and training developers.

2. Required Skills for Architects

Experience in the problem domain and software engineering, leadership to drive technical progress, communication to earn trust, a goal‑oriented proactive attitude, and deep professional knowledge of architecture theories, patterns, and tools.

3. Architecture, Patterns, Reference Models, and Reference Architectures

Definitions of software architecture, architecture patterns, reference models, and reference architectures, and their relationships. The eight classic architectural patterns from Pattern‑Oriented Software Architecture include Layers, Pipes and Filters, Blackboard, Broker, Model‑View‑Controller, Presentation‑Abstraction‑Control, Microkernel, and Reflection.

4. Design Architecture

Successful object‑oriented systems share a strong architectural vision and iterative incremental development. Architecture‑driven design (ADD) uses quality‑attribute scenarios to guide design.

5. Architecture Evaluation – ATAM

ATAM evaluates architectures by identifying quality‑attribute scenarios, classifying decisions as risky or safe, and analyzing trade‑offs through stakeholder workshops.

6. Architecture Risk Management

Risks include changing requirements, insufficient technical understanding, lack of industry research, inexperience, heavy innovation, missing standards, and poor executability. Mitigation strategies involve solidifying requirements, comprehensive prototypes, clear architecture specifications, validating executability, and balancing experience with innovation.

7. Practical Architecture Views

Four views—conceptual, module, execution, and code—help prioritize, analyze trade‑offs, and ensure completeness. Global analysis considers organizational, technical, and product factors.

8. Domain‑Specific Frameworks

Frameworks are categorized into enterprise application, middleware integration, and system infrastructure, with examples such as Amulet, IBM SanFrancisco, OmniBuilder, ACE, and CORBA.

9. Enterprise Application Architecture Patterns

Discusses layered architecture (presentation, domain, data source), concurrency control, transaction management, distribution strategies, and integration methods (file transfer, shared database, RPC, messaging).

10. Common Architectural Styles and Technologies

Mentions MVC, C/S, B/S, HTTP, SOAP, REST, SOA, SaaS, Open API, open‑source stacks (Struts, Spring, Hibernate), and client presentation technologies (Windows controls, embedded WebBrowser, Flash).