The responsibility of the software architect

Architects are divided into the following categories: Business architect, subject area architect, Technical architect, Project architect (Java EE architect). NET architects, etc.), system architects.

1, the architect's responsibilities are mainly embodied

The architect's job is to design the infrastructure of a corporate system and provide guidelines on how to build and maintain the system. In particular, the architect's responsibilities are reflected in the following areas:

1), responsible for the company's system architecture design, research and development work.

2), undertake the bridge function from the business to the technology transformation.

3), assist the project manager to develop the project plan and control the project progress.

4), responsible for assisting and directing the system analysis to carry out the design work.

5), responsible for the organization of Technical research and tackling the work.

6), responsible for the organization and management of the company's internal technical training work.

7), responsible for organizing and leading the company's internal staff research and project-related new technologies.

8), management technology support team and to the project, product development and implementation team to provide technical support.

9), understand the business requirements of the system, develop the overall framework of the system (including, technical framework and business framework).

10), the system framework related technology and business training, to guide the development of developers. and solve various problems in the system development and operation.

2, the architect must have the skills

Experience: Includes both experience in problem areas (through thorough understanding of requirements), as well as experience in the field of software engineering. For an architecture team, these quality requirements can be individually borne by each team member, but at least one architect can grasp the overall project.

Leadership: the ability to drive technical progress across teams, and to make critical decisions under pressure and follow them through. To be more efficient, the architect and project manager must work closely together. The architect is primarily responsible for solving technical problems, and the project manager is responsible for solving administrative problems. The architect must be empowered to make decisions on technical issues.

Communication: The ability to win the trust of others to persuade, motivate and guide them. The architect cannot lead by order, but must win the approval of the other people in the project. In order to improve efficiency, the architect must win the respect of the project team, project manager, customer, user group and management team.

Goal-centric, proactive: relentless pursuit of results. Architects are the technical drivers that drive the development of a project, rather than a dreamer. In his career, successful architects have always had to make compromises in the context of uncertainty and stress. The architect can only be successful in the project by focusing on what they are doing.

Major: Proficient in the theory, practice and tools of architectural design, and master a variety of reference architectures, major reusable architecture mechanisms and patterns (such as the Java EE Architecture, etc.). Has all the skills of a system designer, but involves a broader, more abstract level.

The responsibility of the software architect