Forum Posts

Apr 10, 2022
This article is a review of some situations encountered by the author when building a data sharing system. The experience and lessons summed up from the perspectives of the product layer and the development layer are shared with you! 1. Product introduction 1. Data Sharing System The data sharing system is a tool-type product that realizes data uploading and downloading to the cloud. The first phase mainly realizes the tasks of downloading structured data and unstructured data to the cloud. At the same time, it can set regular schedule updates for the applied tasks. Product users: those who demand structured data and unstructured data in the cloud; Product and service purchase decision maker: Technology Section of job title email list the Information Center of the General Administration; Product functions: data source registration, cloud task application, approval process, cloud data, scheduling update and other functions; User's main appeal point: to ensure data security and realize different types of data sharing on the cloud; Product prototype: 5 modules, each module contains several information flows; 2. Five modules of product prototype User grouping - users can apply for and create tasks in the form of groups; Custom data source - register the data source you want to share with the autonomous system, and realize data sharing under a specific data source by selecting the corresponding data source; Data sharing in the form of tasks; Approval workflow function - a strict approval process is required for shared tasks to protect data security; System-wide auditing - to ensure the safe transmission and sharing of data, and to conduct log audits on tasks and actions in the system; 2. Product review The first phase of the current product is coming to an end. Looking back on the entire project process, some functional refactorings encountered in the middle can be completely avoided. The first phase of the system is coming to an end. After reviewing some situations encountered in the project, and summarizing some experience, the following are the lessons learned from different perspectives: 1. Product layer 2.1.1 Communicate more with customers to understand the business background behind the functions Only by continuously communicating with customers and gradually understanding the customer's use of the system and the business background of its functions, can the system functions truly meet customer needs. After the project was launched, he went to the client as soon as possible and conducted a systematic understanding of the needs with the client. According to the first communication, the entire business process was first sorted out; at the same time, the corresponding competing products were searched according to the relevant information obtained. After the process is determined, confirm the completeness of the entire process with the customer again. In this way, the process, function points, system module classification, initial prototype, prototype confirmation, adjustment prototype, reconfirmation, etc., are constantly communicated with customers, and they explore the bottom-level needs again and again, and get familiar with the customer's business scenarios step by step. Due to the short cycle of the entire project, it is necessary to confirm the system functions as soon as possible, and seize the time to finalize the entire design. The functions of the product include data source management, user group management, task management, approval management, etc. Task management is the core of the entire product.