Roles and tasks of the project's Core System

In the process of software project development, it is very important to have a stable core personnel system, which should include at least three roles: managers, technical experts, and business experts. Of course, if conditions permit, the configuration administrator and quality administrator should be configured again.
As managers in the core system, they usually have the following responsibilities:
1. As a window to communicate with customers, we must ensure that the project status is promptly reflected to the customer, and that the customer needs should be promptly and accurately reflected to the development team;
2. Decision-making. Make decisions on some major issues in the project, such as selection of development platforms and technologies, assignment of tasks, and personnel scheduling;
3. Services. As a project manager, you cannot go deep into every development detail of the project. However, you must be a good service provider who must promptly understand and master various requirements during the project process and give appropriate solutions and solutions;
4. Monitoring. Fully grasp the project status and ensure the integrity of the necessity of various quality activities during the operation;
5. Coordination. Rationally allocate tasks and coordinate dependencies between various jobs to ensure proper and orderly job processes.

The core task of a business expert is to build a business model based on the project-oriented application fields. The business model should include the following:
1. system application scenarios (this scenario is used instead of the environment, mainly to distinguish it from the operating environment of the system ). Application scenarios should include the number of users and users oriented to the system, the working environment and location distribution of system users, and the system application time and frequency;
2. Business Process Model. For users, it is important to build a complete workflow that reflects the actual work conditions of users and determine whether the project can be delivered as scheduled and the customer's needs can be correctly displayed. The dependencies and constraints in different links must be clearly and completely described in the business process;
3. Business Data Model. As the Production and Consumption objects of the software system, data flows between different functional modules in the system, or even between different systems, the integrity, consistency, and uniqueness of data flow must be ensured. Therefore, we must fully consider these elements when building a data process;
4. UI interface model. The UI interface is the first portal for users to use the system. Therefore, these interfaces must be reflected to the customer as soon as possible. By presenting or trying out the interfaces to the customer, the user's operation habits and visual information should be collected, continuously improve the UI interface design.

Technical experts must rely on the results of their operations to complete the following tasks.
1. design the project technical implementation solution. This includes the selection of development platforms, deployment environments, and development technologies. As a technical leader, you must not only understand the application scenarios of the system, but also the technical characteristics of the development team;
2. design the overall functional structure of the system. Based on the business process, we need to reasonably convert the business processing process to the computer environment so that the functional characteristics of the system can effectively reflect the requirements of the business process;
3. Data storage design. Based on the business data model, we need to convert material business data to the logical storage structure to ensure that data can flow and be stored normally during processing of related functions.
4. Design and develop functional interface specifications. Function interfaces are portals for interaction between function modules, and they also shield the module's internal details. The interface specification not only ensures coordination between modules, but also provides exit and entry constraints for parallel development of each module. Good interface specifications should be clear, concise, easy to learn and easy to use;
4. Job breakdown. After the design scheme is confirmed, the content of each assignment in the scheme should be reasonably and effectively decomposed, so that appropriate teams or individuals can be selected to complete the corresponding assignment, in order to reduce the risk of mismatch between the difficulty of the job and the ability of the job personnel;
5. Development and Review of basic core modules. When conditions permit, the basic core module must be developed by the core team or individual, so as to ensure smooth implementation of upper-level functions and reduce repeated development of common content, reduce overlapping functions.