CN111833028B

CN111833028B - Project management method, apparatus, electronic device, and computer-readable storage medium

Info

Publication number: CN111833028B
Application number: CN202010728917.9A
Authority: CN
Inventors: 富巍; 温国锋; 徐行; 孙媛; 胡松鄂; 杨珂
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2020-07-24
Filing date: 2020-07-24
Publication date: 2023-08-11
Anticipated expiration: 2040-07-24
Also published as: CN111833028A

Abstract

The present disclosure provides a project management method, comprising: creating a programmable project management rule model; mapping out a service interface according to a calling relation between a digitalized sequence of a version entity and a programmed rule component, wherein the programmed rule component is used for verifying the compliance of the version entity to the project management rule; calling the programmed rule component through the service interface and the storage address of the programmed rule component, and executing the programmed rule component to obtain the compliance degree corresponding to the version entity; and carrying out project management according to the version entity under the condition that the compliance degree corresponding to the version entity indicates that the version entity complies with the project management rule. The present disclosure also provides an item management apparatus, an electronic device, and a computer-readable storage medium.

Description

Project management method, apparatus, electronic device, and computer-readable storage medium

Technical Field

The present disclosure relates to the field of computer technology, and more particularly, to a project management method, apparatus, electronic device, and computer-readable storage medium.

Background

In order to shorten the project development period and realize flexible project production, the project management mode in the industry is gradually replaced by an iteration agile mode. However, in this large context, cross-domain, cross-team project sets, especially project sets involving thousands of large members, typically present a series of problems in the project management process:

because project members understand and cognition degree of project specifications is inconsistent, more links do not accord with research and development or design specifications, and research and development quality of the project is uneven in the research and development process. This situation is even more serious, especially when facing thousands of project management teams. From the perspective of project full life cycle management, project quality can identify risk points against research and development specifications through test results at the later entering stage, and then improvement is advanced, so that research and development cost and difficulty are improved through the results, and production and operation risks are greatly increased if the risk points against the research and development specifications are put into production directly. From the perspective of project management, because different projects execute different research rules, project members dividing different projects in a project set need to identify the accuracy of the research rules and analyze the rationality and the necessity of the research rules, so that on one hand, the communication cost across teams is increased, and on the other hand, higher requirements are also put forward on the non-self professional field literacy of the project members.

In addition, the current project management also faces the technical problem of inconvenient storage and analysis caused by non-standardization of project management rules.

Disclosure of Invention

In view of this, the present disclosure provides a project management method, apparatus, electronic device, and computer-readable storage medium.

One aspect of the present disclosure provides a project management method, including:

creating a programmable project management rule model;

mapping out a service interface according to the invoking relation between the digitalized sequence of the version entity of the project management rule model and a programmed rule component, wherein the programmed rule component is used for verifying the compliance of the version entity to the project management rule;

calling the programmed rule component through the service interface and the storage address of the programmed rule component, and executing the programmed rule component to obtain the compliance degree corresponding to the version entity; and

and carrying out project management according to the version entity under the condition that the adherence corresponding to the version entity indicates that the version entity adheres to project management rules.

According to an embodiment of the present disclosure, the item management method further includes:

calling a management module to process the version entity under the condition that the adherence corresponding to the version entity indicates that the version entity does not adhere to the project management rule; and

The version entity in the record is modified using version entity practices.

According to an embodiment of the present disclosure, creating a programmable project management rule model in a project management method includes:

the classification storage of project management rules, the storage of the full life cycle stage of the project, the classification storage of entities and the association of the rules and the entity relationship are realized through a parallel memory, a cross-system service interface, a digital matrix and automatic retrieval; and

a programmable project management rule model is created.

According to an embodiment of the present disclosure, creating a programmable project management rule model in a project management method further includes:

sorting project management rules and detail rules;

sorting the version entity;

sorting the full life cycle stage classification;

and automatically generating a rule combination sequence from the arrangement results through a matrix generation rule, wherein the rule combination sequence comprises the following steps:

matrix generation rules and definite constraint relations;

generating a rule according to the matrix, and generating a number sequence based on different versions of entities, project phases, rule classification and specific rules in a round robin manner;

and storing the round robin result, and realizing the programmability of the project management rule model by establishing the association relation between the version entity and the project rule and the project stage of the whole life cycle.

According to an embodiment of the present disclosure, a call defect management processing module in an item management method processes a version entity, including:

creating defect records for the version entity;

performing defect circulation on the version entity with the defect record; and

and carrying out reply tracking management on the version entity.

Another aspect of the present disclosure provides an item management apparatus, comprising:

the project management rule programming module is used for creating a programmable project management rule model;

the project management rule checking module is used for mapping out a service interface according to the calling relation between the digitalized sequence of the version entity and the programmed rule component, wherein the programmed rule component is used for verifying the compliance of the version entity to the project management rule; calling the programmed rule component through the service interface and the storage address of the programmed rule component, and executing the programmed rule component to obtain the compliance degree corresponding to the version entity; and

and the management module is used for carrying out project management according to the version entity under the condition that the adherence corresponding to the version entity indicates that the version entity adheres to the project management rule.

According to an embodiment of the present disclosure, the project management apparatus further comprises a defect management processing module for:

Processing the version entity in case that the compliance corresponding to the version entity indicates that the version entity does not comply with the project management rules; and

the version entity in the record is modified using version entity practices.

According to an embodiment of the present disclosure, the project management rule programming module in the project management apparatus is further configured to:

sorting project management rules and detail rules;

sorting the version entity;

sorting the full life cycle stage classification;

matrix generation rules and definite constraint relations;

Another aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more instructions, wherein the one or more instructions, when executed by the one or more processors, cause the one or more processors to implement the method as described above.

Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions that, when executed, are configured to implement a method as described above.

Another aspect of the present disclosure provides a computer program comprising computer executable instructions which, when executed, are adapted to carry out the method as described above.

In accordance with embodiments of the present disclosure, creation of a programmable project management rule model is employed; mapping out a service interface according to a calling relation between a digitalized sequence of a version entity and a programmed rule component, wherein the programmed rule component is used for verifying the compliance of the version entity to project management rules; calling the programmed rule component through the service interface and the storage address of the programmed rule component, and executing the programmed rule component to obtain compliance corresponding to the version entity; and under the condition that the adherence corresponding to the version entity shows that the version entity adheres to the project management rule, the project management is carried out according to the technical means of the version entity, and the technical problems of inconvenient storage and analysis caused by non-standardization of the project management rule are solved because the programmable project management model realizes technical standardized storage, citation and application processing of the project management rule and the process data.

Drawings

FIG. 1 schematically illustrates an exemplary system architecture to which the project management methods and apparatus of the present disclosure may be applied;

FIG. 2 schematically illustrates a flow chart of a project management method according to an embodiment of the disclosure;

FIG. 3 schematically illustrates a flow chart of a project management method according to another embodiment of the present disclosure;

FIG. 4 schematically illustrates a flow chart for creating a programmable project management rule model in accordance with an embodiment of the present disclosure;

FIG. 5 schematically illustrates a flow chart for creating a programmable project management rule model according to yet another embodiment of the present disclosure;

FIG. 6 schematically illustrates a flow diagram of invoking a defect management handling module to handle a version entity, according to an embodiment of the present disclosure;

FIG. 7 schematically illustrates a flow chart of a method of project management according to yet another embodiment of the present disclosure;

FIG. 8 schematically illustrates a design of a project management method according to a further embodiment of the present disclosure;

FIG. 9 schematically illustrates a block diagram of a project management apparatus according to an embodiment of the disclosure;

FIG. 10 schematically illustrates a block diagram of a design of a project management rule programming module in accordance with an embodiment of the present disclosure;

FIG. 11 schematically illustrates a block diagram of a design of an project management rules checking module, according to an embodiment of the disclosure; and

Fig. 12 schematically illustrates a block diagram of a computer system suitable for implementing the above-described project management method, according to an embodiment of the present disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is only exemplary and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.

Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a formulation similar to at least one of "A, B or C, etc." is used, in general such a formulation should be interpreted in accordance with the ordinary understanding of one skilled in the art (e.g. "a system with at least one of A, B or C" would include but not be limited to systems with a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

Embodiments of the present disclosure provide a method, apparatus, electronic device, and computer storage medium for project management, the method including: creating a programmable project management rule model; mapping out a service interface according to a calling relation between a digitalized sequence of the version entity and a programmed rule component, wherein the programmed rule component is used for verifying the compliance of the version entity to project management rules; calling the programmed rule component through the service interface and the storage address of the programmed rule component, and executing the programmed rule component to obtain the compliance degree corresponding to the version entity; and performing project management according to the version entity under the condition that the adherence corresponding to the version entity indicates that the version entity adheres to the project management rule.

Fig. 1 schematically illustrates an exemplary system architecture 100 of project management methods and apparatus according to embodiments of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which embodiments of the present disclosure may be applied to assist those skilled in the art in understanding the technical content of the present disclosure, but does not mean that embodiments of the present disclosure may not be used in other devices, systems, environments, or scenarios.

As shown in fig. 1, a system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired and/or wireless communication links, and the like.

The user may interact with the server 105 via the network 104 using the terminal devices 101, 102, 103 to receive or send messages or the like. Various communication client applications may be installed on the terminal devices 101, 102, 103, such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients and/or social platform software, to name a few.

The terminal devices 101, 102, 103 may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.

The server 105 may be a server providing various services, such as a background management server (by way of example only) providing support for websites browsed by users using the terminal devices 101, 102, 103. The background management server may analyze and process the received data such as the user request, and feed back the processing result (e.g., the web page, information, or data obtained or generated according to the user request) to the terminal device.

It should be noted that, the project management method provided by the embodiments of the present disclosure may be generally performed by the server 105. Accordingly, the project management apparatus provided by the embodiments of the present disclosure may be generally provided in the server 105. The project management method provided by the embodiments of the present disclosure may also be performed by a server or a server cluster that is different from the server 105 and is capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Accordingly, the project management apparatus provided by the embodiments of the present disclosure may also be provided in a server or a server cluster that is different from the server 105 and is capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Alternatively, the project management method provided by the embodiment of the present disclosure may be performed by the terminal apparatus 101, 102, or 103, or may be performed by another terminal apparatus other than the terminal apparatus 101, 102, or 103. Accordingly, the project management apparatus provided by the embodiments of the present disclosure may also be provided in the terminal device 101, 102, or 103, or in another terminal device different from the terminal device 101, 102, or 103.

It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

In the process of realizing the project management method, the problem of inconvenient storage and analysis caused by non-standardization of the project management rules is found to be important, but the prior art cannot solve the technical problem of inconvenient storage and analysis caused by non-standardization of the project management rules from the perspective of project management. Therefore, programmable project rule management is needed to realize technical normalized storage, reference and application processing on project management rules and process data, so that the technical problems of inconvenient storage and analysis caused by non-normalized project management rules are solved.

The embodiment of the disclosure provides a project management method and device, which realize technical standardization storage, quotation and application processing on project management rules and process data through programmable project rule management, thereby solving the technical problem of inconvenient storage and analysis caused by non-standardization of the project management rules.

Fig. 2 schematically illustrates a flow chart of a project management method according to an embodiment of the present disclosure.

As shown in fig. 2, the method includes operations S201 to S204.

In operation S201, a programmable project management rule model is created.

According to embodiments of the present disclosure, a programmable project management rule model needs to be created by a project management rule programming module, after which a list of programmable project management rule model entries is created.

In operation S202, the server interface is mapped according to the calling relationship between the digitized sequence of the version entity in the project management rule model and the programmed rule component for verifying compliance of the version entity with respect to the project management rule.

According to embodiments of the present disclosure, a version entity may be understood as an item entity; according to the calling relation between the digitalized sequence of the version entity and the programmed rule component, mapping a service interface, which can be understood as that the calling relation between the digitalized sequence of the version entity and the programmed rule component can be uniquely determined through the service interface. Wherein the calling relationship between the digitized sequence of version entities and the programmed rule building blocks may be stored in table 1.

TABLE 1

According to the method and the device, through automatic identification and calling of the programmed rule code components, automatic detection of the execution effect of the project rule is achieved, and the intelligent level of project management data is improved.

In operation S203, the programmed rule component is invoked by servicing the interface and the memory address of the programmed rule component, and the programmed rule component is executed, resulting in compliance with the version entity.

According to an embodiment of the present disclosure, programmed rule construction is invoked and executed, and the execution result is registered and recorded. If execution passes, the version entity adheres to the entry of the corresponding project management rule.

In operation S204, if the compliance level corresponding to the version entity indicates that the version entity complies with the project management rule, project management is performed according to the version entity.

According to an embodiment of the present disclosure, when a version entity complies with a corresponding item management rule entry, then item management is performed according to the current version entity.

According to the embodiment of the disclosure, the project rule model is established mainly through parallel memory, cross-system service interfaces, digital matrixes, automatic retrieval and other technologies and is used as a main tool for controlling the follow-up version process.

According to the embodiment of the disclosure, matching and verification of the version entity and the management rule are completed through cross-storage mapping, cross-system service interfaces and automatic scheduling technology mainly according to the project management rule model, so that quality result output of the version entity on project management rule compliance is realized, on one hand, the quality result output is used as a main basis for defect management and project assessment inclusion, and on the other hand, automatic error correction in the project process is realized.

According to the embodiment of the disclosure, through verification of project management rules, a defect problem creation event list is automatically called, replies are sent to each party according to defect management flows, and the system ensures the modification quality of a modifier by providing a best practice scheme; the automatic learning of best practice and the automatic continuous improvement of full life cycle project management are realized mainly through the recording, quoting and automatic updating of various solutions.

According to the embodiment of the disclosure, various specifications (such as architecture design specifications, code development specifications, safety management specifications, data storage specification specifications, test design specifications and equipment operation baseline rules) of project management, various specifications and various version entity constraint relations are modeled through programming, and are embedded into various links of version process management in a model control mode, so that constraint on research and development work of roles in various stages of a full life cycle is realized; the project management rule model, the version entity, the defect management system and the solution strategy model are connected in series, so that the project management is in butt joint with the assessment mechanism, the working ideas of huge project members of a large-scale organization are gradually unified, and the version quality of the project under the short period of the iteration mode is ensured. By means of technical means of project management rule programming, association management rules and version entities, automatic debugging of a defect management system after rule violation, automatic learning of best practices and the like, the project management method is realized, wherein project management rules directly act on a management process, project management rule execution results and project assessment indexes are automatically hooked, project group members and specifications are required to be automatically aligned, and self-driven improvement is achieved.

The present disclosure provides an application case, which is specifically as follows:

the code class version entity, such as a.java, digitizes the matrix according to rules and entity relationships to obtain that a.java needs to obey the code branch design which must obey the code development rule 1, i.e. must contain exception handling, and the code branch design which must call the underlying distributed architecture public component A, i.e. the security development rule 2, in the programming stage, represented by the digitized sequences 1411 and 1458 respectively. According to the association relation between the digitalized sequence of the version entity and the programmed rule components, the rule compliance condition can be verified through the programmed rule components of a.exe and c.exe, the system automatically calls the rule compliance condition of a.exe (the execution file contains the search function for the Except () code), c.exe (the execution file contains the search function for the include A code) and registers the judgment result into the record corresponding to the a.java in the table of the "version entity rule execution quality", if the verification is not passed, the system automatically calls the defect management system to register, and if the version entity owner adopts the solution provided by the best practice system and solves the problem, the system synchronously registers into the table of the "version entity rule execution quality", as shown in table 2, so as to be the successful case of the programmed rule component system.

TABLE 2

The method illustrated in fig. 2 is further described below with reference to fig. 3-8 in conjunction with the exemplary embodiment.

Fig. 3 schematically illustrates a flow chart of a method of project management according to another embodiment of the present disclosure.

As shown in fig. 3, the method includes operations S301 to S302.

In operation S301, in a case where the adherence corresponding to the version entity indicates that the version entity does not adhere to the project management rule, the defect management processing module is invoked to process the version entity.

According to an embodiment of the disclosure, invoking the defect management processing module to process the version entity includes creating a defect record for the entity version; performing defect circulation on the entity version; and trace management of replies to the entity version. Wherein, whether a certain version entity obeys the registration of a certain project rule verification result is stored in a table of a project entity quality evaluation result, as shown in table 3.

In operation S302, a version entity in the record is modified with version entity practices.

Operations S301 to S302 may be further supplementary descriptions of the entire project management method according to an embodiment of the present disclosure.

According to the embodiment of the disclosure, the defect management processing module is used for directly and automatically hooking the project management rule model on the specific project implementation result and the assessment result, and the creation of defect records, the tracking management of defect circulation and reply are required to be completed. The project management and management rule interaction constraint module is used for calling the project defect creation module in an interconnected manner, and the rule process management result is formally incorporated into defect management check management through the creation record, so that automatic application of the programmable rule, namely automatic hooking with defect check, is realized. The existing defect management circulation and reply flow is referenced, and the floor tracking of work items with unqualified project rule quality is realized.

TABLE 3 Table 3

Along with the gradual popularization of agile iteration project modes in the industry, project management rules are diversified and flexible, the invention can be rapidly applicable to the change through the programmability of the rules, and research and development personnel can self-drive and adjust the research and development process through the self-verification of the rule model.

FIG. 4 schematically illustrates a flow chart for creating a programmable project management rule model in accordance with an embodiment of the present disclosure.

As shown in fig. 4, the method includes operations S401 to S402.

In operation S401, the classification storage of the project management rules, the storage of the project full life cycle stage, the classification storage of the entities, and the association of the rules and the entity relationships are implemented through the parallel memory, the cross-system server interface, the digital matrix, and the automatic search.

In operation S402, a programmable project management rule model is created.

Fig. 5 schematically illustrates a flow chart for creating a programmable project management rule model according to yet another embodiment of the present disclosure.

As shown in fig. 5, the method includes operations S501 to S505.

In operation S501, classification and detail of the project management rules are sorted.

According to an embodiment of the present disclosure, the combing results are stored in a "project management rule classification" sub-table and a "project management rule detail classification" sub-table, both of which are in columns 1 and 2 in table 4.

In operation S502, the version entity classification is consolidated.

According to an embodiment of the present disclosure, the version entity classification is mainly carded and stored into the "version entity classification" sub-table, which is located in column 4 of table 4.

In operation S503, the full lifecycle stage classification is sorted.

According to embodiments of the present disclosure, the full lifecycle stage classification is primarily carded and stored into a "full lifecycle stage classification" sub-table, which is located at column 3 in table 4, as shown in table 4.

TABLE 4 Table 4

In operation S504, the rule combination sequence is automatically generated from the above-mentioned arrangement results through the matrix generation rule, which includes:

matrix generation rules and definite constraint relations;

according to the matrix generation rule, round robin generates each digital sequence based on different version entities, project phases, rule classifications and specific rules.

According to an embodiment of the present disclosure, the matrix generation rules are stored in a "rule, entity relationship digitizing matrix" table according to each combing result, as shown in table 5.

TABLE 5

In operation S505, the round robin result is stored, and the project management rule model is programmed by establishing the association relationship between the version entity and the project rule, and the project stage of the full life cycle.

According to an embodiment of the present disclosure, the execution result according to the round robin is stored in a "rule, entity relationship digitizing matrix" table, as shown in table 6.

TABLE 6

The project management rules are solidified in the project process management flow in a code mode through the programmable ideas of project requirement design rules, architecture and function design rules, test design rules, project role function management relations and the like, version entities and assessment evaluation, cognition of various project management rules by cross-team, cross-domain and cross-enterprise huge project team members is unified, and practical constraint capacity of various management rules such as regulations, systems, guidance and standards is improved.

Fig. 6 schematically illustrates a flow diagram of invoking a defect management handling module to handle a version entity according to an embodiment of the present disclosure.

As shown in fig. 6, the method includes operations S601 to S603.

In operation S601, creation of a defect record is performed for an entity version.

In operation S602, a defect stream is performed on a physical version of a defective record.

In operation S603, trace management of replies is performed to the entity version.

The method and the device improve the automation degree of project and test management by automatically matching the actual output of process management with the project management rule model and automatically hooking the actual output of process management with the defect management module, so that the management is not driven from back to front by a production event, but permeates various links of the project and test management.

FIG. 7 schematically illustrates a flow chart of a project management method according to yet another embodiment of the present disclosure, in accordance with an embodiment of the present disclosure; firstly, creating a project management rule model according to a version entity, then carrying out matching verification by utilizing the project management model, transmitting a matching verification result to a defect management system for registration processing, if the verification result passes the matching, retaining the original version entity, and if the verification result does not pass the matching, calling a solution model.

FIG. 8 schematically illustrates a design of a project management method according to yet another embodiment of the present disclosure, in accordance with an embodiment of the present disclosure; firstly, project management rule modeling is carried out through a project management rule programming module and a project management rule checking module, then a defect management processing module is called, and a best practice machine learning module is properly called according to the result.

It should be noted that, unless there is an execution sequence between different operations or an execution sequence between different operations in technical implementation, the execution sequence between multiple operations may be different, and multiple operations may also be executed simultaneously in the embodiment of the disclosure.

Fig. 9 schematically shows a block diagram of an item management apparatus according to an embodiment of the disclosure.

As shown in fig. 9, the item management apparatus 700 includes: a project management rule programming module 710, a project management rule verification module 720, and a management module 730.

The project management rule programming module 710 is used to create a programmable project management rule model;

the project management rule checking module 720 is configured to map out a service interface according to a calling relationship between a digitized sequence of the version entity and a programmed rule component, where the programmed rule component is configured to verify compliance of the version entity with respect to project management rules; calling the programmed rule component through the service interface and the storage address of the programmed rule component, and executing the programmed rule component to obtain the compliance degree corresponding to the version entity;

the management module 730 is configured to perform project management according to the version entity if the compliance corresponding to the version entity indicates that the version entity complies with the project management rule.

According to an embodiment of the present disclosure, the project management apparatus 700 further includes a defect management processing module for processing the version entity in case that the adherence corresponding to the version entity indicates that the version entity does not comply with the project management rules; and modifying the version entity in the record using the version entity practices.

According to an embodiment of the present disclosure, the project management rule programming module 710 is configured to complete classification storage of project management rules, full life cycle stage storage of projects, classification storage of entities, association of rules with entity relationships through parallel memory, cross-system server interfaces, digital matrix, and automatic retrieval techniques; and creating a programmable project management rule model.

The project management rules programming module 710 is also used for sorting project management rules and combing details of rules according to embodiments of the present disclosure; sorting the version entity to comb; carding the full life cycle stage classification; and automatically generating a rule combination sequence from the carding results through a matrix generation rule, wherein the rule combination sequence comprises the following steps: matrix generation rules and definite constraint relations; generating a rule according to the matrix, and generating a number sequence based on different version entities, project phases, rule classification and specific rules in a round robin manner; and storing the round robin result, and realizing the programmability of the project management rule model by establishing the association relation between the version entity and the project rule and the project stage of the whole life cycle.

A block diagram of a project management rule programming module according to an embodiment of the present disclosure is shown in fig. 10, wherein the module includes the following elements: and the project management rule classification creation and storage unit: the unit mainly realizes classification of project management rules and combing of detail rules; version entity classification creation and storage unit: the unit mainly sorts the version entities for carding. Project full life cycle stage creation and storage unit: the unit is mainly used for carding in full life cycle stage classification. Rule combination sequence generation unit: the unit mainly generates rule combination sequences by self through matrix generation rules (classification control constraint rules) based on the storage results of the units, wherein each sequence is a 4-bit digital sequence, and the 1 st bit represents version entity type, the 2 nd bit represents stage, the 3 rd bit represents rule classification and the 4 th bit represents specific rule sequence number.

The matrix generation rule is used for defining constraint relation, namely, at what stage a certain version entity needs to be in, which class item rules need to be complied with;

performing a combined sequence round robin: the system generates rules according to the matrix, and generates each digit sequence based on different version entities, project phases, rule classification and specific rules in a round robin manner.

Stage, entity, rule number matrix creation unit: the execution result of the round robin is stored in a rule and entity relation digital matrix table, which is a core unit of the module, and the rule programming is realized by establishing the association relation between the version entity and the project rule and the project stage of the whole life cycle.

A block diagram of the design of an item management rule check module according to an embodiment of the present disclosure is shown in fig. 11, and includes the following elements: version entity and project management rule model matching unit: the unit realizes the automatic matching of the application of the project management rule model by the rule and entity relation digitizing matrix, the version entity digitizing sequence and the programmed rule component calling relation, namely, the calling relation of the programmed rule component is uniquely determined aiming at each output (based on different version entities, project phases, rule classification and the digital sequence of specific rules) of the round robin result. Programmed rule component call unit: and calling the service interface to realize the calling of the programmed rule component. Programming rule execution and registration unit: the execution of the programmed rule component is realized, and whether a certain version entity complies with the registration of a certain project rule verification result is stored in a table of the project entity quality evaluation result. Defect management system tuning unit: and directly calling a defect management system to register and circulate for the items which pass the verification result.

According to embodiments of the present disclosure, project management apparatus 700 also includes a best practice machine learning module for accumulation as a solution to achieve maximum sharing and self-driven improvement of project best practices by each character during the project's full lifecycle. Referring to the best practice model, through stage+rule entries, available best practices are automatically found to guide project process practitioners currently violating project rules to take valuable countermeasures and avoid various risks caused by violating the rules when the next stage is not entered.

According to an embodiment of the present disclosure, the project management apparatus 700 further includes a best practice machine learning module comprising the following elements: the best practice generating unit is used for realizing carding and system solidification of the solution after the rule violation of the existing project; the best practice initializing unit is used for quickly retrieving various solutions after finishing carding; the best practice quoting unit automatically calls up the defect management system when the process management result is inconsistent with the rule model, and automatically calls up, matches and quotes the solution initialization result to realize high-quality guidance of the process improvement party, thereby automatically solving the problem and avoiding new problem caused by re-personalized optimization; and the best practice updating unit expands and optimizes the existing solution library through tracking replies of the defect management system so as to improve the quality of the best practice of the solution.

According to an embodiment of the present disclosure, a defect management processing module includes the following units: a defect record unit is newly built, the unit is used for interconnecting and calling the project management and management rule interaction constraint module and the project defect creation module, and the rule process management result is formally incorporated into defect management check management through the creation record, so that automatic application of the programmable rule, namely automatic hooking with defect check, is realized; a defect circulation and reply unit, which refers to the circulation and reply flow of the existing defect management and realizes the floor tracking of the work items with the quality of the project rules not reaching the standard; and the best practice calling unit is used for realizing formal cross-module calling of the best practice system.

Any number of modules, sub-modules, units, sub-units, or at least some of the functionality of any number of the sub-units according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented as split into multiple modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system-on-chip, a system-on-substrate, a system-on-package, an Application Specific Integrated Circuit (ASIC), or in any other reasonable manner of hardware or firmware that integrates or encapsulates the circuit, or in any one of or a suitable combination of three of software, hardware, and firmware. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be at least partially implemented as computer program modules, which when executed, may perform the corresponding functions.

For example, any of the project management rule programming module 710, the project management rule checking module 720, and the management module 730 may be incorporated in one module/unit/sub-unit or any of the modules/units/sub-units may be split into multiple modules/units/sub-units. Alternatively, at least some of the functionality of one or more of these modules/units/sub-units may be combined with at least some of the functionality of other modules/units/sub-units and implemented in one module/unit/sub-unit. According to embodiments of the present disclosure, at least one of the project management rule programming module 710, the project management rule checking module 720, and the management module 730 may be implemented, at least in part, as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable way of integrating or packaging the circuitry, or in any one of or a suitable combination of any of the three. Alternatively, at least one of the project management rule programming module 710, the project management rule checking module 720, and the management module 730 may be at least partially implemented as a computer program module that, when executed, performs the corresponding functions.

It should be noted that, in the embodiments of the present disclosure, the data processing system portion corresponds to the data processing method portion in the embodiments of the present disclosure, and the description of the data processing system portion specifically refers to the data processing method portion and is not described herein.

Fig. 12 schematically illustrates a block diagram of a computer system suitable for implementing the above-described method according to an embodiment of the present disclosure. The computer system illustrated in fig. 12 is merely an example, and should not be construed as limiting the functionality and scope of use of the embodiments of the present disclosure.

As shown in fig. 12, a computer system 800 according to an embodiment of the present disclosure includes a processor 801 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. The processor 801 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processing circuit, and/or an associated chipset and/or special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. The processor 801 may also include on-board memory for caching purposes. The processor 801 may include a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the disclosure.

In the RAM803, various programs and data required for the operation of the system 800 are stored. The processor 801, the ROM 802, and the RAM803 are connected to each other by a bus 804. The processor 801 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 802 and/or the RAM 803. Note that the program may be stored in one or more memories other than the ROM 802 and the RAM 803. The processor 801 may also perform various operations of the method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.

According to an embodiment of the present disclosure, the system 800 may further include an input/output (I/O) interface 805, the input/output (I/O) interface 805 also being connected to the bus 804. The system 800 may also include one or more of the following components connected to the I/O interface 805: an input portion 806 including a keyboard, mouse, etc.; an output portion 807 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage section 808 including a hard disk or the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. The drive 810 is also connected to the I/O interface 805 as needed. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as needed so that a computer program read out therefrom is mounted into the storage section 808 as needed.

According to embodiments of the present disclosure, the method flow according to embodiments of the present disclosure may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via the communication section 809, and/or installed from the removable media 811. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 801. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

The present disclosure also provides a computer-readable storage medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. Examples may include, but are not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

For example, according to embodiments of the present disclosure, the computer-readable storage medium may include ROM 802 and/or RAM 803 and/or one or more memories other than ROM 802 and RAM 803 described above.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be combined in various combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.

The embodiments of the present disclosure are described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the embodiments cannot be used advantageously in combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the disclosure, and such alternatives and modifications are intended to fall within the scope of the disclosure.

Claims

1. A method of project management, comprising:

creating a programmable project management rule model;

mapping out a service interface according to a calling relation between a digitalized sequence of a version entity in the project management rule model and a programmed rule component, wherein the programmed rule component is used for verifying the compliance of the version entity to project management rules;

carrying out project management according to the version entity under the condition that the compliance degree corresponding to the version entity indicates that the version entity complies with the project management rule;

The creating the programmable project management rule model includes:

sorting project management rules and detail rules;

sorting the version entity;

sorting the full life cycle stage classification;

and automatically generating a rule combination sequence from each arrangement result through a matrix generation rule, wherein the rule combination sequence comprises the following steps:

matrix generation rules and definite constraint relations;

generating a rule according to the matrix, and generating a number sequence based on different version entities, project phases, rule classification and specific rules in a round robin manner;

2. The project management method according to claim 1, further comprising:

invoking a defect management processing module to process the version entity under the condition that the compliance degree corresponding to the version entity indicates that the version entity does not comply with the project management rule; and

the version entity in the record is modified using version entity practices.

3. The project management method of claim 1, said creating a programmable project management rule model comprising:

creating the programmable project management rule model.

4. The project management method of claim 2, wherein the invoking the defect management processing module to process the version entity comprises:

creating defect records for the version entity;

performing defect circulation on the version entity with the defect record; and

and carrying out tracking management on the replies of the version entities.

5. An item management apparatus comprising:

the project management rule programming module is used for creating a programmable project management rule model; the project management rule checking module is used for mapping out a service interface according to the calling relation between the digitalized sequence of the version entity of the project management rule model and a programmed rule component, wherein the programmed rule component is used for verifying the compliance of the version entity to the project management rule; calling the programmed rule component through the service interface and the storage address of the programmed rule component, and executing the programmed rule component to obtain the compliance degree corresponding to the version entity; and

The management module is used for carrying out project management according to the version entity under the condition that the compliance degree corresponding to the version entity indicates that the version entity complies with the project management rule;

the project management rule programming module is used for:

sorting project management rules and detail rules;

sorting the version entity;

sorting the full life cycle stage classification;

matrix generation rules and definite constraint relations;

6. The project management apparatus of claim 5, further comprising a defect management processing module for:

processing the version entity if the compliance corresponding to the version entity indicates that the version entity does not comply with the project management rules; and

The version entity in the record is modified using version entity practices.

7. An electronic device, comprising:

one or more processors;

a memory for storing one or more instructions,

wherein the one or more instructions, when executed by the one or more processors, cause the one or more processors to implement the project management method of any of claims 1 to 4.

8. A computer readable storage medium having stored thereon executable instructions which when executed by a processor cause the processor to implement the project management method of any of claims 1 to 4.