profession of systems architect
Posted by Jackprabha on 02/19/2020
The networker sees the Internet as a combination of routers connected by communication channels and terminal devices connected in the “last mile”. The infrastructure manager is aware of the availability of telecommunications, but gives priority to where the content transmitted over the network is stored and how it is generated. Developers are often stuck with the framework of environments (development, test, pre-sales, finished products), etc. The system architect is obliged to see and understand all of the above persons, and the user who leafs through the social network feed, the businessman who owns this social network, and a lot of people involved in the process. In general, he is obliged to understand what and from whom he needs.
In relation to system architects, there are much more different hypostases. In the simplest case, an "advanced" engineer is a specialist in a particular system and knows what can be built from it and where it can be applied. Yes, he is sometimes called a system architect, but he is a "warrior of light" exclusively in his field. This field can be a system / systems of a specific supplier or systems that are produced by many suppliers, but with their own characteristics (for example, switching systems or database management systems). In some foreign companies, such specialists are called certified engineers, while in our country they are called leading engineers.
The main content of the profession of systems architect is a systems approach and systems engineering thinking. In a huge number of projects, many heterogeneous systems and various solutions usually coexist, which implies the presence of specialists of a higher level. Accordingly, systems engineering thinking is the use of a systems approach in engineering. In turn, systems engineering can be defined as a set of ways to create a successful system (i.e., satisfying all the needs of customers, users and other stakeholders) based on an interdisciplinary approach that involves working with various engineering specialties.
A system can be anything from a complex of information systems to entire industrial enterprises (industrial groups), including technological and production processes, logistics, business processes, as well as equipment and buildings. And if for a leading engineer the system is, say, a server farm, integrated into a computer complex by means of infrastructure software, then for a system architect, a system is a working complex, where such a farm is a small unit. For example, a large shopping center operated by a company whose staffing is optimally staffed, the ratio of its own staffing and contracting / outsourcing is optimally selected, all the necessary systems have been designed and implemented (information, engineering, parking, security systems ...), an optimal plan of interaction with tenants has been developed ... Moreover, the IT infrastructure here is far from the first in terms of tasks. In other words, a system architect solves a business problem, and a system for him is an enterprise, organization, industry ... with all processes, people and mechanisms.