A good software architect must understand key concepts and techniques including MVC, front controller, command, and factory patterns as well as low coupling, services, dependency injection, layers, interfaces, API programming, and concerns separation. They must also grasp ORM patterns like active record and data mapper, data integrity principles, and object relation tools. Additionally, architects need skills in generalization, simple design, clean coding practices, and using understandable names.

1. Minimum Concepts/Techniques a Good Software
Architect Must Grasp and Experience
 MVC – Front Controller – Command – Factory –
Facade – Singleton
by Adil ZEAARAOUI
 Low Coupling – Services – Dependency Injection –
Layers – Interfaces – API Oriented Programming –
COP –Pure Fabrication – Packaging
 AOP – Proxies – Concerns Separation
 ORM – Active Record – Data Mapper – ACID –
DAO – DTO
 Generalization/Abstract Design – Simple Design
 Clean Coding – Clarity – Reflection – Using Real
World Names For Object/Attribute/Method –
Interceptors – Filters