CN111680892A - A research and development management system integrating systematic tool chain - Google Patents

Abstract

The invention relates to the field of application software production, in particular to a research and development management system of an integrated systematic tool chain, which comprises: the system comprises an agility management module, a test management module, an application management module, a development pipeline module, a deployment pipeline module and a DevOps management module, wherein the DevOps management module can provide the basic service resource management function of the whole research and development management. The agile management module can provide management of the requirement, plan and execution of the whole project, and the test management module, the application management module, the development pipeline module and the deployment pipeline module realize the functions of testing, version, development, deployment and the like of the application, so that the software can be rapidly produced, the research and development efficiency is high, and the development threshold is low.

Description

A research and development management system integrating systematic tool chain

technical field

The invention relates to the field of application software production, in particular to a research and development management system of an integrated systematic tool chain.

Background technique

The production of enterprise application software involves the management and tracking of requirements, code management in the development process, resource and environment management in the deployment process, management related to the testing process, and display in the field of operation monitoring after the application goes online. At each stage of the entire software production life cycle, it is necessary to consider improving efficiency. Although different independent systems can meet certain needs, it usually requires more labor costs to support this system. There is an urgent need in the industry to build an R&D management system that integrates a systematic tool chain. By coordinating different roles and visualizing the operation process, it simplifies the process of application development, testing, deployment, operation and maintenance, and monitoring, improving the overall R&D efficiency and reducing the development cost. The threshold for application software is quickly produced, and it adapts to and facilitates the rapid change and development of enterprise business.

Therefore, the existing technology still needs to be improved and developed.

SUMMARY OF THE INVENTION

In view of the above-mentioned deficiencies of the prior art, the purpose of the present invention is to provide a R&D management system integrating a systematic tool chain to solve the problems of low R&D efficiency and high developer threshold in the existing software.

The technical scheme of the present invention is as follows:

The present invention provides a research and development management system of an integrated systematic tool chain, including:

Agile management module for managing project requirements, planning and execution;

The test management module is used to provide test management in the software development process;

The application management module is used for the management of applications and application versions in the project;

Develop pipeline modules for software development process control;

Deployment pipeline module for software application deployment;

The DevOps management module is used to manage the underlying resources of DevOps.

A further preferred solution of the present invention is that: the R&D management system further includes: a report management module, which is used to visualize various stages of software development.

A further preferred solution of the present invention is that: the R&D management system further includes: a three-tier authority structure module, which is used to limit the authority of different modules.

A further preferred solution of the present invention is that: the three-layer authority structure model includes a platform layer, an organization layer and a project layer whose authority is arranged from high to low; wherein, the platform layer is used to manage the functional configuration of the research and development platform itself; The DevOps management module is located at the organizational layer; the agile management module, test management module, application management module, development pipeline module, deployment pipeline module, and report management module are located at the project layer.

A further preferred solution of the present invention is: the agile management module includes:

Issue management unit for creating issues and managing the created issues;

To-do task management unit, which is used to assign sprints to problems and adjust the demand between sprints;

Release version unit, used to create versions;

Active sprint units for creating cycle goals;

Meeting minutes unit to record meetings and track to-do items;

Reporting workbench unit for working report.

A further preferred solution of the present invention is: the test management module includes:

Test outline management unit, establish test outline according to problem management unit;

The test case management unit creates test cases with execution granularity associated downwards according to the test outline;

Test planning unit, which establishes a test plan according to the test outline;

The test execution unit performs test activities according to the test plan.

A further preferred solution of the present invention is: the application management module includes:

Application templates, which are used to provide templates for creating applications;

App version, used to determine the app version

Application release, which is used to release the application to the application market for use by other projects;

The application market is used for quick deployment of internal applications within the organization.

A further preferred solution of the present invention is: the development pipeline module includes: a development console unit, a code warehouse unit, a code branch management unit, a tag management unit, a merge request unit, a continuous integration unit, a code quality unit and a branch detection unit .

A further preferred solution of the present invention is that: the deployment pipeline module includes: an environment self-defining unit, an application deployment unit, an instance state unit, and a resource management unit.

A further preferred solution of the present invention is that: the DevOps management module includes: a template management unit, a cluster management unit, a host management unit, a monitoring management unit and a certificate management unit.

A further preferred solution of the present invention is that: the report management module includes: an agile report unit, a DevOps report unit and a test report unit.

A further preferred solution of the present invention is: the agile reporting unit provides statistics on 12 agile reporting dimensions, the DevOps reporting unit provides statistics on 6 DevOps reporting dimensions; and the test reporting unit provides statistics on 6 test reporting dimensions statistics.

The beneficial effect of the invention is that the basic service resource management function of the whole R&D management can be provided through the DevOps management module. Through the agile management module, the management of the entire project requirements, planning and execution can be provided, and then the application testing, versioning, development, deployment and other functions can be realized through the four modules of the test management module, the application management module, the development pipeline module and the deployment pipeline module. It can realize rapid output of software, high R&D efficiency, and low development threshold.

Description of drawings

1 is a schematic structural diagram of a research and development management system of an integrated systematic tool chain according to an embodiment of the present invention;

2 is a schematic structural diagram of a research and development management system of an integrated systematic tool chain according to an embodiment of the present invention;

3 is a schematic structural diagram of a three-tier authority architecture model according to an embodiment of the present invention;

4 is a schematic structural diagram of an agile management module according to an embodiment of the present invention;

5 is a schematic structural diagram of a test management module according to an embodiment of the present invention;

6 is a schematic structural diagram of an application management module according to an embodiment of the present invention;

FIG. 7 is a schematic structural diagram of a development pipeline module according to an embodiment of the present invention;

8 is a schematic structural diagram of a deployment pipeline module according to an embodiment of the present invention;

9 is a schematic diagram of a structure of a DevOps management module according to an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of a report management module according to an embodiment of the present invention.

Detailed ways

The present invention provides a research and development management system for an integrated systematic tool chain. In order to make the purpose, technical solutions and effects of the present invention clearer and clearer, the present invention is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention, but not to limit the present invention.

A research and development management system of an integrated systematic tool chain provided by an embodiment of the present invention, referring to FIG. 1 to FIG. 10 together, includes:

an agile management module 100 for managing project requirements, planning and execution;

The test management module 200 is used to provide test management in the software development process;

The application management module 300 is used for the management of applications and application versions in the project;

The development pipeline module 400 is used for the management and control of the software development process;

A deployment pipeline module 500 is used for software application deployment;

The DevOps management module 600 is used to manage the underlying resources of DevOps.

The DevOps management module can provide basic service resource management functions for the entire R&D management. Through the agile management module, the management of the entire project requirements, planning and execution can be provided, and then the application testing, versioning, development, deployment and other functions can be realized through the four modules of the test management module, the application management module, the development pipeline module and the deployment pipeline module. It can realize rapid output of software, high R&D efficiency, and low development threshold.

Further, the R&D management system further includes: a report management module 700, which is used to visualize various stages of software development.

By adding the report management module 700, reports of different latitudes can be obtained, and data can be used to display the situation of each stage of the software development process, and provide a basis for improved analysis.

Further, the R&D management system further includes: a three-tier authority structure module 800 for limiting the authority of different modules. By defining different permissions for different modules, it is easy to assign different permissions roles of users flexibly.

Further, the three-layer authority structure model 800 includes a platform layer 810, an organization layer 820 and a project layer 830 whose authority is arranged from high to low; wherein, the platform layer 810 is used to manage the functional configuration of the R&D platform itself; The DevOps management module 600 is located at the organizational layer 820 ; the agile management module 100 , the test management module 200 , the application management module 300 , the development pipeline module 400 , the deployment pipeline module 500 , and the report management module 700 are located at the project layer 830 .

The system is divided into three layers of authority structure, from high to low are the platform layer 810, the organization layer 820 and the project layer 830 respectively. The platform layer 810 mainly manages the configuration of the entire R&D management system. The organization management 820 manages the organization (company) configuration and resource allocation. The project layer 830 manages the data and resources of a project. Each level has its own permission and role system to facilitate the flexible assignment of roles at different levels of users.

Among them, the DevOps management module 600 provides the basic service resource management function of the entire R&D management at the organizational layer 820, which is the cornerstone of all function invocation resources. Generally, it can only be configured after the entire system is deployed, and it is rarely adjusted except monitoring services. . In the project layer 830, if the application management module 300, the test management module 200, the development pipeline module 400, and the deployment pipeline module 500 are compared to pearls, the agile management module 100 is a line that connects these pearls in series, and finally makes each function closely Connection becomes a chain of pearls with higher dimensional overall value. The user associates the code branch with the test task through the issues created in the agile management module 100 . Divide the content of each application through the agile concept of epics and modules. The current application deployment stage and task progress are expressed through the status of the problem. Finally, the report management module 700 is used to quantify the efficiency and progress of each module.

Further, the agile management module 100 includes:

a problem management unit 110, configured to create problems and manage the created problems;

To-do task management unit 120, used for allocating sprints to problems and adjusting the demand between sprints;

a release version unit 130 for creating a version;

Active sprint unit 140 for creating cycle goals;

A meeting minutes unit 150 for recording meetings and tracking to-do items;

The reporting workbench unit 160 is used to make work reports.

The agile management module 100 takes the Scrum model as the core concept, records requirements and work tasks by creating issues such as epics, stories, defects, and tasks, and uses tools such as Active Kanban and Story Kanban to arrange the priorities and tasks of requirements and tasks. Implement batches. Use meeting minutes to record the content of each important meeting node in the agile management process and associate to-do items to achieve the purpose of rhythmically tracking the progress of the project.

Further, the test management module 200 includes:

The test outline management unit 210 establishes a test outline according to the question management unit 110;

The test case management unit 220, according to the test outline, creates test cases with execution granularity associated downwards;

The test planning unit 230 establishes a test plan according to the test outline;

The test execution unit 240 performs test activities according to the test plan.

Wherein, the user creates a one-to-one corresponding test outline based on the stories in the agile management module 100, and creates downward associated test cases with execution granularity according to the test outline. And arrange the test rhythm and corresponding executors by creating a test plan. Executors can report defects found during testing and start new testing cycles and stages accordingly. Finally, the purpose of sustainable circulation of test environment and efficient optimization of delivery quality is achieved.

Further, the application management module 300 includes:

Application template 310, for providing a template for creating an application;

app version 320, used to determine the app version

Application publishing 330, for publishing the application in the application market for use by other projects;

The application market 340 is used for quick deployment of applications within the organization.

The application management module 300 is responsible for managing the applications and application versions in the project, and can import or download second-party and third-party applications in the application market. The user creates a new application under application management, and can select the required scaffolding to initialize the application. The application version generated after application deployment can be included in the whitelist to prevent it from being eliminated by regular cleaning tasks. The produced applications can be published in the application market for deployment by other projects, and similarly, second-party applications and third-party applications can be selected in the application market to be deployed under this project.

Further, the development pipeline module 400 includes: a development console unit 410, a code repository unit 420, a code branch management unit 430, a tag management unit 440, a merge request unit 450, a continuous integration unit 460, a code quality unit 470 and a branch The detection unit 480 .

Wherein, the development console unit 410 is used to provide all quick entries and simple reports of the development pipeline; the code warehouse unit 420 is used to collect code programs that implement specific functions; the code branch management unit 430 is used to develop branches and Branch policy management; the tag management unit 440 is used to create and edit tags; the merge request unit 450 is used to create and edit merge requests; the continuous integration unit 460 is used to monitor the completion of application continuous integration in real time; The code quality unit 470 is used to visually display the result of the code passing the security detection; the branch detection unit 480 is used to perform information flow and review on the R&D detection process.

In this embodiment, the development pipeline module 400 serves as a strategy management for software development, and provides management and control of the development process. The remote code repositories of each application of the project can be managed, and new branches can be created in the corresponding code repositories. After the local branch is edited and submitted, the system will automatically continue to integrate and provide operations for branch tagging and submitting merge requests. Provides the branch detection management function that tracks the branch status for the flow of branches in various environments, and checks the branch code and outputs the code quality report through the SonarQube plug-in.

Further, the deployment pipeline module 500 includes: an environment customization unit 510 , an application deployment unit 520 , an instance state unit 530 , and a resource management unit 540 .

The environment customization unit 51 is used to create and manage environment configurations; the application deployment unit 520 is used to visualize one-click deployment applications; the instance status unit 530 is used to edit the instance and monitor the running state of the instance; the The resource management unit 540 is used to manage the domain name, certificate, container, network and other resources required for application deployment

In this embodiment, the deployment pipeline module 500 mainly describes the deployment environment, instance, network, domain name, container, etc., to inform the user how to deploy and deploy. The user will first create an environment here and configure the resources corresponding to the environment, such as network, domain name, container, certificate, etc. Then deploy the application in a certain environment and manage the generated instance. This module also provides the function of customizing the automatic deployment pipeline, which can edit the entire application deployment process through the visual pipeline operation, so that the same deployment requirements can be automatically realized.

Further, the DevOps management module 600 includes: a template management unit 610 , a cluster management unit 620 , a host management unit 630 , a monitoring management unit 640 and a certificate management unit 650 .

The template management unit 610 is used to create and edit application templates; the cluster management unit 620 is used to create and edit clusters; the host management unit 630 is used to create and edit hosts; the monitoring management unit 640 is used to Real-time monitoring of basic resource operation data of each dimension; the certificate management unit 65 is used to create and edit domain name certificates.

In this embodiment, the DevOps management module 600 exists in the organizational layer 820, and manages organizational elements related to DevOps. New cluster and host resources can be associated and allocated. Integrate Skywalking, Grafana and Prometheus tools to realize real-time monitoring of host and cluster basic service resources and provide monitoring and alarm functions.

Further, the report management module 700 includes: an agile report unit 710 , a DevOps report unit 720 and a test report unit 730 . Furthermore, the agile reporting unit 710 provides statistics on 12 agile reporting dimensions, the DevOps reporting unit 720 provides statistics on six DevOps reporting dimensions; and the test reporting unit 730 provides statistics on six test reporting dimensions.

Wherein, the agile reporting unit 710 is used to view the statistical reports of agile management of each dimension; the DevOps reporting unit 720 is used to view the statistical reports of continuous integration and continuous deployment of each dimension; the test reporting unit 730 is used to view the statistical reports of each dimension The test management statistics report.

Through reports of different latitudes, data are used to display the situation of each stage of the software development process and provide the basis for improvement and analysis. The report management module 700 of the present invention provides statistics of 12 agile report dimensions, 6 DevOps report dimensions and 6 test report dimensions, which can serve the statistical work in the summary stage of each link or view the real-time situation of each dimension of the current project.

The following is a specific embodiment:

Take a project team that needs to use the capabilities of the middle platform to release an application with new functions as an example:

1) Management requirements

Product managers collect functional requirements from the business side and create stories to record specific requirements. Through the sprint kick-off meeting, use the meeting minutes function to conduct project team review of the requirements set. After the review, the requirements are incorporated into the new sprint plan, and the requirements are disassembled and assigned to the corresponding project members.

2) Initialize the application

The technical manager creates an application in the corresponding project, and uses the middle-office microservice scaffolding to initialize the code framework of the application. Then the system automatically generates the code warehouse of the application in the gitlab warehouse, and generates the microservice framework required by the middle platform in the code warehouse. Because the application needs to use the middle-end capabilities, the technical manager can deploy the developed applications in the required fields through the application market, and the code warehouse corresponding to the middle-end application will be created under the project warehouse. The developer can then directly call the application capability in the project.

3) Manage branches

Front-end or back-end development members create new code branches in association with story tasks. And clone the remote branch to the local, and write the function code. Commit this local branch when you have finished writing the feature code. The system will automatically detect the branch commit action and perform continuous integration. The development members communicate the branch status information to the test members through the branch detection function.

4) Manage tests

After the sprint kick-off meeting, test students will generate a test outline and conduct an internal test outline review (using meeting minutes). After disassembling the reviewed outline into executable test cases, the test manager creates a test plan, organizes the test rhythm and date in an orderly manner, and assigns the corresponding execution tasks to the test members. After the development member communicates the branch status to the test member through the branch detection, the test member can execute the test on the test environment, and record the defects in the execution process to facilitate the subsequent round of test inspection. After multiple rounds of testing are completed, agile management can be used to set the story status to pending acceptance. At this time, the branch will be submitted to the acceptance environment. After the product manager has passed the acceptance, the story status will be set to the pending state, and then the technical manager can go online.

5) Publish the application

After the required application function is accepted, the technical manager can publish the application to the application market through the release application function in the application management. At this time, it means that the application provides the permission to deploy the application package to other projects under the same organization. One-click deployment for other projects.

The research and development management system of the integrated systematic tool chain of the present invention can realize the rapid output of software, high research and development efficiency, and low development threshold through the cooperation of various modules.

It should be understood that the application of the present invention is not limited to the above examples. For those of ordinary skill in the art, improvements or transformations can be made according to the above descriptions, and all these improvements and transformations should belong to the protection scope of the appended claims of the present invention.

Claims (12)

1. a research and development management system of an integrated systematic tool chain, is characterized in that, comprises: Agile management module for managing project requirements, planning and execution; The test management module is used to provide test management in the software development process; The application management module is used for the management of applications and application versions in the project; Develop pipeline modules for software development process control; Deployment pipeline module for software application deployment; The DevOps management module is used to manage the underlying resources of DevOps. 2 . The research and development management system of an integrated systemized tool chain according to claim 1 , wherein the research and development management system further comprises: a report management module for visualizing various stages of software development. 3 . 3 . The R&D management system of an integrated systematic tool chain according to claim 2 , wherein the R&D management system further comprises: a three-tier authority architecture module, which is used to limit the authority of different modules. 4 . 4. The research and development management system of an integrated systematic tool chain according to claim 3, wherein the three-layer authority structure model comprises a platform layer, an organization layer and a project layer whose authority is arranged from high to low; The platform layer is used to manage the functional configuration of the R&D platform itself; the DevOps management module is located at the organizational layer; the agile management module, test management module, application management module, development pipeline module, deployment pipeline module, and report management module are located at the project layer. . 5. The R&D management system of an integrated systematic tool chain according to any one of claims 1-4, wherein the agile management module comprises: Issue management unit for creating issues and managing the created issues; To-do task management unit, which is used to assign sprints to problems and adjust the demand between sprints; Release version unit, used to create versions; Active sprint units for creating cycle goals; Meeting minutes unit to record meetings and track to-do items; Reporting workbench unit for working report. 6. The R&D management system of the integrated systemized tool chain according to claim 5, wherein the test management module comprises: Test outline management unit, establish test outline according to problem management unit; The test case management unit creates test cases with execution granularity associated downwards according to the test outline; Test planning unit, which establishes a test plan according to the test outline; The test execution unit performs test activities according to the test plan. 7. The research and development management system of an integrated systematic tool chain according to claim 6, wherein the application management module comprises: Application templates, which are used to provide templates for creating applications; App version, used to determine the app version Application release, which is used to release the application to the application market for use by other projects; The application market is used for quick deployment of internal applications within the organization. 8. The research and development management system of an integrated systematic tool chain according to claim 7, wherein the development pipeline module comprises: a development console unit, a code warehouse unit, a code branch management unit, a tag management unit, a merge request Units, Continuous Integration Units, Code Quality Units, and Branch Test Units. 9 . The R&D management system of an integrated systemized tool chain according to claim 8 , wherein the deployment pipeline module comprises: an environment self-defining unit, an application deployment unit, an instance state unit, and a resource management unit. 10 . 10 . The R&D management system for an integrated systematic tool chain according to claim 9 , wherein the DevOps management module comprises: a template management unit, a cluster management unit, a host management unit, a monitoring management unit, and a certificate management unit. 11 . 11 . The research and development management system of an integrated systematic tool chain according to claim 10 , wherein the report management module comprises: an agile report unit, a DevOps report unit, and a test report unit. 12 . 12. The R&D management system of an integrated systematic tool chain according to claim 11, wherein the agile reporting unit provides statistics of 12 agile reporting dimensions, and the DevOps reporting unit provides statistics of 6 DevOps reporting dimensions ; and the test report unit provides statistics of 6 test report dimensions.

Images