System Analyst, System Architect, Project Manager

The "green" Section represents the activities that each role must take into consideration (Note: The system analysts mentioned below share the responsibilities of design ):

First, let's take a look at the differences between architects and system analysts:
1The system analyst must consider all aspects of the system he designed. He is the original author of the system implementation, it also plays a direct role in meeting customers' technical requirements and accepting product costs.
2Architects generally have only a few people in software organizations. They are mainly responsible for evaluating the product architecture and approving the interfaces between subsystems. The evaluation mainly focuses on the quality attributes and cost of the system level, including: whether the current architecture meets the reliability requirements, scalability of the system architecture, reusability, performance, and basic public functions. They must perform initial checks on the system designed by the system analyst. Therefore, they are highly responsible and must be undertaken by experienced people. In other departments of the company and Ivar jacbsonIn the communication, JacobIt is clearly pointed out that the Architecture Committee is not a permanent organization and generally comes from the system analyst of the team. The only permanent position usually has only one chairman. Other members must temporarily come from the front-line of system development, only when they are the most familiar with the basic idea of system development.
3System cost is the easiest thing for architects and system analysts to ignore, and this is also one of their most basic responsibilities.

Next let's take a look at the differences between the system analyst and the Project Manager:
1An unreasonable plan is often blamed on the project manager, but this is not a fact. Planning relies heavily on the components of the system designed by the system analyst to complete the process, and only the system analyst can make an accurate judgment on this. Therefore, the initial version of the plan comes from a system analyst rather than a project manager. The main role of the project manager in this regard is to assist the system analyst in preparing a plan, to help consider personnel and resource input, and to strictly monitor the progress of the project during project implementation.
2Quality goals are developed and planned by system analysts, especially key technical indicators such as performance and reliability, and these first tracking subjects are also system analysts. The role of the project manager is to assist the system analyst in arranging various resources to complete the testing and tracking activities of these objectives.
3Cost is the only factor that requires the attention and strict control of architects, system analysts, and project managers. The reason is very simple.
4Other non-technical factors of the project are basically handled by the Project Manager, including contract, personnel communication, and procurement.