System Architect study note _ Chapter 1 _ serialization

1.1.1 concept of System Architect

The three elements of the "architecture" of modern information systems: components, models, and planning; planning is the cornerstone of the architecture and the most important of these three contributions.

The architecture has two layers: The concept layer and the physical layer.

 

1.2.1 Definition of System Architect

Understands, manages, and ultimately confirms and evaluates non-functional system requirements, provides development specifications, and builds the core architecture for system implementation, overall Design of the entire software architecture, key construction, and interfaces, and clarify key technical details.

It mainly focuses on the "technical implementation" of the system, while also considering the "organization and coordination" of the system ".

You must have a sufficient understanding of the development team and be able to evaluate the development team's ability to meet specific functional requirements and resource costs.

 

1.2.2 technical quality of System Architects

Have a good grasp of software engineering standards and specifications.

 

1.2.3 System Architect Management Quality

The System Architect is the creator of an efficient team. It is necessary to make the ideas of all team members as consistent as possible, and define clear, mandatory, and component-based goals for a project as the motivation of the entire team;

Specific methods and models must be provided as ideal technical solutions;

You must avoid hesitation and have a sense of urgency and self-confidence to solve technical problems in a timely manner.

 

1.2.4 coordination between System Architects and other team roles

System analysts, demand analysis, and technical implementation

System Architect, system design, environment-and resource-based system technology implementation

Project Manager, resource organization, and resource implementation

 

Due to conflicting positions, it is impossible to provide development specifications, set up the core architecture for system implementation, clarify technical details, and clear the main difficulties.

Therefore, the architect is positioned between the project manager and the system analyst to clearly plan the objectives for the team.

 

For large enterprises or projects, if one person assumes multiple roles, it is often easy to ignore this phenomenon.

 

1.3 knowledge structure of system architects

It is necessary to distinguish from a large number of conflicting system methods and tools which are valid and which are invalid.

 

1.4 from developers to architects

Summarize your own architecture model and go deep into the industry's summary rules.

 

A few days of training is unlikely to train qualified software architects and vendors for training and certification. The ultimate goal is to cultivate your own market and cultivate a group of Loyal users or product spokespersons, instead of cultivating software architects for China.