Shulou(Shulou.com)06/03 Report--

This article introduces the knowledge of "what are the main responsibilities of an architect". Many people will encounter such a dilemma in the operation of actual cases, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

The architect has four main responsibilities:

1. Confirm the requirements

In the project development process, the architect is involved after the completion of the requirements specification, which must be approved by the architect. Architects need to communicate repeatedly with analysts to ensure that they have a complete and accurate understanding of user needs.

2. System decomposition

According to the needs of users, the architect breaks down the system as a whole into smaller subsystems and components, thus forming different logical layers or services. The architect then determines the interfaces of each layer and the relationship between the layers. The architect should not only layer the whole system and decompose it vertically, but also divide the same logical layer into blocks and decompose it horizontally.

The skills of software architects are basically reflected in this, which is a relatively complex task.

3. Technology selection

Through a series of decomposition of the system, the architect finally forms the overall architecture of the software. The choice of technology mainly depends on the software architecture.

Does Web Server run on Windows or Linux? Is the database MSSql, Oracle, or Mysql? Do you need to use lightweight frameworks such as MVC or Spring? Does the front end use rich client or thin client? Similar work needs to be proposed and evaluated at this stage.

The architect's selection of products and technologies is limited to evaluation and has no decision, and the final decision rests with the project manager. The technical proposal proposed by the architect provides important reference information for the project manager, who will weigh the project budget, human resources, schedule and other actual situation, and finally confirm it.

4. Develop technical specifications

The architect is a technical authority in the project development process. He needs to coordinate all developers, always communicate with developers, and always ensure that developers implement various functions in accordance with its architectural intentions.

The most important form of communication between architects and developers is the technical specification, which can be expressed in UML views, Word documents, Visio files, and so on. The technical specification provided by the architect ensures that developers can observe and understand their own subsystems or modules from different angles.

Architects need to communicate not only with developers, but also with project managers, requirements analysts, and even end users. Therefore, for architects, there are not only technical requirements, but also interpersonal communication requirements.

The misunderstanding of the architect

1. The architect is the project manager

The architect is not a project manager. The project manager focuses on budget control, time schedule control, personnel management, external contact and coordination, etc., with management functions. In general, in small projects, it is common for project managers and architects.

2. The architect is responsible for requirements analysis.

The architect is not a requirements analyst. The job of the requirements analyst is to collect and analyze requirements and keep in touch with end users and product managers. The architect only reviews and confirms the final requirements and puts forward the unclear and incomplete parts of the requirements, and he will keep in touch with the requirements analyst at all times. The architect is a technical expert, not a business expert.

3. Architects never write code

This is a controversial issue. At present, there are two views:

Viewpoint 1: architects do not write code, writing code is purely manual, and architects are overqualified for writing code. The architect gives various views of UML to the developer, and if there is any ambiguity, he can communicate with the architect at any time.

Viewpoint 2: architects originally come from programmers, but at a higher level than programmers, and the only thing more than programmers is experience and knowledge, so architects can't avoid writing code.

Personally, I think these two statements are related to the origin and environment of the architect.

Architects are first of all a technical role, so they must come from a group of technicians, such as system architects, mostly from operations and maintenance staff, and may not write much code, or cannot write beautiful code. Software architects are mostly from programmers, with programmer blood and feelings, so in the project development process, may write some core code. Our ideal is that architects don't have to write code, but in fact sometimes it's too ideal. Whether the architect writes code or not may depend on the size of the company, the culture, the quality of the developers, and so on.

That's all for "what are the main responsibilities of an architect?" Thank you for your reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.