Digital supply and sales society software platform building method

Abstract

The invention discloses a digital supply and sales society software platform building method. According to the invention, through automation and optimization of the business processes of the supply and sales agency, such as commodity management, order processing and inventory management, the operation efficiency can be significantly improved and human errors can be reduced. The user requirements are known and met, a friendly operation interface is designed, the satisfaction degree of the user and the attraction of the platform can be improved, and therefore the user stickiness and the market share are increased. By implementing strict data security measures, such as an encryption technology and a network security policy, sensitive data can be protected from unauthorized access or leakage, benefits of users and enterprises are maintained, dependence on manual operation can be reduced through collection and analysis of service data, automation of a supply and sale society and integration of various service processes, and the safety of the users and the enterprises is improved. Therefore, the long-term operation cost is reduced.

Description

Technical Field

[0001] The present invention belongs to the technical field of digital supply and marketing cooperatives, and specifically relates to a method for building a software platform for digital supply and marketing cooperatives. Background Art

[0002] The supply and marketing cooperative is a unique form of economic organization in China. With the development of technology, the traditional supply and marketing cooperative model is gradually being replaced by the digital supply and marketing cooperative. The digital supply and marketing cooperative is a new type of supply and marketing cooperative that uses modern information technology means to innovate the operation mode of the supply and marketing cooperative, improve its operation efficiency and service quality. The digital supply and marketing cooperative establishes an e-commerce platform, transfers offline goods and services to the online, and realizes seamless connection between online transactions and offline distribution. Consumers can purchase various goods and services through the e-commerce platform of the digital supply and marketing cooperative at any time and place, without having to go to the physical store in person, which greatly saves time and energy. In addition, the digital supply and marketing cooperative also uses big data and artificial intelligence technologies to analyze and predict consumers' purchase behaviors, providing decision-making support for the procurement and sales of the supply and marketing cooperative. Through precise procurement and sales, the digital supply and marketing cooperative can reduce inventory costs and improve the efficiency of capital use.

[0003] However, the automation degree of the business process of the common digital supply and marketing cooperative is not high enough, resulting in poor convenience in the use of the entire system. Summary of the Invention

[0004] The purpose of the present invention is to provide a method for building a software platform for digital supply and marketing cooperatives in order to solve the above-mentioned problems.

[0005] The technical solution adopted by the present invention is as follows: A method for building a software platform for digital supply and marketing cooperatives, characterized in that: the building method includes the following steps:

[0006] S1: Conduct requirements analysis: Analyze the business requirements of the supply and marketing cooperative, including commodity management, order processing, inventory management, logistics tracking, etc. Investigate user requirements, understand the user groups and usage habits of the supply and marketing cooperative. Determine the function modules, performance requirements and security requirements of the platform;

[0007] S2: Design the digital supply and marketing cooperative system: Select a suitable system architecture through architecture design, including microservices, server-side rendering;

[0008] Conduct database design: Design a database model according to business requirements and determine the data storage scheme;

[0009] S3: Design the management platform and the online supply and marketing mall.

[0010] S4: Conduct technology selection. Based on project requirements and team skills, select appropriate programming languages and frameworks, such as Java / Spring Boot, Node.js / Express. Consider the licenses, costs, and technical support of open-source software and commercial software.

[0011] S5: Establish coding specifications: Develop unified coding specifications, including naming rules, code structure, and comment standards. Use code review tools, such as Git, GitHub, or Bitbucket, to ensure code quality and consistency.

[0012] S6: Adopt modular design. Split the system into multiple independent modules to improve development efficiency and maintainability. Use a version control system to manage code changes and version iterations.

[0013] S7: Define interfaces: Use API design specifications, such as OpenAPI / Swagger, to define clear interface documents. Develop and test RESTful APIs or GraphQL interfaces to ensure data exchange and communication between modules.

[0014] S8: Deploy and go live with the digital supply and marketing cooperative software platform: Environment preparation: Configure the production environment, including servers, networks, and storage resources. Install and configure necessary software and middleware, such as web servers, databases, and caching systems.

[0015] Deployment script writing: Write automated deployment scripts. Use container technologies such as Docker and Kubernetes to simplify deployment and scaling. Design blue-green deployment or canary release strategies to ensure smooth transitions and rollback capabilities.

[0016] Pre-go-live testing: Conduct comprehensive pre-go-live testing, including functional testing, performance testing, and security testing. Ensure that the system meets the go-live standards and business requirements.

[0017] S9: After testing, go live with the digital supply and marketing cooperative software platform, and the entire construction process of the digital supply and marketing cooperative software platform can be completed.

[0018] In a preferred embodiment, in step S1, during the requirement analysis process, hold meetings with key stakeholders of the supply and marketing cooperative to understand their business processes. Analyze existing information systems to determine the integration points of the new system. During the requirement analysis process, collect users' usage habits and requirements through questionnaires, interviews, etc. Create user personas during the requirement analysis process to understand the specific requirements of different user groups. Write a detailed requirement document based on the collected information during the requirement analysis process. Determine functional modules, performance indicators, and security requirements.

[0019] In a preferred embodiment, in step S2, the specific steps include:

[0020] 1. Requirements analysis: Collect requirements: Communicate with the business team to understand business processes, user requirements, market trends, etc. Determine business goals: Define the business goals that the system needs to achieve, such as performance, availability, consistency, etc.

[0021] 2. Architecture style selection: Evaluate business characteristics: Select a suitable architecture style based on the characteristics of business requirements (such as transaction volume, data complexity, user interaction, etc.). Microservices: Suitable for scenarios with high business complexity, rapid iteration requirements, and relatively large team sizes. Event-driven: Suitable for scenarios of asynchronous processing and decoupling of system components. Layered architecture: Suitable for scenarios where the business is relatively stable and the coupling degree between system components is relatively low. Technical feasibility analysis: Consider the existing technology stack, the technical capabilities of the team, and available technical solutions in the market.

[0022] 3. Architecture design: Component decomposition: Break down the system into multiple components or services with high cohesion and low coupling. Define interfaces: Clearly define the communication interfaces between components to ensure clear and controllable interaction between components. Data management: Design a data storage solution, including database selection, data synchronization, and backup strategies. Security design: Ensure data security and privacy protection, including authentication, authorization, and encryption mechanisms.

[0023] 4. Scalability and maintainability design: Modularity: Design modular components for easy independent update and replacement. Service orientation: Improve the reusability of the system through service orientation and reduce repetitive development. Automation: Implement automated testing, deployment, and monitoring to improve the stability and maintainability of the system. Monitoring and logging: Integrate a logging management and monitoring system for easy problem tracking and performance analysis.

[0024] 5. Technology selection: Framework selection: Select a suitable development framework and tools based on the architecture style. Middleware selection: Select suitable middleware to support message queues, caches, databases, etc.

[0025] 6. Architecture verification: Prototype development: Develop a minimum viable product (MVP) to verify the feasibility of the architecture design. Performance testing: Conduct stress testing and performance testing to ensure that the system meets the performance requirements. Security audit: Conduct a security audit to ensure that the system design complies with security standards.

[0026] 7. Documentation and training: Architecture documentation: Write detailed architecture documentation, including component responsibilities, interface definitions, and data flows; Team training: Provide training on the architecture and technology to the development team to ensure that the team can understand and follow the architecture design;

[0027] 8. Continuous Iteration, Feedback Mechanism: Establish a feedback mechanism to collect problems and improvement suggestions during system operation, and continuously optimize: Continuously optimize the architecture design and system implementation based on feedback and technological development.

[0028] In a preferred embodiment, in the step S2, the specific process steps for database design include:

[0029] 1. Requirement Analysis, Collect Requirements: Communicate with the business team to understand business processes, data entities, data relationships, and business rules. Determine Business Goals: Define the transaction types, data volumes, query requirements, and performance metrics that the database needs to support.

[0030] 2. Conceptual Design, Based on requirement analysis, draw an entity-relationship diagram, define entities, attributes, and relationships between entities, and normalize: Normalize the ER model to reduce data redundancy and update anomalies.

[0031] 3. Logical Design, Data Model Selection: Select a suitable data model, such as a relational model, document model, key-value model, etc. Table Structure Design: Convert the ER model into a specific table structure, define fields, data types, primary keys, foreign keys, etc. Index Strategy: Design indexes according to query requirements to optimize query performance.

[0032] 4. Physical Design, Storage Engine Selection: Select a suitable database storage engine according to business requirements, such as InnoDB, MyISAM, Tokyo Cabinet, etc. Partition Strategy: For large databases, consider partition strategies to improve performance and management convenience. File System Configuration: Configure the database's file system to optimize disk I / O performance.

[0033] 5. Database Security Design, User Permission Management: Design a user permission management system to ensure data security and compliance. Data Encryption: Encrypt sensitive data for storage to protect user privacy.

[0034] 6. Backup and Recovery Strategy, Backup Plan: Design a regular backup plan, including full backups and incremental backups. Recovery Testing: Conduct recovery tests regularly to ensure the availability of backup data.

[0035] 7. Performance Optimization, Performance Testing: Conduct stress tests and performance tests on the database to evaluate system bottlenecks. Query Optimization: Optimize slow queries to improve database performance.

[0036] 8. Data Migration and Synchronization, Migration Plan: If an old database migration is involved, formulate a detailed migration plan. Data Synchronization: For distributed systems, design a data synchronization mechanism to ensure data consistency.

[0037] 9. Documentation and Training, Database Documentation: Prepare a detailed database design document, including data dictionary, ER diagram, and index strategy. Team Training: Provide training on database management and maintenance for the development team and the operation and maintenance team.

[0038] 10. Continuous Iteration, Monitoring and Tuning: Continuously monitor the database performance and perform tuning according to the actual situation.

[0039] In summary, due to the adoption of the above technical solutions, the beneficial effects of the present invention are as follows:

[0040] 1. In the present invention, by automating and optimizing the business processes of the supply and marketing cooperatives, such as commodity management, order processing, and inventory management, the operation efficiency can be significantly improved and human errors can be reduced. Understanding and meeting user needs and designing a user-friendly operation interface can enhance user satisfaction and the attractiveness of the platform, thereby increasing user stickiness and market share. By implementing strict data security measures, such as encryption technology and network security policies, sensitive data can be protected from unauthorized access or leakage, safeguarding the interests of users and enterprises. By collecting and analyzing business data, the platform can provide insights and reports for management, supporting more informed business decisions and strategic planning. Through supply and marketing cooperative operation and maintenance monitoring and regular maintenance, the high availability and stability of the system can be ensured, system failures and downtime can be reduced, and service quality can be improved. The modular system design and flexible technology selection enable the platform to adapt to business expansion and changes, supporting long-term sustainable development. The unified supply and marketing cooperative coding specifications and code review processes can promote the collaboration and knowledge sharing of the development team, improving development quality and efficiency. By automating and integrating various business processes of the supply and marketing cooperatives, the dependence on manual operations can be reduced, thereby lowering long-term operating costs.

[0041] 2. In the present invention, by combining mobile devices with the computer side, the overall structure and functions of the platform are designed around six main functions, namely, online supply and marketing mall, agricultural product bidding, agricultural assistance services, supply and marketing cooperative goods allocation, order management, and employee management. The WeChat mini-program user side is targeted at farmers and purchasers, and the web management side is targeted at branch supply and marketing cooperatives and the head supply and marketing cooperative. The development and application of the agricultural branch supply and marketing cooperative management platform are expected to accelerate the circulation of agricultural products, promote the development of traditional agriculture towards modern agriculture, improve the management efficiency of grass-roots supply and marketing cooperatives, respond to national policies, develop new supply and marketing cooperatives that meet the needs of the times, and promote rural revitalization. Detailed Implementation Modes

[0042] In order to make the objectives, technical solutions, and advantages of the present invention clearer and more understandable, the present invention will be further described in detail below in conjunction with embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0043] Embodiment:

[0044] A method for building a digital supply and marketing cooperative software platform, the building method comprising the following steps:

[0045] S1: Conduct requirements analysis: Analyze the business requirements of the supply and marketing cooperative, including commodity management, order processing, inventory management, logistics tracking, etc. Investigate user requirements to understand the user groups and usage habits of the supply and marketing cooperative. Determine the functional modules, performance requirements, and security requirements of the platform;

[0046] S2: Conduct digital supply and marketing cooperative system design: Select a suitable system architecture through architecture design, including microservices and server-side rendering;

[0047] Conduct database design: Design a database model according to business requirements and determine the data storage scheme;

[0048] S3: Design the management platform and the online supply and marketing mall

[0049] S4: Conduct technology selection. According to project requirements and team skills, select appropriate programming languages and frameworks, such as Java / Spring Boot, Node.js / Express, and consider the licenses, costs, and technical support of open-source software and commercial software.

[0050] S5: Formulate coding specifications: Formulate unified coding specifications, including naming rules, code structure, and comment standards. Use code review tools, such as Git, GitHub, or Bitbucket, to ensure code quality and consistency;

[0051] S6: Adopt modular design, split the system into multiple independent modules to improve development efficiency and maintainability. Use a version control system to manage code changes and version iterations;

[0052] S7: Define interfaces: Use API design specifications, such as OpenAPI / Swagger, to define clear interface documents. Develop and test RESTful APIs or GraphQL interfaces to ensure data exchange and communication between modules;

[0053] S8: Deploy and go live the digital supply and marketing cooperative software platform: Environment preparation: Configure the production environment, including servers, networks, and storage resources. Install and configure necessary software and middleware, such as web servers, databases, and cache systems.

[0054] Deployment script writing: Write automated deployment scripts, use container technologies such as Docker and Kubernetes to simplify deployment and scaling. Design blue-green deployment or canary release strategies to ensure smooth transition and rollback capabilities.

[0055] Pre - launch testing: Conduct comprehensive pre - launch testing, including functional testing, performance testing, and security testing. Ensure that the system meets the launch standards and business requirements;

[0056] S9: After the testing is completed, launch the Digital Supply and Marketing Cooperative software platform, and the entire construction process of the Digital Supply and Marketing Cooperative software platform can be completed.

[0057] In step S1, during the process of requirement analysis, hold meetings with the key stakeholders of the supply and marketing cooperative to understand their business processes. Analyze the existing information systems to determine the integration points of the new system. During the process of requirement analysis, collect users' usage habits and requirements through questionnaires, interviews, etc. Create user personas during the process of requirement analysis to understand the specific requirements of different user groups. Write a detailed requirement document based on the collected information during the process of requirement analysis. Determine the functional modules, performance indicators, and security requirements.

[0058] In step S2, the specific steps include:

[0059] 1. Requirement analysis: Collect requirements: Communicate with the business team to understand business processes, user requirements, market trends, etc. Determine business goals: Clearly define the business goals that the system needs to achieve, such as performance, usability, consistency, etc.

[0060] 2. Architecture style selection: Evaluate business characteristics: Select a suitable architecture style according to the characteristics of business requirements (such as transaction volume, data complexity, user interaction, etc.). Microservices: Suitable for scenarios with high business complexity, rapid iteration requirements, and relatively large team sizes. Event - driven: Suitable for scenarios of asynchronous processing and decoupling of system components. Layered architecture: Suitable for scenarios where the business is relatively stable and the coupling degree between system components is relatively low. Technical feasibility analysis: Consider the existing technology stack, the technical capabilities of the team, and the available technical solutions in the market.

[0061] 3. Architecture design: Component decomposition: Break down the system into multiple highly cohesive and loosely coupled components or services. Define interfaces: Clearly define the communication interfaces between components to ensure clear and controllable interaction between components. Data management: Design a data storage solution, including database selection, data synchronization, and backup strategies. Security design: Ensure data security and privacy protection, including authentication, authorization, and encryption mechanisms.

[0062] 4. Scalability and maintainability design: Modularity: Design modular components for easy independent update and replacement. Service - orientation: Improve the reusability of the system through service - orientation and reduce repetitive development. Automation: Implement automated testing, deployment, and monitoring to improve the stability and maintainability of the system. Monitoring and logging: Integrate a log management and monitoring system for easy problem tracking and performance analysis.

[0063] 5. Technology Selection: Framework Selection: Select appropriate development frameworks and tools according to the architectural style. Middleware Selection: Select appropriate middleware to support message queues, caches, databases, etc.

[0064] 6. Architecture Verification: Prototype Development: Develop a Minimum Viable Product (MVP) to verify the feasibility of the architecture design. Performance Testing: Conduct stress testing and performance testing to ensure that the system meets the performance requirements. Security Audit: Conduct a security audit to ensure that the system design complies with security standards.

[0065] 7. Documentation and Training: Architecture Documentation: Write detailed architecture documentation, including component responsibilities, interface definitions, and data flows; Team Training: Train the development team on the architecture and technology to ensure that the team can understand and follow the architecture design;

[0066] 8. Continuous Iteration, Feedback Mechanism: Establish a feedback mechanism to collect problems and improvement suggestions during system operation, and continuous optimization: Continuously optimize the architecture design and system implementation based on feedback and technological development.

[0067] In step S2, the specific process steps for database design include:

[0068] 1. Requirement Analysis, Requirement Collection: Communicate with the business team to understand the business processes, data entities, data relationships, and business rules. Determine Business Goals: Define the transaction types, data volumes, query requirements, and performance metrics that the database needs to support.

[0069] 2. Conceptual Design, Based on requirement analysis, draw an entity-relationship diagram, define entities, attributes, and relationships between entities, and normalization: Normalize the ER model to reduce data redundancy and update anomalies.

[0070] 3. Logical Design, Data Model Selection: Select an appropriate data model, such as a relational model, document model, key-value model, etc. Table Structure Design: Convert the ER model into a specific table structure, define fields, data types, primary keys, foreign keys, etc. Index Strategy: Design indexes according to query requirements to optimize query performance.

[0071] 4. Physical Design, Storage Engine Selection: Select an appropriate database storage engine according to business requirements, such as InnoDB, MyISAM, Tokyo Cabinet, etc. Partitioning Strategy: For large databases, consider a partitioning strategy to improve performance and management convenience. File System Configuration: Configure the file system of the database to optimize disk I / O performance.

[0072] 5. Database Security Design, User Privilege Management: Design a user privilege management system to ensure data security and compliance. Data Encryption: Encrypt sensitive data for storage to protect user privacy.

[0073] 6. Backup and Recovery Strategy, Backup Plan: Design a regular backup plan, including full backups and incremental backups. Recovery Testing: Conduct regular recovery tests to ensure the availability of backup data.

[0074] 7. Performance Optimization, Performance Testing: Conduct stress testing and performance testing on the database to evaluate system bottlenecks. Query Optimization: Optimize slow queries to improve database performance.

[0075] 8. Data Migration and Synchronization, Migration Plan: If an old database migration is involved, formulate a detailed migration plan. Data Synchronization: For distributed systems, design a data synchronization mechanism to ensure data consistency.

[0076] 9. Documentation and Training, Database Documentation: Compile a detailed database design document, including data dictionaries, ER diagrams, and index strategies. Team Training: Provide training on database management and maintenance for the development team and the operations and maintenance team.

[0077] 10. Continuous Iteration, Monitoring and Tuning: Continuously monitor database performance and perform tuning according to actual situations.

[0078] In step S2, the supply and marketing cooperative management is carried out through the management information system on the web side. While doing a good job in internal management, it also takes into account the business management of farmers and purchasers, improving the operation efficiency of grass-roots supply and marketing cooperatives. Due to differences in management levels, the functional focuses of the general supply and marketing cooperative and the branch supply and marketing cooperative are also different. As the management center of the entire platform, the general supply and marketing cooperative overall manages the supply and marketing cooperatives within its jurisdiction and maintains the stable operation of the platform at the same time. Its functional requirements mainly include general supply and marketing cooperative employee management, subordinate branch supply and marketing cooperative management, supply and marketing cooperative mall management, purchaser management, user management, agricultural assistance service management, etc. As the secondary manager of the platform, the functional requirements of the branch supply and marketing cooperative mainly include branch supply and marketing cooperative employee management, commodity management, inventory management, order management, distribution management, etc.

[0079] In step S3, the online supply and marketing mall is a basic function of the agricultural branch supply and marketing cooperative management platform for the applet user side. It combines the physical operation of traditional supply and marketing cooperatives with e-commerce, enabling rural residents to enjoy supply and marketing cooperative services without leaving home. After farmers log in and authorize the online supply and marketing cooperative applet, they can locate and select a nearby supply and marketing cooperative, enter the supply and marketing mall section, browse the details of agricultural materials, farm tools, daily necessities and other commodities sold in the supply and marketing cooperative. The prices are publicly transparent and unified. After selecting a favorite product and adding it to the shopping cart, farmers can place an order and settle the payment, fill in information such as the delivery address, recipient's name, and number, and wait for the village supply and marketing cooperative to deliver the goods after paying the order. Farmers can view the order progress, contact customer service, cancel the order, view historical order situations, and fill in evaluations in the personal center of the applet. The home page will push hot-selling products for users to refer to for purchase and display relevant information of the supply and marketing cooperative to facilitate users to understand the latest policies.

[0080] In step S3, the sub-supply and marketing cooperative administrators within the management platform can monitor the status of supply and marketing cooperative orders in real time, promptly handle emergencies, track order logistics, avoid order delays, and ensure the smooth completion of orders. Meanwhile, they can view the details of store orders and browse historical orders. The general supply and marketing cooperative administrator can trace the details of order transactions, monitor abnormal orders, assist farmers and purchasers in successfully completing order transactions; manage orders that require the assistance of the supply and marketing cooperative for delivery, reasonably arrange delivery personnel to pick up items, and update the logistics status in real time.

[0081] In step S3, the sub-supply and marketing cooperative administrators within the management platform can achieve informatized management of the store's employees, edit and view basic employee information such as name, phone number, home address, position, and employment time, assisting administrators in better understanding employees, reasonably arranging work, and improving the operation efficiency of the supply and marketing cooperative. In this module, the administrator can also apply for a new management account, and after completing the information of the new administrator, submit it to the general supply and marketing cooperative for review and approval. The general supply and marketing cooperative administrator can modify and query the employee information of the general supply and marketing cooperative to achieve human resource management; manage platform permissions and review and process applications for sub-supply and marketing cooperative management accounts.

[0082] In step S5, the detailed steps include:

[0083] Formulation of coding specifications: Naming rules:

[0084] Variable naming: It should be descriptive, using camel case or underscore separation, such as userProfile or user_profile.

[0085] Function naming: Start with a verb to describe the function's behavior, such as calculateTotal.

[0086] Class naming: Start with a noun, using camel case, such as ShoppingCart.

[0087] Constant naming: All letters are in uppercase, separated by underscores, such as MAX_USERS.

[0088] Code structure: Indentation: Use spaces or tabs uniformly for indentation, usually 4 spaces are recommended. Brackets: Follow a consistent bracket style, such as Allman style or K&R style.

[0089] Line length: Limit the length of each line of code, usually no more than 80 or 120 characters. Code blocks: Use curly braces to enclose code blocks, even for a single line of code.

[0090] Comment standard: Single-line comments: Use / / for single-line comments, avoiding excessive comments.

[0091] Multi-line comments: Use / *...* / for multi-line comments, which are usually used to explain functions or complex logic.

[0092] Documentation comments: Use specific tags (such as / **...* / in Java) to generate documentation.

[0093] After setting up, it is also necessary to select appropriate monitoring tools such as Prometheus, Grafana, and the ELK stack to monitor the performance and health of the system in real time. Set performance and error monitoring alerts to detect and solve problems in a timely manner. At the same time, perform system maintenance regularly, including software updates, security patches, and configuration optimizations. Implement data backup and recovery strategies to ensure the reliability and security of data. It is necessary to regularly upgrade and optimize the system based on monitoring data and user feedback. Adopt continuous integration and continuous deployment (CI / CD) processes to accelerate development iterations and problem fixing.

[0094] In the present invention, by automating and optimizing the business processes of the supply and marketing cooperatives, such as commodity management, order processing, and inventory management, the operation efficiency can be significantly improved and human errors can be reduced. Understanding and meeting user needs and designing a friendly operation interface can enhance user satisfaction and the attractiveness of the platform, thereby increasing user stickiness and market share. By implementing strict data security measures, such as encryption technology and network security policies, sensitive data can be protected from unauthorized access or leakage, safeguarding the interests of users and enterprises. By collecting and analyzing business data, the platform can provide insights and reports for management, supporting more informed business decisions and strategic planning. Through the operation and maintenance monitoring and regular maintenance of the supply and marketing cooperatives, the high availability and stability of the system can be ensured, system failures and downtime can be reduced, and the service quality can be improved. The modular system design and flexible technology selection enable the platform to adapt to business expansion and changes, supporting long-term sustainable development. The unified coding specification and code review process of the supply and marketing cooperatives can promote the collaboration and knowledge sharing of the development team, improving the development quality and efficiency. By automating and integrating various business processes of the supply and marketing cooperatives, the dependence on manual operations can be reduced, thereby lowering the long-term operating costs.

[0095] In the present invention, the mobile device is combined with the computer terminal, and the overall structure and functions of the platform are designed around six main functions, namely, the online supply and marketing mall, agricultural product bidding, agricultural assistance services, supply and marketing cooperative goods allocation, order management, and employee management. The WeChat mini-program user terminal is for farmers and purchasers, and the web management terminal is for branch supply and marketing cooperatives and the head supply and marketing cooperative. The development and application of the agricultural branch supply and marketing cooperative management platform are expected to accelerate the circulation of agricultural products, promote the development of traditional agriculture to modern agriculture, improve the management efficiency of grass-roots supply and marketing cooperatives, respond to national policies, develop new supply and marketing cooperatives that meet the needs of the times, and promote rural revitalization.

[0096] It should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprising", "including" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or device comprising the element.

[0097] The above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for building a digital supply and marketing cooperative software platform, characterized in that: The construction method comprises the following steps: S1: Conduct demand analysis: Analyze the business needs of the supply and marketing cooperative, including commodity management, order processing, inventory management, and logistics tracking; investigate user needs, understand the user groups and usage habits of the supply and marketing cooperative; determine the functional modules, performance requirements, and security requirements of the platform; S2: Design the digital supply and marketing cooperative system: select the appropriate system architecture through architectural design, including microservices and server-side rendering; Perform database design: Design the database model according to business requirements and determine the data storage solution; S3: Design the management platform and online supply and marketing mall. S4: Select technology, choose appropriate programming languages ​​and frameworks such as Java / SpringBoot, Node.js / Express according to project requirements and team skills, and consider the licenses, costs, and technical support of open source and commercial software; S5: Develop coding standards: Develop unified coding standards, including naming rules, code structure, and comment standards; use code review tools such as Git, GitHub, or Bitbucket to ensure code quality and consistency; S6: Adopt modular design to split the system into multiple independent modules to improve development efficiency and maintainability; use version control system to manage code changes and version iterations; S7: Define interfaces: Use API design specifications, such as OpenAPI / Swagger, to define clear interface documents; develop and test RESTfulAPI or GraphQL interfaces to ensure data exchange and communication between modules; S8: Deployment and launch of the digital supply and marketing cooperative software platform: Environmental preparation: Configure the production environment, including servers, networks, and storage resources; install and configure necessary software and middleware, such as Web servers, databases, and cache systems; Deployment script writing: Write automated deployment scripts and use container technologies such as Docker and Kubernetes to simplify deployment and expansion; design blue-green deployment or canary release strategies to ensure smooth transition and rollback capabilities; Pre-launch testing: Conduct comprehensive pre-launch testing, including functional testing, performance testing, and security testing; ensure that the system meets the launch standards and business requirements; S9: After the test is completed, the digital supply and marketing cooperative software platform will be launched online, and the entire digital supply and marketing cooperative software platform construction process can be completed.

2. A method for building a digital supply and marketing cooperative software platform as claimed in claim 1, characterized in that: In step S1, during the demand analysis, meetings are held with key stakeholders of the supply and marketing cooperative to understand their business processes; existing information systems are analyzed to determine the integration points of the new system; during the demand analysis, user usage habits and needs are collected through questionnaires and interviews; Create user portraits during demand analysis to understand the specific needs of different user groups; Write detailed requirements documents based on the information collected during the requirements analysis; Determine functional modules, performance indicators and security requirements.

3. A method for building a digital supply and marketing cooperative software platform as claimed in claim 1, characterized in that: In step S2, the specific steps include:

1. Requirements analysis: Collect requirements: communicate with the business team to understand business processes, user needs, and market trends; determine business goals: clarify the business goals that the system needs to achieve, such as performance, availability, and consistency; 2. Architectural style selection: Evaluate business characteristics: select the appropriate architectural style according to the characteristics of business requirements (such as transaction volume, data complexity, and user interaction); Microservices: suitable for scenarios with high business complexity, rapid iteration, and large team size; Event-driven: suitable for scenarios with asynchronous processing and decoupled system components; Layered architecture: suitable for scenarios with relatively stable business and low coupling between system components; Technical feasibility analysis: consider the existing technology stack, team technical capabilities, and available technical solutions on the market; 3. Architecture design: Component decomposition: split the system into multiple highly cohesive and loosely coupled components or services; Define interfaces: clarify the communication interfaces between components to ensure that the interactions between components are clear and controllable; Data management: design data storage solutions, including database selection, data synchronization and backup strategies; Security design: ensure data security and privacy protection, including authentication, authorization and encryption mechanisms; 4. Scalability and maintainability design: Modularity: Design modular components to facilitate independent updating and replacement; Service-oriented: Improve the reusability of the system and reduce repeated development through service-oriented; Automation: Implement automated testing, deployment and monitoring to improve the stability and maintainability of the system; Monitoring and logging: Integrate log management and monitoring systems to facilitate problem tracking and performance analysis; 5. Technology selection: Framework selection: select appropriate development framework and tools according to the architectural style; Middleware selection: select appropriate middleware to support message queues, caches, and databases; 6. Architecture verification: Prototype development: Develop a minimum viable product (MVP) to verify the feasibility of the architecture design; Performance testing: Conduct stress testing and performance testing to ensure that the system meets performance requirements; Security audit: Conduct security audits to ensure that the system design meets security standards; 7. Documentation and training: Architecture documentation: Write detailed architecture documentation, including component responsibilities, interface definitions, and data flows; Team training: Provide architecture and technology training to the development team to ensure that the team can understand and follow the architecture design; 8. Continuous iteration and feedback mechanism: Establish a feedback mechanism to collect problems and improvement suggestions in system operation, and continuous optimization: Continuously optimize the architecture design and system implementation based on feedback and technological development.

4. A method for building a digital supply and marketing cooperative software platform as claimed in claim 1, characterized in that: In step S2, the specific process steps for database design include:

1. Demand analysis and demand collection: communicate with the business team to understand business processes, data entities, data relationships and business rules; determine business goals: clarify the transaction types, data volume, query requirements and performance indicators that the database needs to support; 2. Conceptual design: Draw entity relationship diagrams based on demand analysis, define entities, attributes, and relationships between entities, and normalize: normalize the ER model to reduce data redundancy and update anomalies; 3. Logical design, data model selection: select the appropriate data model, such as relational model, document model, key-value model; table structure design: convert the ER model into a specific table structure, define fields, data types, primary keys, and foreign keys; index strategy: design indexes according to query requirements to optimize query performance; 4. Physical design, storage engine selection: select the appropriate database storage engine according to business needs, such as InnoDB, MyISAM, Tokyo Cabinet; partition strategy: for large databases, consider partition strategy to improve performance and management convenience; file system configuration: configure the database file system and optimize disk I / O performance; 5. Database security design, user rights management: design user rights management system to ensure data security and compliance; data encryption: encrypt and store sensitive data to protect user privacy; 6. Backup and recovery strategy, backup plan: design a regular backup plan, including full backup and incremental backup; recovery test: perform recovery tests regularly to ensure the availability of backup data; 7.Performance optimization and performance testing: perform stress testing and performance testing on the database to evaluate the bottleneck of the system; query optimization: optimize slow queries to improve database performance; 8. Data migration and synchronization, migration plan: if it involves the migration of the old database, formulate a detailed migration plan; data synchronization: for distributed systems, design a data synchronization mechanism to ensure data consistency; 9. Documentation and training, database documentation: write detailed database design documents, including data dictionary, ER diagram, index strategy, team training: provide database management and maintenance training to the development team and operation and maintenance team; 10. Continuous iteration, monitoring and tuning: Continuously monitor database performance and perform tuning based on actual conditions.

5. A method for building a digital supply and marketing cooperative software platform as claimed in claim 1, characterized in that: In step S2, the supply and marketing cooperatives are managed through the management information system on the web side. While doing a good job of internal management, the business management of farmers and purchasers is taken into account to improve the operational efficiency of the grassroots supply and marketing cooperatives. Due to the difference in management level, the functional focus of the general supply and marketing cooperative and the branch supply and marketing cooperatives is also different. The general supply and marketing cooperative, as the management center of the entire platform, coordinates the management of the supply and marketing cooperatives within its scope and maintains the stable operation of the platform. Its functional requirements mainly include general supply and marketing cooperative employee management, subordinate branch supply and marketing cooperative management, supply and marketing cooperative mall management, purchaser management, user management, and farmer assistance service management. The branch supply and marketing cooperative, as the secondary manager of the platform, has functional requirements mainly for branch supply and marketing cooperative employee management, commodity management, inventory management, order management, and delivery management.

6. A method for building a digital supply and marketing cooperative software platform as claimed in claim 1, characterized in that: In step S3, the online supply and marketing mall is a basic function of the agricultural supply and marketing cooperative management platform for the mini-program user end, which combines the physical operation of traditional supply and marketing cooperatives with e-commerce, allowing rural residents to enjoy the supply and marketing cooperative services without leaving their homes; after farmers log in to authorize the online supply and marketing cooperative mini-program, they can locate and select a nearby supply and marketing cooperative, enter the supply and marketing mall section, and browse the details of agricultural supplies, farm tools and daily necessities sold by the supply and marketing cooperative, with prices that are open, transparent and unified; after selecting the desired products and adding them to the shopping cart, farmers can place an order and settle the bill, fill in the delivery address, recipient name and number information, pay the order and wait for the village supply and marketing cooperative to deliver the goods; farmers can check the order status, contact customer service, cancel orders, browse historical orders and fill in reviews in the personal center of the mini-program; the homepage will push hot-selling products for users to refer to and purchase, and display relevant information about the supply and marketing cooperative to facilitate users to understand the latest policies.

7. A method for building a digital supply and marketing cooperative software platform as claimed in claim 1, characterized in that: In step S3, the sub-supply and marketing cooperative administrator within the management platform can monitor the status of the supply and marketing cooperative order in real time, handle emergencies in a timely manner, track order logistics, avoid order delays, and ensure the smooth completion of orders; at the same time, the store order details can be viewed and historical orders can be browsed; the general supply and marketing cooperative administrator can track order transaction details, monitor abnormal orders, and help farmers and buyers complete order transactions smoothly; Manage orders that require the assistance of supply and marketing cooperatives in delivery, reasonably arrange delivery personnel to pick up the items at the door, and update the logistics status in real time.

8. A method for building a digital supply and marketing cooperative software platform as claimed in claim 1, characterized in that: In step S3, the administrator of the branch supply and marketing cooperative within the management platform can implement information management of store employees, edit and view basic information of employees, such as name, telephone number, home address, position, and time of employment, to assist the administrator to better understand the situation of employees, arrange work reasonably, and improve the operation efficiency of the supply and marketing cooperative; in this module, the administrator can also apply for a new management account, complete the information of the new administrator and submit it to the general supply and marketing cooperative for review and approval; the administrator of the general supply and marketing cooperative can modify and query the employee information of the general supply and marketing cooperative to realize human resource management; Manage platform permissions and review and process applications for branch supply and marketing cooperative management accounts.

9. A method for building a digital supply and marketing cooperative software platform as claimed in claim 1, characterized in that: In step S5, the detailed steps include: Development of coding standards: Naming rules: Variable naming: should be descriptive, using camelCase or underscores, such as userProfile or user_profile; Function naming: starts with a verb and describes the behavior of the function, such as calculateTotal; Class naming: Start with a noun and use camelCase, such as ShoppingCart; Constant naming: all letters are capitalized, separated by underscores, such as MAX_USERS; Code structure: Indentation: Use spaces or tabs for indentation, usually 4 spaces are recommended; Brackets: Follow a consistent bracket style, such as Allman style or K&R style; Line length: limit the length of each line of code, usually no more than 80 or 120 characters; Code block: use curly braces to wrap the code block, even if it is one line of code; Comment standards: Single-line comments: Use / / for single-line comments to avoid excessive comments; Multi-line comments: Use / *...* / for multi-line comments, usually used to describe functions or complex logic; Documentation comments: Use specific tags (such as Java's / **...* / ) to generate documentation.

10. A method for building a digital supply and marketing cooperative software platform as claimed in claim 1, characterized in that: After the above is built, you need to select appropriate monitoring tools, such as Prometheus, Grafana, and ELK stack, to monitor the performance and health of the system in real time; Set up performance and error monitoring alerts to promptly identify and resolve problems, and perform regular system maintenance, including software updates, security patches, and configuration optimization; implement data backup and recovery strategies to ensure data reliability and security; regularly upgrade and optimize the system based on monitoring data and user feedback; adopt continuous integration and continuous deployment (CI / CD) processes to accelerate development iterations and problem fixing.