 | This article needs additional citations for verification. (December 2006) |
 | This article includes a list of general references, but it lacks sufficient corresponding inline citations. (March 2024) |
 Systems architects divide large and complex systems into manageable subsystems that can be handled by individual engineers. | |
| Occupation | |
|---|---|
| Names | Systems architect |
Occupation type | Profession |
Activity sectors | Systems engineering Systems Design Engineering |
| Description | |
| Competencies | user domain knowledge, scientific knowledge, engineering, planning and management skills |
Education required | See education |
The systems architect is an information and communications technology professional. Systems architects define the architecture of a computerized system (i.e., a system composed of software and hardware) in order to fulfill certain requirements. Such definitions include: a breakdown of the system into components, the component interactions and interfaces (including with the environment, especially the user), and the technologies and resources to be used in its design and implementation.
The systems architect's work should seek to avoid implementation issues and readily permit unanticipated extensions/modifications in future stages. Because of the extensive experience required for this, the systems architect is typically a very senior technologist with substantial, but general, knowledge of hardware, software, and similar (user) systems. Above all, the systems architect must be reasonably knowledgeable of the users' domain of experience. For example, the architect of an air traffic system needs to be more than superficially familiar with all of the tasks of an air traffic system, including those of all levels of users.
The title of systems architect connotes higher-level design responsibilities than a systems engineer, software engineer or programmer, though day-to-day activities may overlap.