Chapter 13 System Architect
The importance of the system architect position is self-evident, playing a high-level role in the design and development process of a project. The system architect needs to design the system architecture after the relatively stable requirements of the project, and solve the problems such as the development architecture and coding technology of the code in the process of project development. System architect has its importance in the actual project system design process, in the project system development process may need to constantly adjust the details of the architecture, such as the content of the interface, so, the role of the system architect is also throughout the whole project system from design to the completion of such a process.
1. Job responsibilities
The daily work of a system architect is more one-dimensional, but there are important aspects to it. The system architect must be involved in the system development problem at the system requirements stage, and design the overall architecture of the system according to the concept of requirements to design.
L Cooperate with project manager to design system architecture in the process from requirement to design;
L Timely adjust the architecture during project development;
L Explain the problems of system architecture in development to project team members, who are required to understand the whole system architecture;
2, should have knowledge
As the architect of the system, the system architect must be proficient in system-level issues. Understand the bottom of the operating system and the bottom of the development code, and carry out practical application in the actual work process, so that the system architecture can be reused in other projects.
3. Daily work
The work of the system architect is relatively simple, which is basically completed from the project requirements to the design stage, and there is little adjustment on the system architecture in the later stage. The system architect needs to understand the bottom layer of the system daily, and also needs to understand the business aspects of the system, and designs the architecture of the system according to the requirements in the design stage. Therefore, after the design of the system architecture, the system architect is relatively idle.
4. Methods of experience promotion
System architects also need to timely supplement their experience and knowledge in the actual work process, especially with the emergence of new technologies, such as big data and cloud computing, which require new architectural design concepts. The position of system architect also has a certain number of years, and there are exam contents in the software level examination. However, the experience of system architect is summed up in the actual work process, and it is more about self-improvement. There is no relevant training for system architecture design in the market at present.
5. Communication with other characters
The design concept of the system architect communicates with other roles on the project team. It must be involved in the system architecture design from the demand to the design stage, and the technical manager together to do a good job of the system architecture, and in the actual application of timely adjustment. As a result, the system architect mainly communicates with technical managers and software engineers.
6. Books to read
System architects are basically self-learning because they have less training.
L [Software Architecture Design: Programmer to Architect Essential (2nd edition)];
L Microsoft.NET. Framework programming;
97 things a software Architect should know;
L SOA platform architecture;
L WEB foreground architecture design;
L Detailed design of large-scale website architecture;
Words to bear in mind
L Continue to learn and summarize experience in system architecture design;
L Understand new system needs and deal with them in actual architecture design;