U
U
User_3452018-07-19 23:31:45
Career in IT
User_345, 2018-07-19 23:31:45

What should a system architect know?

What knowledge is generally required from a system architect?
What languages ​​are used for software development?
Do you need business knowledge?
What personal qualities are required?
Do I need to have web programming skills?
From what specialty can I switch to a system architect?
What does this specialist mainly do: development or project management?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
D
Doc44, 2018-07-20
@Doc44

https://habr.com/company/technoserv/blog/350170/
Statistics from the job search site (NOT FROM the article)
%D0%A1%D0%B8%D1%81%D1%82%D0%B5%D0%BC%D0%

Y
Yuri Grushevsky, 2018-07-27
@yuriy_grushevskiy

Hey!
I'll tell you from my own experience:
1) A system architect (SA in the future) grows out of programmers or system analysts.
2) A system architect is a person who monitors the overall system architecture (unexpectedly!) And is responsible for the operation of a product or a dedicated block of functionality as a whole, where in general it implies an understanding of the component structure, all integration interactions, all objects and their attributes, business rules and so on. Being a CA, a person should (ideally) answer any questions about where and what to look for in a product, how it is architecturally arranged and how to interact with it - any integration questions, give feedback to the BA on their product development ideas, have the skills to add functionality to a product without disrupting its operation.
2) Knowledge requirements are similar to requirements for an experienced programmer:
a. Programming languages ​​- depending on the vacancy, both back and front;
b. Good knowledge and understanding of database development (predominantly SQL) is required;
in. Good understanding of the development process in general - key roles, development sequence from backlog to completion of testing, etc. Understanding and understanding key methodologies - Agile, Waterfall.
d. Knowledge of UML, BPMN and IDEF notations.
e. In some cases, this is a good knowledge of corporate software (EDMS, CRMs, ERP, etc.).
And much more, depending on the specific needs of the employer.
3) The SA position is highly paid, but has rather high requirements. If you want to become a SA and there is a misunderstanding of his responsibilities - it's definitely too early for you, start with an analyst or a programmer. If you want to hire or open such a vacancy - you need more specifics to answer in detail.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question