WO2019242167A1 - 一种需求管理方法及计算机设备 - Google Patents
一种需求管理方法及计算机设备 Download PDFInfo
- Publication number
- WO2019242167A1 WO2019242167A1 PCT/CN2018/109662 CN2018109662W WO2019242167A1 WO 2019242167 A1 WO2019242167 A1 WO 2019242167A1 CN 2018109662 W CN2018109662 W CN 2018109662W WO 2019242167 A1 WO2019242167 A1 WO 2019242167A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- operation information
- requirements
- information
- file
- requirement
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Definitions
- the present application relates to the field of computer technology, and in particular, to a demand management method and computer equipment.
- the existing operation process when reviewing a requirements design, the time of the developers participating in the review and the time of the requirement reviewers need to be considered. In addition, the use time of the conference room must also be considered, and the developers required to participate in the review. The three hours, the requirements reviewer, and the use time of the meeting room can be coordinated.
- the developers first develop and wait for the time of the developers, requirements reviewers, and conference rooms to be unavailable. Once the review fails, the requirements need to be redone. Therefore, the existing operation method is not flexible due to the limitation of time and place, which seriously affects the efficiency of requirements review.
- the embodiments of the present application provide a requirements management method and computer equipment, which can implement the requirements review process without the need for developers and requirements reviewers to complete the requirements review time and place flexibly, thereby increasing the demand to a certain extent Review efficiency.
- an embodiment of the present application provides a demand management method, where the method includes:
- an embodiment of the present application provides a demand management platform.
- the demand management platform includes:
- a display unit configured to display the requirement design file in response to the first operation information
- the processing unit is configured to obtain second operation information for the requirement design file, and generate a reviewed requirement review file according to the second operation information.
- an embodiment of the present application provides a computer device including a memory, a processor, and a computer program stored in the memory and executable on the processor.
- the processor executes the computer program, Implementing the requirements management method of any one of the first aspects.
- an embodiment of the present application provides a computer non-volatile readable storage medium, including computer-readable instructions.
- the computer reads and executes the computer-readable instructions, the computer is caused to execute any of the foregoing first aspects.
- a demand management method as described in one item.
- the requirements management platform obtains the requirements design files, and then, the requirements reviewer operates the requirements management platform to trigger the requirements management platform to display the requirements design files. Then, the requirements management platform obtains a number of requirements reviewers for the requirements
- the second operation information of the design file is used to generate a reviewed requirement review file according to the second operation information. Therefore, developers and requirements reviewers only need to perform related operations on the requirements management platform to trigger the requirements management platform to execute the requirements management method and assist developers and requirements reviewers to complete the requirements review flow.
- each requirement reviewer can review the requirements design documents anytime and anywhere by operating the requirements management platform, and the developer only needs to download from the requirements management platform to view the review results
- the requirements review process does not need to be completed by the developer and the requirements reviewer, and the requirements review time and place are flexible, thereby improving the efficiency of the requirements review to a certain extent.
- FIG. 1 is a schematic flowchart of a demand management method according to an embodiment of the present application
- FIG. 2 is a schematic flowchart of another demand management method according to an embodiment of the present application.
- FIG. 3 is a schematic flowchart of another demand management method according to an embodiment of the present application.
- FIG. 4 is a functional block diagram of a requirements management platform provided by an embodiment of the present application.
- FIG. 5 is a functional block diagram of a computer device according to an embodiment of the present application.
- first, second, etc. may be used to describe the operation information in the embodiments of the present application, these operation information should not be limited to these terms. These terms are only used to distinguish operational information from each other.
- the first operation information may also be referred to as the second operation information, and similarly, the second operation information may also be referred to as the first operation information.
- the word “if” as used herein can be interpreted as “at” or “when” or “responding to determination” or “responding to detection”.
- the phrases “if determined” or “if detected (the stated condition or event)” can be interpreted as “when determined” or “responded to the determination” or “when detected (the stated condition or event) ) “Or” in response to a test (statement or event stated) ".
- FIG. 1 is a schematic flowchart of a demand management method according to an embodiment of the present application.
- the requirements management method includes:
- the requirements reviewer inputs operation information through the external input device or the touch screen of the user terminal, so that the execution subject receives the first operation information, and generates a control instruction according to the first operation information.
- the control instruction the display of the execution body Requirements design document.
- the operation inputted by the requirements reviewer to trigger the display of the requirement design file may be one of a click operation, a double-click operation, a long-press operation, and a click on a specified control, which is not limited in this application.
- the second operation information includes, but is not limited to, requirements review opinions, operation positions, and the like.
- the requirements management platform obtains the requirements design files. Then, the requirements reviewer operates the requirements management platform to trigger the requirements management platform to display the requirements design files. Then, the requirements management platform obtains a number of requirements reviewers to target the requirements.
- the second operation information of the design file is used to generate a reviewed requirement review file according to the second operation information. Therefore, developers and requirements reviewers only need to perform related operations on the requirements management platform to trigger the requirements management platform to execute the requirements management method and assist developers and requirements reviewers to complete the requirements review flow.
- each requirement reviewer can review the requirements design documents anytime and anywhere by operating the requirements management platform, and the developer only needs to download from the requirements management platform to view the review results
- the requirements review process does not need to be completed by the developer and the requirements reviewer, and the requirements review time and place are flexible, thereby improving the efficiency of the requirements review to a certain extent.
- obtaining the requirement design in step 101 may be implemented in any of the following ways:
- the first way the developer directly enters the requirements design file that has been designed.
- the developer can fill in the requirements design file offline, and then upload the filled requirements design file to the management platform.
- the execution subject (that is, the requirements management platform) in this application sets the requirements design file editing function, and utilizes the requirements design file editing function provided on the requirements management platform, according to the developer's operation requirements design file editing function. Manage the relevant content filled in on the platform and generate requirements design files.
- the flowchart of the second embodiment is shown in FIG. 2.
- the second embodiment specifically includes:
- a demand design template selection list is displayed.
- requirement design templates are pre-stored in the demand management platform, such as the original product version upgrade template, new product development template, original product repair template, etc., and in order to facilitate users to view and select the corresponding template, design according to these pre-stored requirements Generate a mapping list (that is, a requirement design template selection list) related to the template information, and display this mapping list to the developer, so that the developer can select the matching requirement design template from the requirement design template selection list at a glance, saving When developers find the requirements design template.
- a mapping list that is, a requirement design template selection list
- the developer enters a specified operation into the requirement design template selection list, and the requirements management platform has been triggered to obtain the third operation information for the requirement design template selection list, and according to the third operation information, a corresponding call instruction is generated to call the developer The selected requirements design template, so that the requirements design template is displayed to the developer.
- the first implementation method The developer fills in his own requirement design into the requirement design template currently displayed by the requirement management platform through an external input device such as a mouse or a keyboard, so that the requirement management platform obtains the requirement design information filled in by the developer. A corresponding requirement design file is generated according to the obtained requirement design information.
- the second implementation manner displaying the demand design option in response to the fourth operation information for the demand design template, and then responding to the demand design option indicated by the fifth operation information in response to the fifth operation information for the demand design option
- the information is written into the currently displayed requirements design template to generate the corresponding requirements design file.
- Step 103 acquires the second operation information for the requirements design file, and generates the implementation of the reviewed requirements review file according to the second operation information.
- step 103 may include: first, when obtaining a plurality of second operation information for the requirements design file, summarize the plurality of second operation information to obtain a summary result, and then, according to the summary, As a result, a requirements review file is generated.
- the multiple second operation information is summarized to obtain a summary result.
- the implementation process includes: first, obtaining the similarity of any two pieces of second operation information, and then when the similarity between the two pieces of second operation information reaches a threshold, The two pieces of second operation information are merged into one piece to obtain the merged information after the merge processing. Then, based on the merged information, the similarity between the other operated second operation information and the merged information is obtained. When the threshold is reached, the merging process is performed again. In this way, the above two steps are repeatedly performed until all related second operation information is traversed, so as to obtain a final summary result. What is added here is that when the above process summary is performed, when the similarity of any two pieces of second operation information does not reach the threshold, the two pieces of second operation information are stored separately.
- obtaining the similarity of any two pieces of second operation information in the above embodiment is specifically: comparing whether the operation positions in any two pieces of second operation information are the same, and if they are the same, obtaining keywords for the demand review opinions, and according to the obtained key Words to obtain the similarity of keywords as the similarity of any two second operation information.
- the process of summarizing these second operation information is performed, and when the similarity reaches a threshold, the two arbitrary second operation information are merged, and after the merged information is obtained, the process is also implemented.
- the method includes: obtaining the number of times of merging corresponding to the merge information; and when the number of times of merging is greater than a preset number value, configuring a merge identifier for the merge information.
- the number of mergers is greater than a preset number, it indicates that the problem corresponding to the demand review opinion is more recognized or prominent. Therefore, the corresponding merger mark is set to mark to distinguish it from other corresponding demand review opinions. .
- the requirement review file when displaying the requirement review file to the developer, may be displayed in a specified manner according to the merged identifier.
- the content corresponding to the merged identifier in the requirement review file may be displayed in a specified manner such as highlighting or blinking, and the content display corresponding to the non-merged identifier in the requirement review file may be displayed in a normal display manner to prompt the developer in the requirement review file Important needs review comments.
- the requirements review document in order for developers to quickly view the requirements review documents, they can quickly learn which requirements reviewers put forward each of the requirements review opinions in the requirements review documents.
- the requirements review document Before the requirements review document, it also includes: obtaining the user ID corresponding to each second operation information for the requirements design document, and then generating the requirements review document based on the user identification and the second operation information for the requirements design document by the requirements reviewer Therefore, by looking at the user ID corresponding to each requirement review opinion in the requirement review file, the developer can clearly understand which requirement reviewer put forward each requirement review opinion.
- the user identification may be an ID number, a user name, and the like of the user.
- the requirements reviewer first registers with the requirements management platform, so that the requirements reviewer needs to log in to the requirements management platform when reviewing the requirements design documents, so that the executing entity can obtain the user ID. Number and / or user name, and correlate the ID number and / or user name with the second operation information to implement the above-mentioned scheme for reviewing opinions based on user identification requirements.
- FIG. 3 is a flowchart of another demand management method according to an embodiment of the present application.
- the demand management method further includes:
- the time node information in each stage of the requirements processing includes at least, but not limited to, the time node for completing the requirements design file, the time node for completing the requirements review, and the time node for determining the requirements design file.
- the information of the processing personnel at each stage of the requirements processing includes at least but not limited to: the contact information of the developer and the contact information of the requirements reviewer.
- the process of determining the demand processing phase corresponding to the current time may be: comparing time nodes of the current time with each stage of the demand processing to obtain a comparison result; and determining the demand processing phase corresponding to the current time according to the comparison result.
- the completion time for the developer to fill in the requirements design file is March 20, 2018, and the current time is March 10, 2018.
- the completion time for the developer to fill in the requirements design file is March 20, 2018, and the completion time for the requirements review node is March 30, 2018, and the current time is March 25, 2018.
- the file information includes, but is not limited to, a file type, a file completion identifier, and a file name.
- the time limit reminder information sent to the corresponding processing personnel includes, but is not limited to, the time node corresponding to the demand processing stage, and the remaining processing time.
- the time limit reminder information can be sent in text form, picture form or table form.
- the time limit reminder information is sent to the corresponding processing personnel via email according to the email address of the processing personnel at the demand processing stage corresponding to the current time.
- a time limit reminder message is sent to the corresponding processing personnel through a short message.
- steps 202-204 are performed again.
- This application provides a device for implementing the above-mentioned demand management method.
- FIG. 4 is a demand management platform provided by the present application.
- the demand management platform is used to implement the above-mentioned demand management method.
- the requirements management platform includes:
- An obtaining unit 31 configured to obtain a requirement design file
- a display unit 32 configured to display the requirement design file in response to the first operation information
- the processing unit 33 is configured to obtain second operation information for the requirement design file, and generate a reviewed requirement review file according to the second operation information.
- the obtaining unit 31 in this application is specifically configured to:
- the specific execution process may include: In response to the fourth operation information of the demand design template, display the demand design options; then, obtain the fifth operation information for the demand design options, and write the information corresponding to the demand design options indicated by the fifth operation information into the currently displayed Requirement design template to generate the corresponding requirements design file.
- the processing unit 33 is configured to obtain second operation information for the requirement design file, and to generate a reviewed requirement review file according to the second operation information, which is specifically used to:
- the processing unit 33 when the processing unit 33 obtains a plurality of second operation information for the requirements design file, it summarizes the plurality of second operation information, and when the summary result is obtained, it can perform the following operation: obtain any two second operation information. Similarity of the second operation information; then, when the similarity reaches a threshold, the arbitrary two pieces of second operation information are merged to obtain merged information.
- the processing unit 33 when the processing unit 33 executes that when the similarity reaches a threshold value, the arbitrary two pieces of second operation information are merged, and after the merged information is obtained, it is further used to perform: acquiring the merge The number of merge times corresponding to the information; and when the number of merge times is greater than a preset number value, a merge identifier is configured for the merge information.
- the display unit 32 is further configured to: Displaying the requirements review file in a specified manner according to the identification.
- processing unit 33 in the embodiment of the present application is further specifically configured to:
- each unit in the embodiment of the present application is further configured to:
- the obtaining unit 31 is further configured to obtain time node information and processing personnel information in each stage of demand processing;
- the processing unit 33 is further configured to determine the demand processing stage corresponding to the current moment according to the time node information of each stage of the demand processing; and to detect whether the file information of the demand processing stage corresponding to the current moment is stored; Send the time limit reminder information to the information of the processing personnel corresponding to the demand processing stage corresponding to the time.
- FIG. 5 is a functional block diagram of a computer device provided by the present application.
- the embodiment of the present application provides a computer device including a memory 41, a processor 42, and a computer program stored in the memory 41 and executable on the processor 42.
- the processor 42 executes the computer program To implement the demand management method described in any of the above.
- the present application provides a computer non-volatile readable storage medium.
- a computer program is stored in the computer non-volatile readable storage medium, and when the computer program is called, the computer executes the above requirements management method.
- the requirements management platform obtains the requirements design files, and then, the requirements reviewer operates the requirements management platform to trigger the requirements management platform to display the requirements design files. Then, the requirements management platform obtains a number of requirements reviewers for the requirements
- the second operation information of the design file is used to generate a reviewed requirement review file according to the second operation information. Therefore, developers and requirements reviewers only need to perform related operations on the requirements management platform to trigger the requirements management platform to execute the requirements management method and assist developers and requirements reviewers to complete the requirements review flow.
- each requirement reviewer can review the requirements design documents anytime and anywhere by operating the requirements management platform, and the developer only needs to download from the requirements management platform to view the review results
- the requirements review process does not need to be completed by the developer and the requirements reviewer, and the requirements review time and place are flexible, thereby improving the efficiency of the requirements review to a certain extent.
- the disclosed systems, devices, and methods may be implemented in other ways.
- the device embodiments described above are only schematic.
- the division of the unit is only a logical function division.
- multiple units or components may be combined.
- the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
- the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
- each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.
- the above integrated unit may be implemented in the form of hardware, or in the form of hardware plus software functional units.
- the above integrated unit implemented in the form of a software functional unit may be stored in a computer-readable storage medium.
- the above software functional unit is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) or a processor to execute the methods described in the embodiments of the present application. Some steps.
- the foregoing storage media include: U disks, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks or compact discs and other media that can store program codes .
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Engineering & Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Operations Research (AREA)
- Economics (AREA)
- Marketing (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
本申请实施例提供了一种需求管理方法及计算机设备,涉及计算机技术领域。其中,该需求管理方法包括:首先,获取需求设计文件;然后,响应于第一操作信息,显示所述需求设计文件;从而,获取针对于所述需求设计文件的第二操作信息,根据所述第二操作信息生成评审后的需求评审文。因此,本申请提供的技术方案在需求评审过程不需要开发人员和需求评审人员一起完成,需求评审时间和地点灵活,从而在一定程度上提高了需求评审效率。
Description
本申请要求于2018年06月22日提交中国专利局、申请号为201810654788.6、发明名称为“一种需求管理方法及计算机设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及计算机技术领域,尤其涉及一种需求管理方法及计算机设备。
随着科技信息的发展,人们对于产品的性能要求越来越高。因此,为了满足人们的日益增长的需求,需要不断研发新的产品或者优化已有的产品。
而为了让生产的产品更能贴近用户的需求,在实现研发新的产品或者优化已有的产品之前,通常产品开发人员需要先编写产品的需求设计,然后,开发人员在与需求评审人员约时间和地点,就开发人员编写产品的需求设计开会进行评审,开发人员在根据会议评审结果对需求设计进行修改。
现有的这种操作流程,在对一个需求设计进行评审时,需要考虑参加评审的开发人员的时间以及需求评审人员的时间,此外,还需要考虑会议室的使用时间,要求参加评审的开发人员、需求评审人员以及会议室的使用时间这三个时间相互配合才可以。有时候为了加快研发进度,在开发人员、需求评审人员以及会议室的时间无法配合上时,开发人员先进行开发,等待开发人员、需求评审人员以及会议室的时间无法配合上后才开始评审,一旦评审不通过就需要重新做需求。因此,现有的这种操作方式,对于受时间和地点的限制,操作流程不灵活,严重影响需求评审效率。
申请内容
有鉴于此,本申请实施例提供了一种需求管理方法及计算机设备, 能够实现需求评审过程不需要开发人员和需求评审人员一起完成,需求评审时间和地点灵活,从而在一定程度上提高了需求评审效率。
一方面,本申请实施例提供一种需求管理方法,所述方法包括:
获取需求设计文件;
响应于第一操作信息,显示所述需求设计文件;
获取针对于所述需求设计文件的第二操作信息,根据所述第二操作信息生成评审后的需求评审文件。
第二方面,本申请实施例提供了一种需求管理平台,所述需求管理平台包括:
获取单元,用于获取需求设计文件;
显示单元,用于响应于第一操作信息,显示所述需求设计文件;
处理单元,用于获取针对于所述需求设计文件的第二操作信息,根据所述第二操作信息生成评审后的需求评审文件。
第三方面,本申请实施例提供例一种计算机设备,包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机程序,所述处理器执行所述计算机程序时实现第一方面中任一项所述的需求管理方法。
第四方面,本申请实施例提供了一种计算机非易失性可读存储介质,包括计算机可读指令,当计算机读取并执行上述计算机可读指令时,使得计算机执行如上述第一方面任意一项所述的需求管理方法。
本申请提供的技术方案,需求管理平台获取需求设计文件,然后,需求评审人员通过操作该需求管理平台,触发需求管理平台显示需求设计文件,然后,需求管理平台获取若干个需求评审人员针对于需求设计文件的第二操作信息,根据所述第二操作信息生成评审后的需求评审文件。从而,开发人员和需求评审人员只需要通过对需求管理平台进行相关操作,就可以触发需求管理平台执行需求管理方法,协助开发人员和需求评审人员完成需求评审流。如此,在对需求设计文件进行评审时,每个需求评审人员可以通过操作需求管理平台随时随地对需求设计文件进行评审,且开发人员要查看评审结果时,只需要从需求管理平台上下载即可,这样需求评审过程不需要开发人员和需求评审人员一起完成,需求评审时间和地点灵活,从而在一定程度上提高了需求评审效率。
为了更清楚地说明本申请实施例的技术方案,下面将对实施例中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本申请的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其它的附图。
图1是本申请实施例提供的一种需求管理方法的流程示意图;
图2是本申请实施例提供的另一种需求管理方法的流程示意图;
图3是本申请实施例提供的另一种需求管理方法的流程示意图;
图4是本申请实施例提供的一种需求管理平台的功能方框图;
图5是本申请实施例提供的一种计算机设备的功能方框图。
为了更好的理解本申请的技术方案,下面结合附图对本申请实施例进行详细描述。
应当明确,所描述的实施例仅仅是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其它实施例,都属于本申请保护的范围。
在本申请实施例中使用的术语是仅仅出于描述特定实施例的目的,而非旨在限制本申请。在本申请实施例和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式,除非上下文清楚地表示其他含义。
应当理解,本文中使用的术语“和/或”仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或”的关系。
应当理解,尽管在本申请实施例中可能采用术语第一、第二等来描述操作信息,但这些操作信息不应限于这些术语。这些术语仅用来将操作信息彼此区分开。例如,在不脱离本申请实施例范围的情况下,第一操作信息也可以被称为第二操作信息,类似地,第二操作信息也 可以被称为第一操作信息。
取决于语境,如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”或“响应于检测”。类似地,取决于语境,短语“如果确定”或“如果检测(陈述的条件或事件)”可以被解释成为“当确定时”或“响应于确定”或“当检测(陈述的条件或事件)时”或“响应于检测(陈述的条件或事件)”。
请参考图1,其为本申请实施例提供的一种需求管理方法的流程示意图。
该需求管理方法包括:
101、获取需求设计文件。
102、响应于第一操作信息,显示所述需求设计文件。
需求评审人员通过外部输入设备或者用户终端的触控屏输入操作息,从而,执行主体接收第一操作信息,并根据第一操作信息生成控制指令,响应该控制指令,触发显示执行主体中存储的需求设计文件。
其中,需求评审人员输入的触发显示需求设计文件的操作可以是单击操作、双击操作、长按操作、点击指定控件等操作中的一种,对此本申请不做限定。
103、获取针对于需求设计文件的第二操作信息,根据第二操作信息生成评审后的需求评审文件。
其中,第二操作信息包括但不限于:需求评审意见、操作位置等。
本申请提供的技术方案,需求管理平台获取需求设计文件,然后,需求评审人员通过操作该需求管理平台,触发需求管理平台显示需求设计文件,然后,需求管理平台获取若干个需求评审人员针对于需求设计文件的第二操作信息,根据所述第二操作信息生成评审后的需求评审文件。从而,开发人员和需求评审人员只需要通过对需求管理平台进行相关操作,就可以触发需求管理平台执行需求管理方法,协助开发人员和需求评审人员完成需求评审流。如此,在对需求设计文件进行评审时,每个需求评审人员可以通过操作需求管理平台随时随地对需求设计文件进行评审,且开发人员要查看评审结果时,只需要从需求管理平台上下载即可,这样需求评审过程不需要开发人员和需求评审人员一起完成,需求评审时间和地点灵活,从而在一定程度上提高了需求评审效率。
下面对上述各步骤的实现过程进行详细的阐述。
其中,步骤101获取需求设计可以通过以下任一种方式实现:
第一种方式:由开发人员直接输入已经设计好的需求设计文件。
具体的,开发人员可以线下填写需求设计文件,然后,将填写好的需求设计文件上传到管理平台。
第二种方式:本申请中的执行主体(即需求管理平台)设置需求设计文件编辑功能,利用需求管理平台上供的需求设计文件编辑功能,根据开发人员通过操作需求设计文件编辑功能,在需求管理平台上填写的相关内容,生成需求设计文件。其中,第二种实施方式的流程图如图2所示,第二种实施方式具体包括:
1011、响应指定操作(如,点击显示界面中的需求设计控制),显示需求设计模板选择列表。
其中,需求管理平台中预存有多种需求设计模板,如,原产品版本升级模板、新产品研发模板、原产品修复模板等,而为了便于用户查看和选择对应的模板,根据这些预存的需求设计模板的相关信息生成一个映射列表(即需求设计模板选择列表),并且将这个映射列表显示给开发人员,从而开发人员可以一目了然地从该需求设计模板选择列表中选择出符合的需求设计模板,节省开发人员查找需求设计模板的时间。
1012、获取针对需求设计模板选择列表的第三操作信息,显示所述第三操作信息指示的需求设计模板。
具体的,开发人员对需求设计模板选择列表输入指定的操作,已触发需求管理平台获取针对需求设计模板选择列表的第三操作信息,并根据该第三操作信息生成相应的调用指令,调用开发人员选择的需求设计模板,从而,将需求设计模板显示给开发人员。
1013、获取针对选择的需求设计模板的第四操作信息,并根据该第四操作信息生成对应的需求设计文件。
第一种实现方式:开发人员通过鼠标、键盘等外部输入设备,向需求管理平台当前显示的需求设计模板中填写自己的需求设计,从而,使得需求管理平台获取到开发人员填写的需求设计信息,并根据获得的需求设计信息生成对应的需求设计文件。
第二种实现方式:响应于针对需求设计模板的第四操作信息,显 示需求设计选项,然后,响应于针对需求设计选项的第五操作信息,将所述第五操作信息指示的需求设计选项对应的信息写入当前显示的需求设计模板中,以生成对应的需求设计文件。
这里需要说明的是,通过在需求管理平台中的需求设计选项,开发人员只需要通过操作需求设计选项就可以实现对需求设计文件编写,不需要开发人员手动输出每一个需求设计信息,简化了开发人员填写需求设计文件的操作过程,节省了人力成本。
步骤103获取针对于所述需求设计文件的第二操作信息,根据所述第二操作信息生成评审后的需求评审文件的实现相关阐述如下:
为了提高产品前期需求设计的准确率,从而进一步缩短产品的研发周期,在开发人员设计的需求设计文件可以通过多个需求评审人员审核,从而综合多个需求评审人员的评审意见,做出相应的调整。基于此,步骤103的实现可以包括:首先,当获取到多个针对于所述需求设计文件的第二操作信息时,对多个第二操作信息汇总,得到汇总结果,然后,根据所述汇总结果,生成需求评审文件。
具体的,对多个第二操作信息汇总,得到汇总结果实现过程包括:首先,获取任意两条第二操作信息相似度,然后,当这两条第二操作信息的相似度达到阈值时,将这两条第二操作信息合并为一条,得到合并处理后的合并信息,然后,以该合并信息为基准,获取其他为操作过的第二操作信息与该合并信息的相似度,当其相似度达到阈值时,再次进行合并处理,如此,重复执行上述两步,直到遍历完所有相关的第二操作信息为止,从而得到最终汇总结果。这里补充说明的是在执行上述过程汇总,当任意两条第二操作信息的相似度未达到阈值时,则分别存储这两条第二操作信息。
其中,上述实施例中获取任意两条第二操作信息相似度具体为:比较任意两条第二操作信息中的操作位置是否相同,若相同,分别获取需求评审意见的关键词,根据获得到关键词,获取关键词的相似度,以作为任意两条第二操作信息的相似度。
在另一个实施例中,对这些第二操作信息进行汇总的过程汇总,在执行当所述相似度达到阈值时,所述任意两条第二操作信息合并,得到合并信息之后,还实现过程还包括:获取所述合并信息对应的合并次数;并且,当所述合并次数大于预设数量值时,为所述合并信息 配置合并标识。其中,当该合并次数大于预设数量值时,说明该需求评审意见对应的问题较为公认、或者较为突出,因而,通过设置相应的合并标识进行标记,以实现与其他对应的需求评审意见进行区分。
此外,为了能够提起查看该需求评审文件的开发人员的关注,在显示该需求评审文件给开发人员时,可以根据合并标识,按照指定方式显示需求评审文件。具体可以为,以通过高亮或闪烁等指定方式显示需求评审文件中该合并标识对应的内容,以正常显示方式显示需求评审文件中非合并标识对应的内容显示,以提示开发人员需求评审文件中重要的需求评审意见。
进一步的,结合上述实施例为了便于开发人员在查看需求评审文件时,能够快速获知到需求评审文件中的各条需求评审意见是哪位需求评审员提出的,针对于此,在生成评审后的需求评审文件之前,还包括:获取每个针对于需求设计文件的第二操作信息对应的用户标识,然后,根据用户标识以及需求评审人员针对于需求设计文件的第二操作信息,生成需求评审文件,从而,开发人员通过查看需求评审文件中各条需求评审意见对应的用户标识,就可以清楚的了解到各条需求评审意见是由哪位需求评审人员提出的。
其中,上述用户标识可以为用户的ID号、用户名等。
在一个具体应用场景中,需求评审人员先在该需求管理平台进行注册登录,从而需求评审人员在对需求设计文件进行评审时,需要登录该需求管理平台,从而执行主体就可获取到用户的ID号和/或用户名,并将该ID号和/或用户名与该第二操作信息进行关联,实现上述基于用户标识需求评审意见的方案。
为了能够避免开发人员和/或需求评审人员由于某些原因,忘记填写需求文件或者忘记对需求设计文件进行评审,造成产品研发周期长的问题,本申请进一步提供了另一种需求管理方法,请参考图3,其为本申请实施例提供的另一种需求管理方法的流程图,需求管理方法还包括:
201、获取需求处理各阶段的时间节点信息以及处理人员信息。
其中,需求处理各阶段的时间节点信息至少包括但不限于:需求设计文件填写完成时间节点、需求评审完成时间节点,以及,需求设计文件确定时间节点等。
其中,需求处理各阶段的处理人员信息至少包括但不限于:开发人员的联系方式以及需求评审人员的联系方式。
202、根据需求处理各阶段的时间节点信息,确定当前时刻对应的需求处理阶段。
确定当前时刻对应的需求处理阶段实现过程可以为:比较当前时刻与需求处理各阶段的时间节点,得到比较结果;根据比较结果,确定当前时刻对应的需求处理阶段。例如,开发人员填写需求设计文件的完成时间节点为2018年03月20日,当前时刻为2018年03月10日,通过比较这两个时间,确定出当前时刻处于需求设计文件填写阶段;又例如,开发人员填写需求设计文件的完成时间节点为2018年03月20日,需求评审完成时间节点为2018年03月30日,而当前时刻为2018年03月25日,通过将当前时刻与需求处理各阶段的时间节点,确定出当前时刻处于需求评审阶段。
203、检测是否存储有当前时刻对应的需求处理阶段的文件信息。
其中,文件信息包括但不限于文件类型、文件完成标识、文件名称等。
204、若未检测到,根据当前时刻对应的需求处理阶段的处理人员的信息,发送时限提醒信息。
其中,向对应的处理人员发送时限提醒信息包括但不限于:该需求处理阶段对应的时间节点,以及,剩余处理时间等。此外,发送的时限提醒信息可以是文字形式,图片形式或者表格形式等。
具体的,若处理人员的信息为电子邮件地址,若未检测到,根据当前时刻对应的需求处理阶段的处理人员的电子邮件地址,通过电子邮件向对应的处理人员发送时限提醒信息。
具体的,若处理人员的信息为电话号码,若未检测到,根据当前时刻对应的需求处理阶段的处理人员的电话号码,通过短信息向对应的处理人员发送时限提醒信息。
补充说明的,若检测到存储有当前时刻对应的需求处理阶段的文件信息,则不需要发送时限提醒信息,而是等待进入下一相邻需求处理阶段。当进入到下一相邻需求处理阶段之后,重新执行步骤202-204。
本申请提供了实现上述需求管理方法的装置,请参考图4,其为本申请提供的一种需求管理平台,该需求管理平台用于实现上述需求管 理方法。该需求管理平台包括:
获取单元31,用于获取需求设计文件;
显示单元32,用于响应于第一操作信息,显示所述需求设计文件;
处理单元33,用于获取针对于所述需求设计文件的第二操作信息,根据所述第二操作信息生成评审后的需求评审文件。
可选的是,本申请中的获取单元31具体用于:
响应于指定操作,显示需求设计模板选择列表;
获取针对需求设计模板选择列表的第三操作信息,显示所述第三操作信息指示的需求设计模板;
获取针对所述需求设计模板的第四操作信息,并根据所述第四操作信息生成对应的需求设计文件。
在一个具体实施例中,获取单元31在用于实现获取针对所述需求设计模板的第四操作信息,并根据所述第四操作信息生成对应的需求设计文件时,其具体执行过程可以包括:响应于针对需求设计模板的第四操作信息,显示需求设计选项;然后,获取针对需求设计选项的第五操作信息,将所述第五操作信息指示的需求设计选项对应的信息写入当前显示的需求设计模板中,以生成对应的需求设计文件。
可选的是,本申请实施例中处理单元33用于实现获取针对于所述需求设计文件的第二操作信息,根据所述第二操作信息生成评审后的需求评审文件时,具体用于:
当获取到多个针对于所述需求设计文件的第二操作信息时,对多个第二操作信息汇总,得到汇总结果;
根据所述汇总结果,生成需求评审文件。
其中,处理单元33在实现当获取到多个针对于所述需求设计文件的第二操作信息时,对多个第二操作信息汇总,得到汇总结果时,可以执行一下操作:获取任意两条第二操作信息的相似度;然后,当所述相似度达到阈值时,合并所述任意两条第二操作信息,得到合并信息。
具体的,本申请的一个实施例中,在处理单元33执行当所述相似度达到阈值时,所述任意两条第二操作信息合并,得到合并信息之后,还用于执行:获取所述合并信息对应的合并次数;以及,当所述合并次数大于预设数量值时,为所述合并信息配置合并标识。
此外,结合上述发明实施例,在处理单元33执行完获取针对于所述需求设计文件的第二操作信息,根据所述第二操作信息生成评审后的需求评审文件之后,显示单元32还用于根据所述标识,按照指定方式显示所述需求评审文件。
可选的是,本申请实施例中的处理单元33具体还用于:
获取所述第二操作信息对应的用户标识;
根据所述用户标识以及所述第二操作信息,生成需求评审文件。
可选的是,本申请实施例中的各单元还用于:
获取单元31,还用于获取需求处理各阶段的时间节点信息以及处理人员信息;
处理单元33,还用于根据需求处理各阶段的时间节点信息,确定当前时刻对应的需求处理阶段;以及,检测是否存储有当前时刻对应的需求处理阶段的文件信息;若未检测到,根据当前时刻对应的需求处理阶段对应的处理人员的信息,发送时限提醒信息。
请参考图5,其为本申请提供的一种计算机设备的功能框图。
本申请实施例提供例一种计算机设备,包括存储器41、处理器42以及存储在所述存储器41中并可在所述处理器42上运行的计算机程序,所述处理器42执行所述计算机程序时实现上述任一项所述的需求管理方法。
本申请提供了一种计算机非易失性可读存储介质,该计算机非易失性可读存储介质中存储有计算机程序,当该计算机程序被调用时,计算机执行上述需求管理方法。
本申请提供的技术方案,需求管理平台获取需求设计文件,然后,需求评审人员通过操作该需求管理平台,触发需求管理平台显示需求设计文件,然后,需求管理平台获取若干个需求评审人员针对于需求设计文件的第二操作信息,根据所述第二操作信息生成评审后的需求评审文件。从而,开发人员和需求评审人员只需要通过对需求管理平台进行相关操作,就可以触发需求管理平台执行需求管理方法,协助开发人员和需求评审人员完成需求评审流。如此,在对需求设计文件进行评审时,每个需求评审人员可以通过操作需求管理平台随时随地对需求设计文件进行评审,且开发人员要查看评审结果时,只需要从需求管理平台上下载即可,这样需求评审过程不需要开发人员和需求 评审人员一起完成,需求评审时间和地点灵活,从而在一定程度上提高了需求评审效率。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的***,装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的***,装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如,多个单元或组件可以结合或者可以集成到另一个***,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元,可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中,包括若干指令用以使得一台计算机装置(可以是个人计算机,服务器,或者网络装置等)或处理器(Processor)执行本申请各个实施例所述方法的部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述仅为本申请的较佳实施例而已,并不用以限制本申请,凡在本申请的精神和原则之内,所做的任何修改、等同替换、改进等,均应包含在本申请保护的范围之内。
Claims (20)
- 一种需求管理方法,其特征在于,所述方法包括:获取需求设计文件;响应于第一操作信息,显示所述需求设计文件;获取针对于所述需求设计文件的第二操作信息,根据所述第二操作信息生成评审后的需求评审文件。
- 根据权利要求1所述的方法,其特征在于,所述获取需求设计文件,包括:响应指定操作,显示需求设计模板选择列表;获取针对所述需求设计模板选择列表的第三操作信息,显示所述第三操作信息指示的需求设计模板;获取针对所述需求设计模板的第四操作信息,并根据所述第四操作信息生成对应的所述需求设计文件。
- 根据权利要求2所述的方法,其特征在于,所述获取针对所述需求设计模板的第四操作信息,并根据所述第四操作信息生成对应的所述需求设计文件,包括:响应于针对所述需求设计模板的所述第四操作信息,显示需求设计选项;获取针对所述需求设计选项的第五操作信息,将所述第五操作信息指示的需求设计选项对应的信息写入所述需求设计模板中,以生成对应的所述需求设计文件。
- 根据权利要求1所述的方法,其特征在于,在所述获取针对于所述需求设计文件的第二操作信息,根据所述第二操作信息生成评审后的需求评审文件,包括:当获取到多个针对于所述需求设计文件的第二操作信息时,对所述多个第二操作信息汇总,得到汇总结果;根据所述汇总结果,生成所述需求评审文件。
- 根据权利要求4所述的方法,其特征在于,所述当获取到多个针对于所述需求设计文件的第二操作信息时,对所述多个第二操作信息汇总,得到汇总结果,包括:获取任意两条第二操作信息的相似度;当所述相似度达到阈值时,合并所述任意两条第二操作信息,得到合并信息。
- 根据权利要求5所述的方法,其特征在于,所述当所述相似度达到阈值时,合并所述任意两条第二操作信息,得到合并信息之后,还包括:获取所述合并信息对应的合并次数;当所述合并次数大于预设数量值时,为所述合并信息配置合并标识。
- 根据权利要求6所述的方法,其特征在于,在所述获取针对于所述需求设计文件的第二操作信息,根据所述第二操作信息生成评审后的需求评审文件之后,所述方法还包括:根据所述合并标识,按照指定方式显示所述需求评审文件。
- 根据权利要求1所述的方法,其特征在于,在所述获取针对于所述需求设计文件的第二操作信息,根据所述第二操作信息生成评审后的需求评审文件,包括:获取所述第二操作信息对应的用户标识;根据所述用户标识以及所述第二操作信息,生成所述需求评审文件。
- 根据权利要求1所述的方法,其特征在于,所述方法还包括:获取需求处理各阶段的时间节点信息以及处理人员信息;根据所述需求处理各阶段的时间节点信息,确定当前时刻对应的需求处理阶段;检测是否存储有所述当前时刻对应的需求处理阶段的文件信息;若未检测到,根据所述当前时刻对应的需求处理阶段对应的处理人员的信息,发送时限提醒信息。
- 一种需求管理平台,其特征在于,所述需求管理平台包括:获取单元,用于获取需求设计文件;显示单元,用于响应于第一操作信息,显示所述需求设计文件;处理单元,用于获取针对于所述需求设计文件的第二操作信息,根据所述第二操作信息生成评审后的需求评审文件。
- 根据权利要求10所述的需求管理平台,其特征在于,所述获取单元用于获取需求设计文件时,具体包括:响应指定操作,显示需求设计模板选择列表;获取针对所述需求设计模板选择列表的第三操作信息,显示所述第三 操作信息指示的需求设计模板;获取针对所述需求设计模板的第四操作信息,并根据所述第四操作信息生成对应的所述需求设计文件。
- 根据权利要求11所述的需求管理平台,其特征在于,所述获取单元执行获取针对所述需求设计模板的第四操作信息,并根据所述第四操作信息生成对应的所述需求设计文件时,具体包括:响应于针对所述需求设计模板的所述第四操作信息,显示需求设计选项;获取针对所述需求设计选项的第五操作信息,将所述第五操作信息指示的需求设计选项对应的信息写入所述需求设计模板中,以生成对应的所述需求设计文件。
- 根据权利要求10所述的需求管理平台,其特征在于,所述获取单元执行获取针对于所述需求设计文件的第二操作信息,根据所述第二操作信息生成评审后的需求评审文件时,具体包括:当获取到多个针对于所述需求设计文件的第二操作信息时,对所述多个第二操作信息汇总,得到汇总结果;根据所述汇总结果,生成所述需求评审文件。
- 根据权利要求13所述的需求管理平台,其特征在于,所述处理单元执行当获取到多个针对于所述需求设计文件的第二操作信息时,对所述多个第二操作信息汇总,得到汇总结果时,具体包括:获取任意两条第二操作信息的相似度;当所述相似度达到阈值时,合并所述任意两条第二操作信息,得到合并信息。
- 根据权利要求14所述的需求管理平台,其特征在于,所述当所述相似度达到阈值时,合并所述任意两条第二操作信息,得到合并信息之后,所述处理单元还执行:获取所述合并信息对应的合并次数;当所述合并次数大于预设数量值时,为所述合并信息配置合并标识。
- 根据权利要求15所述的需求管理平台,其特征在于,在所述处理单元执行获取针对于所述需求设计文件的第二操作信息,根据所述第二操作信息生成评审后的需求评审文件之后,还用于:根据所述合并标识,按照指定方式显示所述需求评审文件。
- 根据权利要求10所述的需求管理平台,其特征在于,在所述处理单元执行所述获取针对于所述需求设计文件的第二操作信息,根据所述第二操作信息生成评审后的需求评审文件时,具体用于:获取所述第二操作信息对应的用户标识;根据所述用户标识以及所述第二操作信息,生成所述需求评审文件。
- 根据权利要求10所述的需求管理平台,其特征在于,所述处理单元还用于:获取需求处理各阶段的时间节点信息以及处理人员信息;根据所述需求处理各阶段的时间节点信息,确定当前时刻对应的需求处理阶段;检测是否存储有所述当前时刻对应的需求处理阶段的文件信息;若未检测到,根据所述当前时刻对应的需求处理阶段对应的处理人员的信息,发送时限提醒信息。
- 一种计算机设备,包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机程序,其特征在于,所述处理器执行所述计算机程序时实现如权利要求1至9任一项所述的方法。
- 一种计算机非易失性可读存储介质,其特征在于,包括计算机可读指令,当计算机读取并执行所述计算机可读指令时,使得计算机执行如权利要求1至9任一项所述的方法。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810654788.6A CN109242403B (zh) | 2018-06-22 | 2018-06-22 | 一种需求管理方法及计算机设备 |
CN201810654788.6 | 2018-06-22 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019242167A1 true WO2019242167A1 (zh) | 2019-12-26 |
Family
ID=65072040
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/109662 WO2019242167A1 (zh) | 2018-06-22 | 2018-10-10 | 一种需求管理方法及计算机设备 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN109242403B (zh) |
WO (1) | WO2019242167A1 (zh) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111191999B (zh) * | 2019-11-14 | 2023-07-28 | 中国平安人寿保险股份有限公司 | 产品研发管理方法、装置、计算机设备及存储介质 |
CN112949262B (zh) * | 2021-02-09 | 2024-05-28 | 中广核工程有限公司 | 评审单处理方法、装置、计算机设备和存储介质 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2012174104A (ja) * | 2011-02-23 | 2012-09-10 | Nippon Telegr & Teleph Corp <Ntt> | 苦情検索装置、苦情検索方法、及びそのプログラム |
CN105512034A (zh) * | 2015-12-04 | 2016-04-20 | 北京京东尚科信息技术有限公司 | 一种评审方法和评审*** |
CN108089984A (zh) * | 2017-12-14 | 2018-05-29 | 泰康保险集团股份有限公司 | 代码评审的实现方法、装置、存储介质及电子设备 |
CN108153599A (zh) * | 2017-12-26 | 2018-06-12 | 泰康保险集团股份有限公司 | 一种项目管理平台、方法、存储介质及电子设备 |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090249224A1 (en) * | 2008-03-31 | 2009-10-01 | Microsoft Corporation | Simultaneous collaborative review of a document |
US20100235403A1 (en) * | 2009-01-14 | 2010-09-16 | Mathematical Science Publishers Department of Mathematics University of California, Berkeley | Method and system for on-line edit flow peer review |
JP2011145996A (ja) * | 2010-01-18 | 2011-07-28 | Fujitsu Ltd | レビューワ評価装置、レビューワ評価方法、及びプログラム |
CN105739968B (zh) * | 2016-01-20 | 2020-06-30 | 北京京东尚科信息技术有限公司 | 基于分布式版本控制***Git的更新内容的评审方法和装置 |
CN107622375A (zh) * | 2017-08-01 | 2018-01-23 | 平安科技(深圳)有限公司 | 文档自动生成方法、文档自动生成器及可读存储介质 |
-
2018
- 2018-06-22 CN CN201810654788.6A patent/CN109242403B/zh active Active
- 2018-10-10 WO PCT/CN2018/109662 patent/WO2019242167A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2012174104A (ja) * | 2011-02-23 | 2012-09-10 | Nippon Telegr & Teleph Corp <Ntt> | 苦情検索装置、苦情検索方法、及びそのプログラム |
CN105512034A (zh) * | 2015-12-04 | 2016-04-20 | 北京京东尚科信息技术有限公司 | 一种评审方法和评审*** |
CN108089984A (zh) * | 2017-12-14 | 2018-05-29 | 泰康保险集团股份有限公司 | 代码评审的实现方法、装置、存储介质及电子设备 |
CN108153599A (zh) * | 2017-12-26 | 2018-06-12 | 泰康保险集团股份有限公司 | 一种项目管理平台、方法、存储介质及电子设备 |
Also Published As
Publication number | Publication date |
---|---|
CN109242403A (zh) | 2019-01-18 |
CN109242403B (zh) | 2023-07-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN109992589B (zh) | 基于可视化页面生成sql语句的方法、装置、服务器及介质 | |
CN110045953B (zh) | 生成业务规则表达式的方法及计算装置 | |
CN109697066B (zh) | 实现数据表拼接及自动训练机器学习模型的方法和*** | |
JP3272281B2 (ja) | データアイテム表示方法及び表示装置、データアイテムの表示を制御するプログラムを格納した記憶媒体 | |
US10409901B2 (en) | Providing collaboration communication tools within document editor | |
CN111324609A (zh) | 知识图谱构建方法、装置、电子设备及存储介质 | |
CN108388623B (zh) | Er关系生成方法、装置、计算机设备及存储介质 | |
JP2019133645A (ja) | 構造化文書の内容をチャットベースのインタラクションに翻訳するための半自動化された方法及びシステム、プログラム | |
KR20180091838A (ko) | 페이지 구축 방법, 단말기, 컴퓨터 판독 가능 저장 매체 및 페이지 구축기기 | |
US11816096B2 (en) | Systems and methods for managing designated content in collaboration systems | |
CN111324535A (zh) | 一种控件异常检测方法、装置和计算机设备 | |
CN115576974B (zh) | 数据处理方法、装置、设备和介质 | |
WO2019242167A1 (zh) | 一种需求管理方法及计算机设备 | |
US11567635B2 (en) | Online collaborative document processing method and device | |
CN116360735A (zh) | 一种表单生成方法、装置、设备和介质 | |
CN113590097B (zh) | 一种api接口的生成方法、装置、电子设备及存储介质 | |
WO2020253069A1 (zh) | 表格数据修改方法、装置、电子设备及存储介质 | |
US11847599B1 (en) | Computing system for automated evaluation of process workflows | |
CN112732243B (zh) | 一种用于生成功能组件的数据处理方法及装置 | |
JP2003111042A (ja) | 会議支援装置、情報処理装置、電子会議システムおよびプログラム | |
US11995036B2 (en) | Automated customized modeling of datasets with intuitive user interfaces | |
CN114928566A (zh) | 客户端的功能测试方法、装置、存储介质与电子设备 | |
CN109952557A (zh) | 分层内容选择 | |
CN112182350A (zh) | 基于内容库的交互方法、装置、服务器及存储介质 | |
CN111191057A (zh) | 一种自定义检索方法、装置、电子设备及其存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18923620 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 18923620 Country of ref document: EP Kind code of ref document: A1 |