Requirement Acquisition Method, Device, Storage Medium and Electronic Device
By constructing a product requirement list and a system function list based on user behavior habit data and generating a product attribute list, the problem of inaccurate acquisition of user needs is solved, and the rapid conversion of user needs into application system functions is achieved.
Patent Information
- Application Number
- CN202111191349.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-10-13
- Publication Date
- 2025-06-27
- Estimated Expiration
- 2041-10-13
AI Technical Summary
It is difficult for the prior art to accurately obtain user needs and quickly convert user needs into system functions of application systems.
By obtaining user behavior habit data, building a product requirement list, combining the system function list of the product system to be updated, building a product attribute list, and sending it to the user terminal. After the user fills in, the target requirements are built based on the filling results so that the developer can update the system to be updated.
It realizes system functions that more accurately acquire user needs and quickly convert needs into application systems, improving the popularity of user experience and product systems.
Smart Images

Figure CN113918122B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the technical field of software development, and particularly to a method and device for requirement acquisition, a storage medium, and an electronic device. Background Art
[0002] With the improvement of living standards and the development of technology, users' requirements are constantly changing. Since users' requirements are closely related to the popularity and user experience of product systems, how to accurately obtain users' requirements and quickly convert users' requirements into system functions of application systems is an urgent problem for those skilled in the art. Summary of the Invention
[0003] This application provides a method and device for requirement acquisition, a storage medium, and an electronic device, aiming to accurately obtain users' requirements and quickly convert users' requirements into system functions of application systems.
[0004] To achieve the above object, this application provides the following technical solutions:
[0005] A method for requirement acquisition, including:
[0006] Obtaining a product requirement list; the product requirement list is constructed based on user behavior habit data;
[0007] Obtaining a system function list of the product system to be updated;
[0008] Based on the product requirement list and the system function list, constructing a product attribute list; the product attribute list at least includes a plurality of function attribute items and corresponding selection items of the function attribute items;
[0009] Sending the product attribute list to a user terminal;
[0010] Obtaining result information filled in by the user for the product attribute list fed back by the user terminal, and obtaining a target requirement based on the result information, so that developers can update the system to be updated based on the target requirement.
[0011] For the above method, optionally, the obtaining a system function list of the product system to be updated includes:
[0012] Determining a system function menu of the product system to be updated;
[0013] Parsing the system function menu to obtain hierarchical function menus included in the system function menu;
[0014] Based on the hierarchical function menus, constructing a system function list.
[0015] In the above method, optionally, constructing a product attribute list based on the product requirement list and the system function list includes:
[0016] Generating a plurality of function attribute items and corresponding selection items for the function attribute items based on the system function list;
[0017] Constructing an initial product attribute list based on each of the function attribute items and the corresponding selection items for the function attribute items;
[0018] Supplementing the initial product attribute list based on the product requirement list to obtain a product attribute list.
[0019] In the above method, optionally, the product requirement list includes a plurality of requirement items, and supplementing the initial product attribute list based on the product requirement list to obtain a product attribute list includes:
[0020] For the requirement items included in the product requirement list, determining whether there are function attribute items in the initial product attribute list that match the requirement items. If there are, updating the selectable items corresponding to the matched function attribute items based on the requirement items to obtain an updated initial product attribute list. If not, determining the requirement item as an unmatched requirement item;
[0021] Generating function attribute items corresponding to the unmatched requirement items and corresponding selection items for the function attribute items;
[0022] Adding the function attribute items corresponding to each unmatched requirement item and the corresponding selection items for the function attribute items to the updated initial product attribute list to obtain a product attribute list.
[0023] In the above method, optionally, the product attribute list further includes input items corresponding to the function attribute items.
[0024] In the above method, optionally, obtaining a target requirement based on the result information includes:
[0025] Calculating the probability that the selection items in the product attribute list are selected and the probability that the user filling information corresponding to the input items is similar based on the result information;
[0026] Determining the target information corresponding to the function attribute items from the selection items corresponding to the function attribute items and the user filling information corresponding to the input items based on the probability that the selection items in the product attribute list are selected and the probability that the user filling information corresponding to the input items is similar;
[0027] Obtaining a target requirement based on the target information corresponding to each function attribute item.
[0028] Optionally, before obtaining the target requirement based on the target information corresponding to the functional attribute item, the above method further includes:
[0029] Updating a preset requirement analysis template based on the target information corresponding to the functional attribute item.
[0030] A requirement acquisition device includes:
[0031] A first acquisition unit, configured to acquire a product requirement list; the product requirement list is constructed based on user behavior habit data;
[0032] A second acquisition unit, configured to acquire a system function list of a product system to be updated;
[0033] A construction unit, configured to construct a product attribute list based on the product requirement list and the system function list; the product attribute list at least includes a plurality of functional attribute items and selection items corresponding to the functional attribute items;
[0034] A sending unit, configured to send the product attribute list to a user terminal;
[0035] A third acquisition unit, configured to acquire result information filled in by the user for the product attribute list fed back by the user terminal, and obtain a target requirement based on the result information, so that developers can update the system to be updated based on the target requirement.
[0036] A storage medium stores an instruction set, wherein when the instruction set is executed by a processor, the above-mentioned requirement acquisition method is implemented.
[0037] An electronic device includes:
[0038] A memory, configured to store at least one set of instruction sets;
[0039] A processor, configured to execute the instruction sets stored in the memory, and implement the above-mentioned requirement acquisition method by executing the instruction sets.
[0040] Compared with the prior art, the present application has the following advantages:
[0041] The present application provides a method and apparatus for requirement acquisition, a storage medium, and an electronic device. The method includes: obtaining a product requirement list, which is constructed based on user behavior habit data; obtaining a system function list of the product system to be updated; constructing a product attribute list based on the product requirement list and the system function list, where the product attribute list at least includes a plurality of function attribute items and corresponding selection items for the function attribute items; sending the product attribute list to a user terminal; obtaining result information of the user's filling of the product attribute list feedback by the user terminal; and obtaining a target requirement based on the result information, so that developers can update the system to be updated based on the target requirement. It can be seen that in the solution of the present application, since the product attribute list is constructed based on the system functions of the product system to be updated and user behavior habit data, therefore, by filling in the product attribute list, it helps the user to express requirements more accurately, so as to obtain relatively accurate user requirements. Moreover, most of the functions included in the obtained target requirement are functions already supported by the product system to be updated. Therefore, based on the target requirement, it is possible to quickly convert user requirements into system functions of an application system. BRIEF DESCRIPTION OF THE DRAWINGS
[0042] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only the embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on the provided drawings.
[0043] Figure 1 It is a flowchart of a method for requirement acquisition provided by the present application;
[0044] Figure 2 It is another flowchart of a method for requirement acquisition provided by the present application;
[0045] Figure 3 It is an example diagram of a method for requirement acquisition provided by the present application;
[0046] Figure 4 It is yet another flowchart of a method for requirement acquisition provided by the present application;
[0047] Figure 5 It is another example diagram of a method for requirement acquisition provided by the present application;
[0048] Figure 6 It is another flowchart of a method for requirement acquisition provided by the present application;
[0049] Figure 7 It is a schematic structural diagram of a requirement acquisition apparatus provided by the present application;
[0050] Figure 8 The structural schematic diagram of an electronic device provided for this application. Specific embodiments
[0051] Next, the technical solutions in the embodiments of this application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of this application.
[0052] The term "including" and its variants used herein are open-ended, that is, "including but not limited to". The term "based on" is "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.
[0053] It should be noted that the concepts such as "first" and "second" mentioned in the disclosure of this application are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.
[0054] It should be noted that the modifications of "one" and "multiple" mentioned in the disclosure of this application are illustrative rather than restrictive. Those skilled in the art should understand that unless otherwise clearly stated in the context, it should be understood as "one or more".
[0055] This application can be used in many general or special computing device environments or configurations. For example: personal computers, server computers, handheld devices or portable devices, tablet devices, multi-processor devices, distributed computing environments including any of the above devices or equipment, and so on.
[0056] The embodiments of this application provide a method for obtaining requirements. This method can be applied to a product system to be updated. The method flow chart of the method for obtaining requirements is as Figure 1 shown, and specifically includes:
[0057] S101. Obtain a product requirements list.
[0058] In this embodiment, a product requirements list is obtained. Among them, the product requirements list is constructed based on user behavior habit data, and the user behavior habit data can be obtained through a preset acquisition path. The preset acquisition path includes but is not limited to: the user behavior database in the product system to be updated.
[0059] It should be noted that this embodiment does not limit the acquisition channels of user behavior habit data.
[0060] In this embodiment, the process of constructing a product requirement list based on user behavior habit data specifically includes the following steps: parsing the user behavior habit data to obtain multiple key data items, and then updating the preset product requirement list based on the key data items to obtain an updated product requirement list.
[0061] An example of the process of constructing a product requirement list based on user behavior habit data mentioned above is as follows:
[0062] For example, credit granting, loan disbursement, repayment, collection, etc. required in the loan process are all added to the product requirement list; there are multiple repayment methods, and common ones such as equal principal, equal principal and interest, and interest first and principal later also need to be added to the product requirement list;
[0063] Different customer groups have different needs and habits. For example, some customers are not used to being in debt. They only need a loan for a while, but they have the idea of repaying the money after their funds are turned over. Another part of the customers hope that the monthly repayment amount is fixed. Therefore, if the same product is targeted at customer groups that require two repayment methods, the product needs to support 2 repayment methods for customers to choose from; for another example, when logging in to the APP, some customers are used to logging in with passwords, some customers are not used to remembering passwords and are used to logging in with SMS verification codes, and some customers are used to using gesture passwords or fingerprint or face recognition. These are all added to the product requirement list.
[0064] In real life, customers need to verify their funds when studying abroad, buying a house, etc. However, if the customer's funds have been used to purchase time deposits, wealth management, etc. and cannot be flowed in time, the customer needs to open a deposit certificate; due to reasons such as time difference in credit reporting, there is a situation where the customer has repaid the loan but it is still not shown as repaid in the credit report. The customer may not be able to obtain a loan approval when applying for a mortgage. At this time, a settlement certificate needs to be opened. After receiving such customer needs, they are added to the product requirement list.
[0065] S102. Obtain the system function list of the product system to be updated.
[0066] In this embodiment, the system function list of the product system to be updated is obtained, where the system function list includes all function menus of the product system to be updated.
[0067] Refer to Figure 2 and the process of obtaining the system function list of the product system to be updated specifically includes the following steps:
[0068] S201. Determine the system function menu of the product system to be updated.
[0069] S202. Analyze the system function menu to obtain the hierarchical function menus included in the system function menu.
[0070] In this embodiment, analyze the system function menu to obtain the hierarchical function menus included in the system function menu package. Specifically, first perform a first-level menu analysis on the system function menu to obtain each first-level function menu included in the system function menu, and then perform a second-level menu analysis on the system function menu to obtain the second-level function menus under the first-level function menus, and so on until all analyses of the system function menu are completed.
[0071] An example of the process of analyzing the system function menu mentioned in this embodiment to obtain the hierarchical function menus included in the system function menu is as follows:
[0072] Sort by the system function menu level by level. First, sort out the system first-level function menus, such as credit inquiry, loan disbursement inquiry, repayment inquiry, and image file processing; then sort out the system second-level function menus (if any), such as under credit inquiry, there are credit application inquiry, credit anomaly handling menu, etc.; the fields that can be displayed under credit anomaly handling are "application time, name, ID number, node where the anomaly occurred, etc.".
[0073] S203. Build a system function list based on the hierarchical function menus.
[0074] In this embodiment, build a system function list based on the hierarchical function menus. Specifically, form the hierarchical function menus into a column in the system function list, and different hierarchical function menus correspond to different columns.
[0075] Refer to Figure 3 , and an example of the process of building a system function list based on the hierarchical function menus is as follows:
[0076] The first-level menus: credit, loan disbursement, repayment, and image file processing are written into a column in the function list (i.e., the system function list), and the second-level menus under credit, such as credit approval inquiry, credit anomaly handling, and credit cancellation, are written into another column in the function list.
[0077] S103. Build a product attribute list based on the product requirement list and the system function list.
[0078] In this embodiment, build a product attribute list based on the product requirement list and the system function list. Among them, the product attribute list includes at least multiple function attribute items and the corresponding selection items for the function attribute items. Optionally, it can also include the input items corresponding to the function attribute items so that users can fill in the input items according to their needs.
[0079] Refer to Figure 4, the process of constructing a product attribute list based on a product requirement list and a system function list specifically includes the following steps:
[0080] S401. Generate multiple functional attribute items and corresponding selection items based on the system function list.
[0081] In this embodiment, multiple functional attribute items and corresponding selection items for the functional attribute items are generated based on the system function list.
[0082] Similarly, refer to Figure 3 , the process of determining multiple functional attribute items and corresponding selection items based on the system function list is illustrated as follows:
[0083] For the secondary menu image file acquisition, a functional attribute item for image file transmission, corresponding real-time and asynchronous sftp selection items for image file transmission, and a description input item can be generated.
[0084] S402. Construct an initial product attribute list based on each functional attribute item and the corresponding selection item.
[0085] In this embodiment, based on each functional attribute item and the corresponding selection item, a preset list template is called to construct an initial product attribute list.
[0086] S403. Supplement the initial product attribute list based on the product requirement list to obtain the product attribute list.
[0087] In this embodiment, supplementing the initial product attribute list based on the product requirement list means adding relevant functions in the product requirement list to the initial product attribute list to obtain the product attribute list.
[0088] In this embodiment, the product requirement list includes multiple requirement items. Similarly, refer to Figure 3 , the requirement items include but are not limited to providing evidence, obtaining results in real time, multiple periods and being optional.
[0089] Specifically, the process of supplementing the initial product attribute list based on the product requirement list to obtain the product attribute list specifically includes the following steps:
[0090] For the requirement items included in the product requirement list, determine whether there are functional attribute items in the initial product attribute list that match the requirement items. If so, update the selectable items corresponding to the matched functional attribute items based on the requirement items to obtain the updated initial product attribute list. If not, determine the requirement item as an unmatched requirement item;
[0091] Generate functional attribute items corresponding to the unmatched requirement items and corresponding selection items;
[0092] Add the function attribute items corresponding to each unmatched requirement item and the selection items corresponding to the function attribute items to the updated initial product attribute list to obtain the product attribute list.
[0093] In this embodiment, first, match the requirement items included in the product requirement list with each function attribute item in the initial product attribute list. Specifically, for the requirement items included in the product requirement list, determine whether there is a function attribute item in the initial product attribute list that matches the requirement item. Specifically, it can be to calculate the similarity between the requirement item and the function attribute items in the initial product attribute list, determine the function attribute item corresponding to the maximum similarity, and when the maximum similarity is greater than the preset similarity threshold, determine that the function attribute item corresponding to the maximum similarity matches the requirement item; otherwise, it does not match. In this embodiment, if there is a function attribute item in the initial product attribute list that matches the requirement item, then based on this requirement item, update the selection items of the matched function attribute item. Specifically, keep the selection items unchanged, or add or delete the selection items, so as to obtain the updated initial product attribute list. Otherwise, determine this requirement item as an unmatched requirement item.
[0094] In this embodiment, generate the function attribute item corresponding to the unmatched requirement item and the selection item corresponding to this function attribute item. Optionally, an input item corresponding to this function attribute item can also be generated, and then write the function attribute item corresponding to the unmatched requirement item and the selection item corresponding to this function attribute item into the updated initial product attribute list, or write the function attribute item corresponding to the unmatched requirement item, the selection item corresponding to this function attribute item, and the input item into the updated initial product attribute list to obtain the product attribute list.
[0095] Optionally, refer to Figure 5 , Figure 5 which shows the function attribute items of the product attribute list, as well as the selection items and input items corresponding to the function attribute items.
[0096] S104. Send the product attribute list to the user terminal.
[0097] In this embodiment, in the form of a questionnaire survey, send the product attribute list to the user terminals of multiple users, so that users can fill in the product attribute list, that is, check the selection items corresponding to the function attribute items included in the product attribute list, or fill in the input items corresponding to the function attribute items.
[0098] S105. Obtain the result information of the user's filling in the product attribute list fed back by the user terminal, and based on the result information, obtain the target requirement, so that developers can update the to-be-updated system based on the target requirement.
[0099] In this embodiment, the result information of the user filling in the product attribute list fed back by the user terminal is obtained.
[0100] In this embodiment, based on the result information, a target requirement is obtained. Specifically, the result information is processed to obtain the target requirement, so that developers can update the tin system to be updated based on the target requirement.
[0101] Refer to Figure 6 , the process of obtaining the target requirement based on the result information specifically includes the following steps:
[0102] S601. Based on the result information, calculate the probability that the selected item in the product attribute list is selected and the probability that the user filling information corresponding to the input item is similar.
[0103] In this embodiment, based on the result information, the probability that the selected item in the product attribute list is selected and the probability that the user filling information corresponding to the input item is similar are calculated. Among them, the probability that the user filling information corresponding to the input item is similar refers to the proportion of the number of user filling information with a similarity greater than the preset threshold to the number of users participating in filling for the same input item.
[0104] S602. Based on the probability that the selected item in the product attribute list is selected and the probability that the user filling information corresponding to the input item is similar, determine the target information corresponding to the functional attribute item from the selected item corresponding to the functional attribute item and the user filling information corresponding to the input item.
[0105] In this embodiment, for the selected item and the input item corresponding to the functional attribute item included in the product attribute list, if the probability that the selected item is selected is greater than the preset first probability, then the selected item is used as the target information, otherwise the selected item is not used as the target information. If the probability that the user filling information corresponding to the input item is similar is greater than the preset second probability, then the user filling information is used as the target information.
[0106] S603. Based on the target information corresponding to each functional attribute item, obtain the target requirement.
[0107] In this implementation, based on the target information corresponding to each functional attribute item, the target requirement is obtained, that is, the target information corresponding to each functional attribute item is used as the target requirement.
[0108] In this implementation, optionally, before step S603, the following steps may further be included:
[0109] Update the preset requirement analysis template based on the target information corresponding to the functional attribute item.
[0110] Due to the ever-changing market, regulatory policies are not static, technological upgrades are rapid, and user needs are even more diverse. It is necessary to update the requirements analysis template in a timely manner to guide requirements analysis within a certain period.
[0111] In the requirements acquisition method provided by the embodiments of the present application, since the product attribute list is constructed based on the system functions of the product system to be updated and the user behavior habit data, by filling in this product attribute list, it helps users express their requirements more accurately, thereby obtaining relatively accurate user requirements. Moreover, most of the functions included in the obtained target requirements are functions already supported by the product system to be updated. Therefore, based on this target requirement, it is possible to quickly convert user requirements into the system functions of the application system.
[0112] It should be noted that although the operations are depicted in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain circumstances, multitasking and parallel processing may be beneficial.
[0113] It should be understood that the various steps described in the method embodiments disclosed in the present application may be executed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present application disclosed is not limited in this regard.
[0114] corresponding to Figure 1 the method described above, the embodiments of the present application also provide a requirements acquisition device for Figure 1 the specific implementation of the method in Figure 7 as shown, specifically including:
[0115] A first acquisition unit 701, configured to acquire a product requirements list; the product requirements list is constructed based on user behavior habit data;
[0116] A second acquisition unit 702, configured to acquire the system function list of the product system to be updated;
[0117] A construction unit 703, configured to construct a product attribute list based on the product requirements list and the system function list; at least multiple function attribute items and corresponding selection items of the function attribute items are included in the product attribute list;
[0118] A sending unit 704, configured to send the product attribute list to the user terminal;
[0119] A third acquisition unit 705, configured to acquire the result information filled in by the user for the product attribute list feedback by the user terminal, and obtain a target requirement based on the result information, so that developers can update the system to be updated based on the target requirement.
[0120] Since the product attribute list provided in the embodiment of the present application is constructed based on the system functions of the product system to be updated and the user behavior habit data, filling in the product attribute list helps the user express requirements more accurately, so as to obtain relatively accurate user requirements. Moreover, most of the functions included in the obtained target requirements are functions already supported by the product system to be updated. Therefore, based on the target requirements, it is possible to quickly convert user requirements into system functions of the application system.
[0121] In an embodiment of the present application, based on the foregoing solution, the second acquisition unit 702 is specifically configured to:
[0122] Determine the system function menu of the product system to be updated;
[0123] Parse the system function menu to obtain the hierarchical function menus included in the system function menu;
[0124] Based on the hierarchical function menus, construct a system function list.
[0125] In an embodiment of the present application, based on the foregoing solution, the construction unit 703 is specifically configured to:
[0126] Generate a plurality of function attribute items and corresponding selection items for the function attribute items based on the system function list;
[0127] Based on the respective function attribute items and the corresponding selection items for the function attribute items, construct an initial product attribute list;
[0128] Based on the product requirement list, supplement the initial product attribute list to obtain a product attribute list.
[0129] In an embodiment of the present application, based on the foregoing solution, the product requirement list includes a plurality of requirement items. When the construction unit 703 supplements the initial product attribute list based on the product requirement list to obtain a product attribute list, it is specifically configured to:
[0130] For the requirement items included in the product requirement list, determine whether there are function attribute items in the initial product attribute list that match the requirement items. If so, update the selectable items corresponding to the matched function attribute items based on the requirement items to obtain an updated initial product attribute list. If not, determine the requirement item as an unmatched requirement item;
[0131] Generate function attribute items corresponding to the unmatched requirement items and corresponding selection items for the function attribute items;
[0132] Add the function attribute items corresponding to each unmatched requirement item and the selection items corresponding to the function attribute items to the updated initial product attribute list to obtain a product attribute list.
[0133] In an embodiment of the present application, based on the foregoing solution, the product attribute list further includes input items corresponding to function attribute items.
[0134] In an embodiment of the present application, based on the foregoing solution, when the third acquisition unit 705 obtains a target requirement based on the result information, it specifically is used for:
[0135] Based on the result information, calculate the probability that the selection items in the product attribute list are selected and the probability that the user filling information corresponding to the input items is similar;
[0136] Based on the probability that the selection items in the product attribute list are selected and the probability that the user filling information of the input items is similar, determine the target information corresponding to the function attribute items from the selection items corresponding to the function attribute items and the user filling information corresponding to the input items;
[0137] Based on the target information corresponding to each function attribute item, obtain the target requirement.
[0138] In an embodiment of the present application, based on the foregoing solution, it can also be configured as:
[0139] An update unit, configured to update a preset requirement analysis template based on the target information corresponding to the function attribute items.
[0140] An embodiment of the present application further provides a storage medium, where the storage medium stores an instruction set, and when the instruction set runs, it executes the requirement acquisition method disclosed in any of the foregoing embodiments.
[0141] An embodiment of the present application further provides an electronic device, the structural schematic diagram of which is as Figure 8 shown, specifically including a memory 801 for storing at least one set of instruction sets; a processor 802 for executing the instruction sets stored in the memory, and implementing the requirement acquisition method disclosed in any of the foregoing embodiments by executing the instruction sets.
[0142] Although the subject matter has been described in language specific to structural features and / or methodological act logical actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms for implementing the claims.
[0143] Although several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the disclosure of this application. Certain features described in the context of separate embodiments can also be implemented combinatorially in a single embodiment. Conversely, the various features described in the context of a single embodiment can also be implemented separately or in any suitable sub-combination in multiple embodiments.
[0144] The above description is only a preferred embodiment of the disclosure of this application and an explanation of the technical principles applied. Those skilled in the art should understand that the scope of the disclosure involved in this application is not limited to the technical solutions formed by the specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosure concept. For example, the technical solutions formed by the mutual replacement of the above features with the technical features (but not limited to) having similar functions disclosed in this application.
Claims
1. A requirement acquisition method, characterized in that, Including: Obtain a list of product requirements; The product requirements list is constructed based on user behavior habit data; Obtain a list of system functions of the product system to be updated; Based on the product requirements list and the system function list, construct a product attribute list; The product attribute list at least includes multiple functional attribute items, corresponding selection items for the functional attribute items, and input items corresponding to the functional attribute items; Send the product attribute list to the user terminals of multiple users; Obtain the result information filled in by the users for the product attribute list fed back by each user terminal, and based on the result information, obtain target requirements, so that developers can update the system to be updated based on the target requirements; The obtaining the target requirements based on the result information includes: Based on the result information, calculate the probability that the selection items in the product attribute list are selected, and the probability that the user filling information corresponding to the input items is similar; the probability that the user filling information corresponding to the input items is similar refers to the proportion of the number of user filling information with a similarity greater than a preset threshold to the number of users participating in filling for the same input item; Based on the probability that the selection items in the product attribute list are selected and the probability that the user filling information corresponding to the input items is similar, determine the target information corresponding to the functional attribute items from the selection items corresponding to the functional attribute items and the user filling information corresponding to the input items; Based on the target information corresponding to each functional attribute item, obtain target requirements.
2. The method according to claim 1, wherein The obtaining the list of system functions of the product system to be updated includes: Determine the system function menu of the product system to be updated; Parse the system function menu to obtain the hierarchical function menus included in the system function menu; Based on the hierarchical function menus, construct a system function list.
3. The method according to claim 1, characterized in that, The constructing the product attribute list based on the product requirements list and the system function list includes: Based on the system function list, generate multiple functional attribute items and the corresponding selection items for the functional attribute items; Based on each functional attribute item and the corresponding selection item for the functional attribute item, construct an initial product attribute list; Based on the product requirements list, supplement the initial product attribute list to obtain a product attribute list.
4. The method according to claim 3, wherein The product requirements list includes multiple requirement items. The supplementing the initial product attribute list based on the product requirements list to obtain a product attribute list includes: For the requirement items included in the product requirements list, determine whether there are functional attribute items in the initial product attribute list that match the requirement items. If so, update the selectable items corresponding to the matched functional attribute items based on the requirement items to obtain an updated initial product attribute list. If not, determine the requirement item as an unmatched requirement item; Generate functional attribute items corresponding to the unmatched requirement items and the corresponding selection items for the functional attribute items; Add the functional attribute items corresponding to each unmatched requirement item and the corresponding selection items for the functional attribute items to the updated initial product attribute list to obtain a product attribute list.
5. The method according to claim 1, wherein Before obtaining the target requirements based on the target information corresponding to the functional attribute items, the following steps are also included: Update the preset requirement analysis template based on the target information corresponding to the functional attribute items.
6. A requirement acquisition device, characterized in that, It includes: A first acquisition unit for acquiring a product requirement list; The product requirement list is constructed based on user behavior habit data; A second acquisition unit for acquiring a system function list of the product system to be updated; A construction unit for constructing a product attribute list based on the product requirement list and the system function list; The product attribute list at least includes a plurality of functional attribute items, corresponding selection items for the functional attribute items, and input items corresponding to the functional attribute items; A sending unit for sending the product attribute list to the user terminals of multiple users; A third acquisition unit for acquiring the result information filled in by the users on the product attribute list feedback by each of the user terminals, and obtaining the target requirements based on the result information, so that developers can update the system to be updated based on the target requirements; When the third acquisition unit obtains the target requirements based on the result information, it specifically is used for: Based on the result information, calculate the probability that the selection items in the product attribute list are selected, and the probability that the user filling information corresponding to the input items is similar; the probability that the user filling information corresponding to the input items is similar refers to the proportion of the number of user filling information with a similarity greater than a preset threshold to the number of users participating in filling for the same input item; Based on the probability that the selection items in the product attribute list are selected and the probability that the user filling information corresponding to the input items is similar, determine the target information corresponding to the functional attribute items from the selection items corresponding to the functional attribute items and the user filling information corresponding to the input items; Obtain the target requirements based on the target information corresponding to each functional attribute item.
7. A storage medium, characterized in that, The storage medium stores an instruction set, wherein the instruction set, when executed by a processor, implements the requirement acquisition method according to any one of claims 1 to 5.
8. An electronic device, characterized in that, It includes: A memory for storing at least one set of instruction sets; A processor for executing the instruction sets stored in the memory, and implementing the requirement acquisition method according to any one of claims 1 to 5 by executing the instruction sets.
Citation Information
Patent Citations
Menu configuration method and device, terminal and readable storage medium
CN110597812A