Method and system for developing life cycle by using robot management software

Abstract

The invention belongs to the technical field of software engineering and robot technology crossing, and discloses a method for managing software development life cycle by using a robot, and the method comprises the following specific steps: S1, putting a demand into a pool and reviewing; s2, developing a test evaluation period; S3, starting a demand version; S4, planning and executing the version; S5, communicating and cooperating; according to the technical scheme, two core advantages of intelligent task allocation and real-time communication cooperation are creatively fused, the skill speciality, the current workload and the past task performance of team members are deeply insighted, optimization of task allocation is achieved, it is ensured that each member can obtain challenges matched with the ability of the member, and the task allocation efficiency is improved. Therefore, the problem of resource waste caused by non-uniform task allocation is effectively avoided, and meanwhile, team members can cross space boundaries and immediately share, see and discuss project problems by relying on a real-time chat platform constructed by the nailing robot.

Description

Technical Field

[0001] The present invention belongs to the cross-technical field of software engineering and robotics technology, and specifically relates to a method and system for managing software development life cycle by using robots. Background Art

[0002] The approach of using robots to manage the software development life cycle is a systematic software development process that combines the characteristics and requirements of robotics technology and aims to ensure that all stages of robot management software, from requirements analysis, design, development, testing to deployment, operation and maintenance, can be carried out efficiently and orderly.

[0003] Although current project management tools have basic task allocation functions, they are often limited by manual configuration or simple rules, ignoring the intelligent consideration of individual skill matching and workload balancing, which can easily lead to uneven task allocation and reduced efficiency. At the same time, the traditional mode of information transmission has lags and errors, and the communication barriers between team members hinder the instant sharing of project information and decision-making efficiency. In addition, the cumbersome manual report preparation process is not only time-consuming and labor-intensive, but also difficult to accurately capture project dynamics, affecting the decision-making basis of management. At the risk management level, existing technologies are insufficient in predicting and warning potential risks, and have failed to effectively establish a rapid response mechanism, making it difficult to quickly adjust strategies when projects face uncertainty. In particular, the lack of automated tools and the lack of daily reporting and bug management have further increased the manual burden and limited the efficiency of team collaboration and problem solving. Summary of the invention

[0004] The purpose of the present invention is to provide a method and system for managing software development lifecycle using robots to solve the problems raised in the above background technology.

[0005] In order to achieve the above object, the present invention provides the following technical solution: a method for managing the software development life cycle using a robot, the specific steps of the method are as follows:

[0006] S1: Requirements entry and review: Requirements are submitted to the "robot assistant" through DingTalk, and after screening, they are transferred to the technical owner for review, feedback or meeting discussion;

[0007] S2: Development, testing and evaluation period: After the evaluation period, the DingTalk robot notifies relevant personnel and automatically adds the requirements to the development pool:

[0008] S3: Start the required version: Start a new version, specify the requirements, and the DingTalk robot will intelligently analyze resources and provide suggestions for increase or decrease and risk reports;

[0009] S4: Version planning and execution: DingTalk helps project management: product managers create version processes and groups, and robots automatically remind tasks and update logs in real time;

[0010] S5: Communication and collaboration: Collaboration within the group, DingTalk records discussions; fix bugs to trigger builds, and automatically notify results after completion;

[0011] S6: Continuous optimization and feedback: Collect feedback after going online, summarize and notify the team through DingTalk; iterate and optimize, and improve quality and efficiency in a cycle.

[0012] Preferably, the specific steps of the requirements pool entry and review in S1 are as follows:

[0013] Step 1: Submit requirements: The product or development team submits detailed requirements to the "robot assistant" through DingTalk;

[0014] Step 2: Preliminary screening and submission: The "robot assistant" receives and screens the requirements, and after confirmation, transfers them to the technical owner for review;

[0015] Step 3: Review and feedback: The technical owner reviews the requirements through the DingTalk robot and directly responds to comments or arranges a meeting for discussion.

[0016] Preferably, the development and testing evaluation period in S2 refers to the period of preliminary evaluation quickly responded to by the technical owner or development manager through the DingTalk robot after carefully considering the complexity of the requirements. Then, the DingTalk robot efficiently executes its automated process and immediately notifies all relevant team members of the evaluation result to ensure transparency and synchronization of information. At the same time, the robot automatically classifies the requirement into the pool of requirements to be developed, laying a solid foundation for subsequent project planning and execution.

[0017] Preferably, the launching requirement version in S3 refers to the product or development team officially launching the development of a new version with the help of the DingTalk robot, and accurately specifying the key requirements that this version should include. Subsequently, the DingTalk robot, relying on its in-depth understanding of development resources and scheduling, intelligently generates suggestions for increasing or decreasing version requirements and a detailed report on potential risk points, thereby ensuring the smooth progress of the project.

[0018] Preferably, the specific steps of version planning and execution in S4 are as follows:

[0019] Step 1: Create a version flow and group

[0020] The product manager logs in to DingTalk and uses the project management tool to create a new version of the development process;

[0021] Then, based on the group function of DingTalk, create a group specifically for the version requirements and invite project managers, developers, testers, and designers to join for centralized discussion and collaboration.

[0022] Step 2: Automatically generate and remind process node tasks

[0023] DingTalk robots automatically generate task reminders at key nodes based on preset version plans and schedules;

[0024] Step 3: Record and update version logs in real time

[0025] During the development process, the DingTalk robot continuously monitors the project progress and automatically records key events and changes, such as code submission records, test report generation, and problem repair status;

[0026] The robot will update the log information to the version requirement group in real time, so that all members can view the latest project status and progress at any time, promoting transparency and sharing of information.

[0027] Preferably, the specific steps of communication and collaboration in S5 are as follows:

[0028] Step 1: Collaboration within the group and recording of key discussions

[0029] Development, product, and test personnel communicate and collaborate efficiently through the DingTalk version requirement group to ensure that all details in the version advancement are properly handled. The DingTalk robot records key discussion points in real time and provides the team with necessary reminders to ensure that important information is not missed.

[0030] Step 2: Trigger build and release after bug fix

[0031] When developers successfully fix the bug, they can trigger the DingTalk robot to automatically execute the application building and release process by entering specific commands or executing predefined operations. This process ensures a seamless connection from code repair to application launch, improving work efficiency.

[0032] Step 3: Build a notification for publishing results

[0033] After the build and release process is completed, the DingTalk robot immediately sends notifications to developers, testers, and relevant stakeholders, detailing the build results, deployment details, and any possible precautions.

[0034] Preferably, the continuous optimization and feedback in S6 refers to actively collecting user feedback through multiple channels after the version is successfully launched, and using the intelligent aggregation function of the DingTalk robot to quickly integrate these valuable opinions and notify the product design and development team. Based on the real feedback from users, the team will conduct targeted iterative optimization to ensure that every detail meets user expectations.

[0035] Preferably, the system is composed of a robot module, a state flow module, a report module, a demand management module, an intelligent task allocation module, a personnel management module, a version management module, a group conversation module, and an early warning module based on the above method.

[0036] The beneficial effects of the present invention are as follows:

[0037] 1. The present invention innovatively integrates the two core advantages of intelligent task allocation and real-time communication and collaboration through technical solutions, deeply understands the skills and expertise of team members, current workload and past task performance, optimizes task allocation, and ensures that each member can get challenges that match their capabilities, thereby effectively avoiding the problem of resource waste caused by uneven task allocation. At the same time, relying on the real-time chat platform built by DingTalk robots, team members can transcend spatial boundaries, share insights and discuss project problems in real time, which greatly promotes the barrier-free flow of information and the deepening of team collaboration. This seamless communication mode not only significantly reduces misunderstandings and delays in communication, but also greatly improves the speed and quality of team decision-making, laying a solid foundation for project success.

[0038] 2. The present invention demonstrates its outstanding ability in enhancing team collaboration. It not only ensures that each member can work in the best condition through an intelligent task allocation mechanism, reducing efficiency loss caused by task mismatch; it also relies on an automated report generation system to easily generate key reports such as project progress, daily work and bug tracking, which not only reduces the paperwork burden of team members, but also ensures the real-time and accuracy of information. More importantly, the intelligent risk management function is like the guardian of the project, monitoring potential risks in real time and issuing immediate warnings, helping the team to plan ahead and respond quickly, ensuring that the project is heading in a clear direction and progressing steadily. The integration of this series of intelligent functions not only deepens the communication and collaboration between team members, but also builds a solid foundation for the successful implementation of the project. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 It is a schematic diagram of the overall process of the present invention;

[0040] Figure 2 It is a functional architecture diagram of the present invention;

[0041] Figure 3 It is a timing diagram of the present invention. DETAILED DESCRIPTION

[0042] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0043] like Figures 1 to 3As shown, an embodiment of the present invention provides a method for managing software development lifecycle using a robot, and the specific steps of the method are as follows:

[0044] S1: Requirements entry and review: Requirements are submitted to the "robot assistant" through DingTalk, and after screening, they are transferred to the technical owner for review, feedback or meeting discussion;

[0045] S2: Development, testing and evaluation period: After the evaluation period, the DingTalk robot notifies relevant personnel and automatically adds the requirements to the development pool:

[0046] S3: Start the required version: Start a new version, specify the requirements, and the DingTalk robot will intelligently analyze resources and provide suggestions for increase or decrease and risk reports;

[0047] S4: Version planning and execution: DingTalk helps project management: product managers create version processes and groups, and robots automatically remind tasks and update logs in real time;

[0048] S5: Communication and collaboration: Collaboration within the group, DingTalk records discussions; fix bugs to trigger builds, and automatically notify results after completion;

[0049] S6: Continuous optimization and feedback: Collect feedback after going online, summarize and notify the team through DingTalk; iterate and optimize, and improve quality and efficiency in a cycle.

[0050] Step 6.1: After the version is launched, collect user feedback, summarize it through the DingTalk robot, and notify the product and development teams.

[0051] Step 6.2: Perform iterative optimization based on feedback, and repeat the above process repeatedly to continuously improve product quality and development efficiency.

[0052] The specific steps of the requirements entry and review in S1 are as follows:

[0053] Step 1: Submit requirements: The product or development team submits detailed requirements to the "robot assistant" through DingTalk;

[0054] Step 2: Preliminary screening and submission: The "robot assistant" receives and screens the requirements, and after confirmation, transfers them to the technical owner for review;

[0055] Step 3: Review and feedback: The technical owner reviews the requirements through the DingTalk robot and directly responds to comments or arranges a meeting for discussion.

[0056] This process greatly improves the efficiency and accuracy of demand management through the combination of DingTalk and "Robot Assistant". First, submitting requirements becomes simple and fast, ensuring the complete transmission of information; second, the initial screening of the robot assistant reduces the interference of invalid requirements, allowing the technical owner to focus more on core evaluation; finally, the immediacy of the review and feedback process not only speeds up the decision-making process, but also promotes seamless collaboration between teams, laying a solid foundation for the success of the project.

[0057] The development and testing evaluation period in S2 refers to the period of initial evaluation that the technical owner or development manager quickly responds to through the DingTalk robot after carefully considering the complexity of the requirements. Then, the DingTalk robot efficiently executes its automated process and immediately notifies all relevant team members of the evaluation result to ensure transparency and synchronization of information. At the same time, the robot automatically classifies the requirement into the pool of requirements to be developed, laying a solid foundation for subsequent project planning and execution.

[0058] The automated processing of the development, testing and evaluation period ensures the immediate transparency of information and efficient collaboration of the team through the rapid feedback and synchronization of evaluation results through the DingTalk robot. This process not only simplifies the communication process, but also speeds up the speed of demand entering the development stage, effectively manages the pool of demand to be developed, provides a clear path for project planning and execution, and promotes the smooth progress of the overall project progress.

[0059] Among them, the launch requirement version in S3 refers to the product or development team officially launching the development of a new version with the help of the DingTalk robot, and accurately specifying the key requirements that this version must include. Subsequently, the DingTalk robot, relying on its in-depth understanding of development resources and scheduling, intelligently generates suggestions for increasing or decreasing version requirements and detailed potential risk point reports, ensuring the smooth progress of the project.

[0060] When launching a demand version, the DingTalk robot helps to accurately define key requirements and intelligently generate demand increase and decrease suggestions and potential risk reports. This not only optimizes resource allocation, but also warns of potential obstacles in advance, ensuring that the project direction is clear and risks are controllable. This process greatly improves development efficiency and project success rate, laying a solid foundation for the smooth launch of the product.

[0061] The specific steps of version planning and execution in S4 are as follows:

[0062] Step 1: Create a version flow and group

[0063] The product manager logs in to DingTalk and uses the project management tool to create a new version of the development process.

[0064] Subsequently, based on the group function of DingTalk, a group dedicated to the requirements of this version was created, and relevant personnel such as project managers, developers, testers, designers, etc. were invited to join for centralized discussion and collaboration.

[0065] Step 2: Automatically generate and remind process node tasks

[0066] DingTalk robots automatically generate task reminders at key nodes based on preset version plans and schedules.

[0067] These reminders include but are not limited to the arrangement of design review meetings, code submission deadlines, the start and end times of test verification, etc., to ensure that all relevant personnel are aware of and prepare for the corresponding work in a timely manner.

[0068] Step 3: Record and update version logs in real time

[0069] During the development process, the DingTalk robot continuously monitors the project progress and automatically records key events and changes, such as code submission records, test report generation, and problem repair status;

[0070] The robot will update the log information to the version requirement group in real time, so that all members can view the latest project status and progress at any time, promoting transparency and sharing of information.

[0071] With the help of DingTalk and robot technology, the version planning and execution process has achieved full automation and efficient collaboration from creation to execution. By creating version groups and inviting key members, the centralization and transparency of information is ensured; the node task reminders automatically generated by the robot ensure that the work is carried out on time; the real-time recording and updating of the version log makes the project progress clear at a glance, enhancing the communication and collaboration efficiency between teams. This series of measures not only improves the standardization of version management, but also accelerates the product development cycle, ensuring that the project is completed on time and with quality.

[0072] The specific steps of communication and collaboration in S5 are as follows:

[0073] Step 1: Collaboration within the group and recording of key discussions

[0074] Development, product, and test personnel communicate and collaborate efficiently through the DingTalk version requirement group to ensure that all details in the version advancement are properly handled. The DingTalk robot records key discussion points in real time and provides the team with necessary reminders to ensure that important information is not missed.

[0075] Step 2: Trigger build and release after bug fix

[0076] When developers successfully fix the bug, they can trigger the DingTalk robot to automatically execute the application building and release process by entering specific commands or executing predefined operations. This process ensures a seamless connection from code repair to application launch, improving work efficiency.

[0077] Step 3: Build a notification for publishing results

[0078] After the build and release process is completed, the DingTalk robot immediately sends notifications to developers, testers, and relevant stakeholders, detailing the build results, deployment details, and any possible precautions. This helps team members understand the project status in a timely manner and prepare for subsequent work.

[0079] The benefits of the communication and collaboration process are: through DingTalk groups and robots, the development, product, and testing teams can achieve seamless connection, ensuring the efficient advancement of version requirements and bug fixes. Real-time recording and automatic notification mechanisms reduce information omissions and improve work efficiency and transparency. The seamless build and release process ensures rapid software iteration and stable launch, enhancing the response speed and overall effectiveness of team collaboration.

[0080] The continuous optimization and feedback in S6 refers to actively collecting user feedback through multiple channels after the version is successfully launched, and using the intelligent aggregation function of the DingTalk robot to quickly integrate these valuable opinions and notify the product design and development team. Based on the real feedback from users, the team will conduct targeted iterative optimization to ensure that every detail can meet user expectations. This process will be repeated to continuously optimize the product experience, improve development efficiency, and bring users more excellent products and services.

[0081] The benefits of continuous optimization and feedback mechanisms are significant: it ensures that products are closely aligned with user needs, collects feedback through multiple channels and uses smart tools to quickly summarize, accelerating product iteration and optimization. This closed-loop process not only improves user satisfaction, but also enhances the team's response speed and innovation capabilities, continuously promotes leaps in product quality, and helps companies gain an advantage in market competition.

[0082] Among them, the system is based on the above method and consists of a robot module, a state flow module, a report module, a demand management module, an intelligent task allocation module, a personnel management module, a version management module, a group conversation module, and an early warning module.

[0083] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device.

[0084] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. A method for managing a software development life cycle using a robot, characterized in that: The specific steps of this method are as follows: S1: Requirements entry and review: Requirements are submitted to the "robot assistant" through DingTalk, and after screening, they are transferred to the technical owner for review, feedback or meeting discussion; S2: Development, testing and evaluation period: After the evaluation period, the DingTalk robot notifies relevant personnel and automatically adds the requirements to the development pool: S3: Start the required version: Start a new version, specify the requirements, and the DingTalk robot will intelligently analyze resources and provide suggestions for increase or decrease and risk reports; S4: Version planning and execution: DingTalk helps project management: product managers create version processes and groups, and robots automatically remind tasks and update logs in real time; S5: Communication and collaboration: Collaboration within the group, DingTalk records the discussion; Fix the bug to trigger the build, and automatically notify the result after completion; S6: Continuous optimization and feedback: Collect feedback after going online, and DingTalk summarizes and notifies the team; Iterate optimization and cyclically improve quality and efficiency.

2. The method for managing software development lifecycle using robots according to claim 1, characterized in that: The specific steps of the requirements pool entry and review in S1 are as follows: Step 1: Submit requirements: The product or development team submits detailed requirements to the "Robot Assistant" through DingTalk; Step 2: Preliminary screening and submission: The "robot assistant" receives and screens the requirements, and after confirmation, transfers them to the technical owner for review; Step 3: Review and feedback: The technical owner reviews the requirements through the DingTalk robot and directly responds to comments or arranges a meeting for discussion.

3. The method for managing software development lifecycle using robots according to claim 1, characterized in that: The development and testing evaluation period in S2 refers to the period of initial evaluation that the technical owner or development manager quickly responds to through the DingTalk robot after carefully considering the complexity of the requirements. Then, the DingTalk robot efficiently executes its automated process and immediately notifies all relevant team members of the evaluation results to ensure transparency and synchronization of information. At the same time, the robot automatically classifies the requirement into the pool of requirements to be developed, laying a solid foundation for subsequent project planning and execution.

4. The method for managing software development lifecycle using robots according to claim 1, characterized in that: The launch requirement version in S3 refers to the product or development team officially launching the development of a new version with the help of the DingTalk robot, and accurately specifying the key requirements that this version must include. Subsequently, the DingTalk robot, relying on its in-depth understanding of development resources and schedules, intelligently generates suggestions for increasing or decreasing version requirements and detailed reports on potential risk points, ensuring the smooth progress of the project.

5. The method for managing software development lifecycle using robots according to claim 1, characterized in that: The specific steps of version planning and execution in S4 are as follows: Step 1: Create a version flow and group The product manager logs in to DingTalk and uses the project management tool to create a new version of the development process; Then, based on the group function of DingTalk, create a group specifically for the version requirements and invite project managers, developers, testers, and designers to join for centralized discussion and collaboration. Step 2: Automatically generate and remind process node tasks DingTalk robots automatically generate task reminders at key nodes based on preset version plans and schedules; Step 3: Record and update version logs in real time During the development process, the DingTalk robot continuously monitors the project progress and automatically records key events and changes, such as code submission records, test report generation, and problem repair status; The robot will update the log information to the version requirement group in real time, so that all members can view the latest project status and progress at any time, promoting transparency and sharing of information.

6. The method for managing software development lifecycle using robots according to claim 1, characterized in that: The specific steps of communication and collaboration in S5 are as follows: Step 1: Collaboration within the group and recording of key discussions Development, product, and test personnel communicate and collaborate efficiently through the DingTalk version requirement group to ensure that all details in the version advancement are properly handled. The DingTalk robot records key discussion points in real time and provides the team with necessary reminders to ensure that important information is not missed. Step 2: Trigger build and release after bug fix When developers successfully fix the bug, they can trigger the DingTalk robot to automatically execute the application building and release process by entering specific commands or executing predefined operations. This process ensures a seamless connection from code repair to application launch, improving work efficiency. Step 3: Build a notification for publishing results After the build and release process is completed, the DingTalk robot immediately sends notifications to developers, testers, and relevant stakeholders, detailing the build results, deployment details, and any possible precautions.

7. The method for managing software development lifecycle using robots according to claim 1, characterized in that: The continuous optimization and feedback in S6 refers to actively collecting user feedback through channels after the version is successfully launched, and using the intelligent aggregation function of the DingTalk robot to quickly integrate these valuable opinions and notify the product design and development team. Based on the real feedback from users, the team will conduct targeted iterative optimization to ensure that every detail meets user expectations.

8. A system for managing software development lifecycle using robots, characterized in that: The system based on the method described in any one of claims 1-7 is composed of a robot module, a state flow module, a report module, a demand management module, an intelligent task allocation module, a personnel management module, a version management module, a group conversation module, and an early warning module.

Images