Types of software architects
Types of software architects
The enterprise architect handles business-related software decisions that frequently can involve multiple software systems within an organization, spanning several projects teams, and often at more than one site. The Enterprise Architect may seldom see or interact with source code.
An application architect works with a single software application. This may be a full- or a part-time role. The application architect is almost always an active software developer.
Other similar titles in use, but without consensus on their exact meaning, include:
- Solutions Architect, which may refer to a person directly involved in advancing a particular business solution needing interactions between multiple applications. May also refer to an Application Architect.
- System Architect (singular), which is often used as a synonym for Application Architect.
- Systems Architect (plural), which is often used as a synonym for Enterprise Architect or Solutions Architect.
The table below indicates many of the differences between various kinds of software architects:
| Architect Type | Strategic Thinking | System Interactions | Communication | Design |
|---|---|---|---|---|
| Enterprise Architect | Across Projects | Highly Abstracted | Across Organization | Minimal, High Level |
| Solutions Architect | Focused on solution | Very Detailed | Multiple Teams | Detailed |
| Application Architect | Component re-use, maintainability | Centered on single Application | Single Project | Very Detailed |
In the software industry, as the table above suggests, the various versions of architect do not always have the same goals.[1]
Architect(아키텍트)에도 여러종류가 있구나. 나에게 어울리는 타입은 뭘까?