CN114897415B - Product demand platform management method, device, terminal and storage medium - Google Patents
Product demand platform management method, device, terminal and storage medium Download PDFInfo
- Publication number
- CN114897415B CN114897415B CN202210607729.XA CN202210607729A CN114897415B CN 114897415 B CN114897415 B CN 114897415B CN 202210607729 A CN202210607729 A CN 202210607729A CN 114897415 B CN114897415 B CN 114897415B
- Authority
- CN
- China
- Prior art keywords
- demand
- product
- baseline
- library
- requirement
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 78
- 238000003860 storage Methods 0.000 title claims abstract description 14
- 230000008859 change Effects 0.000 claims description 30
- 238000013461 design Methods 0.000 claims description 29
- 238000000034 method Methods 0.000 claims description 22
- 238000011156 evaluation Methods 0.000 claims description 21
- 238000012545 processing Methods 0.000 claims description 9
- 238000012986 modification Methods 0.000 claims description 4
- 230000004048 modification Effects 0.000 claims description 4
- 238000007792 addition Methods 0.000 claims description 3
- 238000012217 deletion Methods 0.000 claims description 3
- 230000037430 deletion Effects 0.000 claims description 3
- 238000011161 development Methods 0.000 description 17
- 230000006870 function Effects 0.000 description 14
- 238000004519 manufacturing process Methods 0.000 description 9
- 238000012795 verification Methods 0.000 description 7
- 238000012356 Product development Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 6
- 238000012790 confirmation Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 6
- 238000004458 analytical method Methods 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000009826 distribution Methods 0.000 description 2
- 238000002898 library design Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
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/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Educational Administration (AREA)
- Game Theory and Decision Science (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Operations Research (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)
Abstract
The application relates to the field of product demand management, and particularly discloses a product demand platform management method, a device, a terminal and a storage medium, wherein a plurality of base line demand libraries are created according to the applicable product range of base line demands, and attributes are set for the base line demand libraries to mark the applicable product range of the base line demands contained in the base line demand libraries; creating a product requirement package aiming at a product to be processed, and setting attributes for the product requirement package; wherein the product requirement package setting attribute is consistent with the selectable item content of the attribute set by the baseline requirement library; based on the set attributes, matching a baseline demand library for the product demand package; and carrying all the baseline requirements in the matched baseline requirements library into corresponding product requirement packages. The application realizes unified management of all product requirements and improves management efficiency.
Description
Technical Field
The application relates to the field of product demand management, in particular to a product demand platform management method, a device, a terminal and a storage medium.
Background
The existing product demand management mode generally performs product demand management (including demand definition, design realization and verification) independently by taking a product as a unit, but a company generally has a plurality of product lines, each product line has a plurality of products, and each product can be updated at intervals, so that the current management mode has high management cost, low efficiency, high product development and production cost and low design multiplexing rate among products.
Disclosure of Invention
In order to solve the problems, the application provides a product demand platform management method, a device, a terminal and a storage medium, which realize unified management of all product demands and improve management efficiency.
In a first aspect, the present application provides a product demand platform management method, including the following steps:
creating a plurality of baseline demand libraries according to the applicable product range of the baseline demand, and setting attributes for the baseline demand libraries to mark the applicable product range of the contained baseline demand;
creating a product requirement package aiming at a product to be processed, and setting attributes for the product requirement package; wherein the product requirement package setting attribute is consistent with the selectable item content of the attribute set by the baseline requirement library;
based on the set attributes, matching a baseline demand library for the product demand package;
and carrying all the baseline requirements in the matched baseline requirements library into corresponding product requirement packages.
Further, the attributes set by the baseline requirements repository and the product requirements package include: product category, product platform, product algebra.
Further, the method further comprises:
the baseline demand library is divided into three levels according to the baseline demand applicable product range: l1, L2, and L3 levels;
wherein the baseline requirements in the L1-level baseline requirements library are applicable to all categories of products for all product lines;
the baseline requirements in the L2-level baseline requirements library are applicable to products of specific product categories, and different baseline requirements libraries are respectively established according to all product categories of the product line;
the baseline requirements in the L3-level baseline requirements library are applicable to all technical platforms and all algebraic products, and different baseline requirements libraries are respectively established according to the technical platforms and algebra selected by the product design.
Further, a hardware system baseline demand library and a software system baseline demand library are arranged under the L1-level baseline demand library.
Further, the method comprises the following steps:
performing new adding, modifying and deleting operations on the baseline requirements in the baseline requirements library by a user with authority;
after a new product demand is submitted, identifying whether the product demand can be used as a baseline demand or not in demand decision, and if so, distributing the product demand to a target baseline demand library;
when the requirement decision is made, if a certain baseline requirement in a certain baseline requirement library is identified to be no longer suitable for being placed in the baseline requirement library, executing an operation of deleting the baseline requirement from the baseline requirement library;
when a certain base line demand in a certain base line demand library is changed, after the demand decision agrees, adding the new base line demand after the change into the base line demand library, and deleting the old base line demand before the change.
Further, the method comprises the following steps:
when the base line demand in a certain base line demand library is changed, notifying a change point to a product management responsible person for evaluation, and confirming whether the corresponding product accepts the changed base line demand;
if the evaluation result is that the received result is received, automatically importing the changed baseline requirement into a product requirement package of the corresponding product;
if the evaluation result is refusal, the product requirement package of the corresponding product is not imported with the changed baseline requirement.
In a second aspect, the present application provides a product demand platform management apparatus, including,
a base line demand base creation module: creating a plurality of baseline demand libraries according to the applicable product range of the baseline demand, and setting attributes for the baseline demand libraries to mark the applicable product range of the contained baseline demand;
product demand package creation module: creating a product requirement package aiming at a product to be processed, and setting attributes for the product requirement package; wherein the product requirement package setting attribute is consistent with the selectable item content of the attribute set by the baseline requirement library;
and a matching module: based on the set attributes, matching a baseline demand library for the product demand package;
the demand bringing module: and carrying all the baseline requirements in the matched baseline requirements library into corresponding product requirement packages.
Further, the apparatus further comprises: the base line demand library management module and the demand change notification processing module;
a baseline demand library management module: the method comprises the steps that a user with authority is used for carrying out new addition, modification and deletion operations on the baseline requirements in a baseline requirement library; after a new product demand is submitted, identifying whether the product demand can be used as a baseline demand or not in demand decision, and if so, distributing the product demand to a target baseline demand library; when the requirement decision is made, if a certain baseline requirement in a certain baseline requirement library is identified to be no longer suitable for being placed in the baseline requirement library, executing an operation of deleting the baseline requirement from the baseline requirement library; when a certain baseline demand in a certain baseline demand library is changed, after the demand decision agrees, adding the new baseline demand after the change into the baseline demand library, and deleting the old baseline demand before the change;
the demand change notification processing module: when the base line demand in a certain base line demand library is changed, notifying a change point to a product management responsible person for evaluation, and confirming whether the corresponding product accepts the changed base line demand; if the evaluation result is that the received result is received, automatically importing the changed baseline requirement into a product requirement package of the corresponding product; if the evaluation result is refusal, the product requirement package of the corresponding product is not imported with the changed baseline requirement.
In a third aspect, a technical solution of the present application provides a terminal, including:
the memory is used for storing a product demand platform management program;
and the processor is used for realizing the steps of the product demand platformization management method according to any one of the above steps when executing the product demand platformization management program.
In a fourth aspect, the present application provides a computer readable storage medium, where a product demand platformization management program is stored, where the product demand platformization management program when executed by a processor implements the steps of the product demand platformization management method according to any one of the above claims.
The product demand platform management method, the device, the terminal and the storage medium provided by the application have the following beneficial effects compared with the prior art: 1) Customer perceived brand consistency is good: the serial products of the same company are consistent with the appearance characteristics, the user interfaces and the basic functions presented to the clients; 2) The product development cost is reduced: the functions with the same type of characteristics are developed once, the similar products are designed and reused, and the development cost and the development period are reduced; 3) The production cost is reduced: the multiplexing degree of each module among products is high, the types of materials are reduced, the multiplexing degree is high, and the cost can be reduced through mass purchase and production; 4) The quality stability is high: the design multiplexing degree of a new product is high, the verification and confirmation before marketing are sufficient, and the quality stability after marketing is high; 5) The management cost is low: most of the product demands are baseline demands, the baseline demands are uniformly managed, and the product demands can be used for multiple products only by once definition, analysis and decision making, so that the management cost is reduced.
Drawings
For a clearer description of embodiments of the application or of the prior art, the drawings that are used in the description of the embodiments or of the prior art will be briefly described, it being apparent that the drawings in the description below are only some embodiments of the application, and that other drawings can be obtained from them without inventive effort for a person skilled in the art.
Fig. 1 is a schematic flow chart of a product demand platform management method according to an embodiment of the present application.
FIG. 2 is a schematic diagram of a design architecture of a baseline demand library hierarchy in a product demand platform management method according to an embodiment of the present application.
Fig. 3 is a schematic block diagram of a product demand platform management apparatus according to an embodiment of the present application.
Fig. 4 is a schematic structural diagram of a terminal according to an embodiment of the present application.
Detailed Description
In order to better understand the aspects of the present application, the present application will be described in further detail with reference to the accompanying drawings and detailed description. It will be apparent that the described embodiments are only some, but not all, embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
The method is characterized in that the method comprises the steps of managing product requirements in a platform mode, creating a plurality of base line requirement libraries, providing base line requirements for products by the base line requirement libraries, uniformly analyzing and deciding all product requirements of a company after the product requirements are submitted by a requirement management system, identifying the base line requirements of the platform, uniformly defining, automatically distributing and automatically notifying the base line requirements after changing, uniformly designing, developing and verifying the platform requirements of each generation of products by establishing and maintaining the base line requirements of different levels, and inheriting the platform requirements of each generation of products.
Fig. 1 is a schematic flow chart of a product demand platform management method according to an embodiment of the present application, as shown in fig. 1, the method includes the following steps.
S101, creating a plurality of base line demand libraries according to the base line demand applicable product ranges, and setting attributes for the base line demand libraries to mark the product ranges applicable to the base line demands contained in the base line demand libraries.
A plurality of base line demand libraries are created in the demand management system, the base line demand libraries are used for archiving base line demands, the base line demands archived by each base line demand library are applicable to different product ranges, and the applicable product ranges of the base line demands in the base line demand libraries are marked by attributes. For example, the first baseline demand library has attribute 1 and the second baseline demand library has attribute 2, and the first baseline demand library archives the baseline demand applicable to the product having attribute 1 and the second baseline demand library archives the baseline demand applicable to the product having attribute 2.
The baseline requirement is a plateau requirement applicable to multiple products. The manager creates the product requirement according to the requirement and the actual situation, and decides whether the created product requirement can be used as the baseline requirement, and the product requirement which can be used as the baseline requirement can be archived to the corresponding baseline requirement library.
S102, creating a product requirement package aiming at a product to be processed, and setting attributes for the product requirement package; wherein the product requirement package setting attribute is consistent with the selectable item content of the attribute set by the baseline requirement library.
For products for which development of the standing decision is completed, a product requirement package is created, a base line requirement library is matched to acquire base line requirements, attributes are required to be set for the product requirement package, the product requirement package set attributes are consistent with selectable item contents of the attributes set by the base line requirement library, and the product requirement package and the base line requirement library are matched through the attributes.
S103, matching the baseline demand library for the product demand package based on the set attribute.
The product requirement package has the attribute, the base line requirement library is also configured with the attribute, after the product requirement package is created and the attribute is set, the base line requirement library meeting the attribute is searched, and the product requirement package with the same attribute and the base line requirement library are successfully matched.
S104, bringing all the baseline requirements in the matched baseline requirements library into corresponding product requirement packages.
The base line requirements in the base line requirements library matched with the product requirement package of a certain product are applicable to the product, and the configuration of the product requirements is completed by bringing all base line requirements in the matched base line requirements library into the product requirement package.
The product demand platform management method provided by the embodiment of the application comprises the following steps of 1) good brand consistency perceived by clients: the serial products of the same company are consistent with the appearance characteristics, the user interfaces and the basic functions presented to the clients; 2) The product development cost is reduced: the functions with the same type of characteristics are developed once, the similar products are designed and reused, and the development cost and the development period are reduced; 3) The production cost is reduced: the multiplexing degree of each module among products is high, the types of materials are reduced, the multiplexing degree is high, and the cost can be reduced through mass purchase and production; 4) The quality stability is high: the design multiplexing degree of a new product is high, the verification and confirmation before marketing are sufficient, and the quality stability after marketing is high; 5) The management cost is low: most of the product demands are baseline demands, the baseline demands are uniformly managed, and the product demands can be used for multiple products only by once definition, analysis and decision making, so that the management cost is reduced.
Based on the above embodiment, as a preferred implementation, the attributes set by the baseline requirement repository and the product requirement package include: product category, product platform, product algebra.
The attributes of the base line demand library and the product demand package are designed from three aspects of product category, product platform and product algebra, and the product range applicable to the archived base line demand is marked from the three aspects for the base line demand library. For example, the attributes of a certain baseline demand library are: category 1, platform 1, algebra 2. The attributes of a certain product requirement package are: category 1, platform 2, algebra 3.
On the basis of the above embodiment, as a preferred implementation manner, the method further includes:
the baseline demand library is divided into three levels according to the baseline demand applicable product range: l1, L2, and L3 levels;
wherein the baseline requirements in the L1-level baseline requirements library are applicable to all categories of products for all product lines;
the baseline requirements in the L2-level baseline requirements library are applicable to products of specific product categories, and different baseline requirements libraries are respectively established according to all product categories of the product line;
the baseline requirements in the L3-level baseline requirements library are applicable to all technical platforms and all algebraic products, and different baseline requirements libraries are respectively established according to the technical platforms and algebra selected by the product design.
Meanwhile, a hardware system baseline demand library and a software system baseline demand library are arranged under the L1-level baseline demand library.
The demand management system creates a plurality of baseline demand libraries, and the baseline demand libraries are layered according to the product range applicable to the archived baseline demand of the baseline demand libraries so as to facilitate management. As a preferred embodiment, the baseline demand library is divided into L1, L2, and L3 levels. Of course, the manager can also set different levels according to specific practical situations and user requirements, which does not affect the implementation of the embodiment of the present application.
On the basis of the above embodiment, as a preferred implementation manner, the method further includes:
performing new adding, modifying and deleting operations on the baseline requirements in the baseline requirements library by a user with authority;
after a new product demand is submitted, identifying whether the product demand can be used as a baseline demand or not in demand decision, and if so, distributing the product demand to a target baseline demand library;
when the requirement decision is made, if a certain baseline requirement in a certain baseline requirement library is identified to be no longer suitable for being placed in the baseline requirement library, executing an operation of deleting the baseline requirement from the baseline requirement library;
when a certain base line demand in a certain base line demand library is changed, after the demand decision agrees, adding the new base line demand after the change into the base line demand library, and deleting the old base line demand before the change.
The preferred embodiment realizes the management of the baseline demand library, and the manager with authority manages (adds, modifies and deletes) the baseline demands in the baseline demand library. At the same time, a decision is made as to whether the new product demand can be taken as a baseline demand. And detecting whether the baseline requirements in the baseline requirements library need to be deleted or changed according to the requirement timing.
On the basis of the above embodiment, as a preferred implementation manner, the method further includes:
when the base line demand in a certain base line demand library is changed, notifying a change point to a product management responsible person for evaluation, and confirming whether the corresponding product accepts the changed base line demand;
if the evaluation result is that the received result is received, automatically importing the changed baseline requirement into a product requirement package of the corresponding product;
if the evaluation result is refusal, the product requirement package of the corresponding product is not imported with the changed baseline requirement.
The base line requirements in the base line requirement library can be changed (such as new, modified and deleted), and for the product requirement package with the base line requirements, whether the changed base line requirements need to be received or not can be confirmed according to specific situations and user requirements. If accepted, the modified baseline requirements are brought into the product requirements package, and if not, the modified baseline requirements are not required to be brought into the product requirements package.
For further understanding of the present application, the following further describes a design of a product demand platform management method according to an embodiment of the present application, where the design of the method includes: base line demand library level design, base line demand library attribute design, automatic substitution of product demand packages into base line demand library design, base line demand library management scheme design, automatic distribution and notification of base line demands to product demand package design, base line demand platform development and verification design.
(1) Baseline requirements store tier design
FIG. 2 is a schematic diagram of a baseline repository hierarchy design architecture.
The method comprises the steps of designing a baseline demand library in a demand management system for archiving different types of baseline demands, and dividing the baseline demand library into three layers according to the use range of the baseline demands: l1 level, L2 level, L3 level.
The requirements in the L1-level baseline requirement library are applicable to all types of products of all product lines of a company, and a hardware system baseline requirement library and a software system baseline requirement library are arranged.
The L2-level baseline requirements are applicable to products of a certain product category, and different baseline requirement libraries are respectively built according to all the product categories of each product line of a company.
The L3-level baseline requirement is applicable to all technical platforms and all algebraic products of company product design, and different baseline requirement libraries are respectively established according to the technical platforms and algebra selected by the product design.
(2) Baseline requirements base attribute design
Three attributes are set for each baseline demand library and used for marking the applicable product range of the baseline library, and the three attributes comprise: product category, product platform, product algebra (as shown in fig. 2).
The "product category" sets a plurality of single options according to the product category of the company, for example, including: all products, product category 1, product category 2, product category 3, etc.
The "product platform" sets a plurality of single options according to all the technical platforms used in the design of the company product, for example, the product platform comprises: all of the platforms, platform 1, platform 2, platform 3, etc.
"product algebra" sets a plurality of single options according to all algebra of the company product, for example, contains: all algebra, algebra 1, algebra 2, algebra 3, etc.
(3) Automatic design for bringing product requirement package into baseline requirement library
Each product for completing development standing decision is formed by establishing a requirement package of the product in a requirement management system by a product management responsible person, and setting three attributes of the requirement package of the product: product category, product platform, product algebra. The contents of these three attributes are consistent with the selectable contents of the three attribute settings of the baseline requirements library design.
After the product demand package is established, the demand management system matches the product demand package with a baseline demand library in the system according to the three attributes, and automatically brings all the baseline demands in all the matched L1, L2 and L3 baseline demand libraries into the product demand package.
(4) Baseline requirements base management scheme design
Only the demand decision team can add, modify and delete product demands in the baseline demand library.
After a new product demand is submitted, after demand analysis, whether the demand can be used as a baseline demand is identified in demand decision-making, and then the demand is distributed to a target baseline demand library.
When a need is determined, a need is identified as no longer suitable for placement in a baseline need library, then a delete operation from the baseline library is performed.
When one demand in a certain base line demand library needs to be changed, after the demand decision agrees to the change, adding the new demand after the change into the base line demand library, and deleting the old demand before the change from the base line demand library.
(5) Automatic distribution and notification of baseline demand to product demand package functional design
When the product demand in a certain baseline demand library is changed (including new, modified and deleted), the demand management system automatically informs a change point to a product management responsible person for confirmation.
After receiving the confirmation notice, a product management responsible person organizes a product development team to evaluate the value, technical feasibility, development workload and problems and risks brought by the development of the product, determines whether the product is led in the newly added, modified and deleted product requirements, and adds the evaluation result into a requirement management system; when the evaluation result is 'accept', the demand change is automatically imported into the product demand package, and when the evaluation result is 'reject', the demand change is not imported into the product demand package.
(6) Baseline requirements platform development and validation management design
The development of the baseline requirement adopts a platform development mode, namely a certain development team uniformly analyzes, evaluates and designs the baseline requirement, and a certain test team uniformly tests and verifies the baseline requirement; and uniformly distributing the versions after passing the verification to each product.
The embodiment of the product demand platformization management method is described in detail above, and the embodiment of the application further provides a product demand platformization management device corresponding to the method based on the product demand platformization management method described in the embodiment.
Fig. 3 is a schematic block diagram of a product demand platform management apparatus according to an embodiment of the present application, where, as shown in fig. 3, the apparatus includes: a base line demand library creation module 101, a product demand package creation module 102, a matching module 103, a demand carrying-in module 104, a base line demand library management module 105, and a demand change notification processing module 106.
The base line demand library creation module 101: a plurality of base line demand libraries are created according to the base line demand applicable product ranges, and attributes are set for the base line demand libraries to mark the product ranges applicable to the base line demands contained in the base line demand libraries.
Product demand package creation module 102: creating a product requirement package aiming at a product to be processed, and setting attributes for the product requirement package; wherein the product requirement package setting attribute is consistent with the selectable item content of the attribute set by the baseline requirement library.
Matching module 103: based on the set attributes, a baseline demand library is matched for the product demand package.
Demand bring-in module 104: and carrying all the baseline requirements in the matched baseline requirements library into corresponding product requirement packages.
Baseline requirements library management module 105: the method comprises the steps that a user with authority is used for carrying out new addition, modification and deletion operations on the baseline requirements in a baseline requirement library; after a new product demand is submitted, identifying whether the product demand can be used as a baseline demand or not in demand decision, and if so, distributing the product demand to a target baseline demand library; when the requirement decision is made, if a certain baseline requirement in a certain baseline requirement library is identified to be no longer suitable for being placed in the baseline requirement library, executing an operation of deleting the baseline requirement from the baseline requirement library; when a certain base line demand in a certain base line demand library is changed, after the demand decision agrees, adding the new base line demand after the change into the base line demand library, and deleting the old base line demand before the change.
The demand change notification processing module 106: when the base line demand in a certain base line demand library is changed, notifying a change point to a product management responsible person for evaluation, and confirming whether the corresponding product accepts the changed base line demand; if the evaluation result is that the received result is received, automatically importing the changed baseline requirement into a product requirement package of the corresponding product; if the evaluation result is refusal, the product requirement package of the corresponding product is not imported with the changed baseline requirement.
The product requirement platformization management apparatus of this embodiment is used to implement the foregoing product requirement platformization management method, so that the specific implementation manner of this apparatus can be seen from the foregoing example portion of the product requirement platformization management method, so that the specific implementation manner of this apparatus can refer to the description of the corresponding examples of each portion, and will not be described herein.
In addition, since the product demand platformization management apparatus of the present embodiment is used to implement the foregoing product demand platformization management method, the function thereof corresponds to the function of the foregoing method, and will not be described herein again.
Fig. 4 is a schematic structural diagram of a terminal device 400 according to an embodiment of the present application, including: processor 410, memory 420, and communication unit 430. The processor 410 is configured to implement the product requirement flattening management program stored in the memory 420 by implementing the following steps:
creating a plurality of baseline demand libraries according to the applicable product range of the baseline demand, and setting attributes for the baseline demand libraries to mark the applicable product range of the contained baseline demand;
creating a product requirement package aiming at a product to be processed, and setting attributes for the product requirement package; wherein the product requirement package setting attribute is consistent with the selectable item content of the attribute set by the baseline requirement library;
based on the set attributes, matching a baseline demand library for the product demand package;
and carrying all the baseline requirements in the matched baseline requirements library into corresponding product requirement packages.
The application realizes the following steps: 1) Customer perceived brand consistency is good: the serial products of the same company are consistent with the appearance characteristics, the user interfaces and the basic functions presented to the clients; 2) The product development cost is reduced: the functions with the same type of characteristics are developed once, the similar products are designed and reused, and the development cost and the development period are reduced; 3) The production cost is reduced: the multiplexing degree of each module among products is high, the types of materials are reduced, the multiplexing degree is high, and the cost can be reduced through mass purchase and production; 4) The quality stability is high: the design multiplexing degree of a new product is high, the verification and confirmation before marketing are sufficient, and the quality stability after marketing is high; 5) The management cost is low: most of the product demands are baseline demands, the baseline demands are uniformly managed, and the product demands can be used for multiple products only by once definition, analysis and decision making, so that the management cost is reduced.
The terminal device 400 includes a processor 410, a memory 420, and a communication unit 430. The components may communicate via one or more buses, and it will be appreciated by those skilled in the art that the configuration of the server as shown in the drawings is not limiting of the application, as it may be a bus-like structure, a star-like structure, or include more or fewer components than shown, or may be a combination of certain components or a different arrangement of components.
The memory 420 may be used to store instructions for execution by the processor 410, and the memory 420 may be implemented by any type of volatile or nonvolatile memory terminal or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk. The execution of the instructions in memory 420, when executed by processor 410, enables terminal 400 to perform some or all of the steps in the method embodiments described below.
The processor 410 is a control center of the storage terminal, connects various parts of the entire electronic terminal using various interfaces and lines, and performs various functions of the electronic terminal and/or processes data by running or executing software programs and/or modules stored in the memory 420, and invoking data stored in the memory. The processor may be comprised of an integrated circuit (Integrated Circuit, simply referred to as an IC), for example, a single packaged IC, or may be comprised of a plurality of packaged ICs connected to the same function or different functions. For example, the processor 410 may include only a central processing unit (Central Processing Unit, simply CPU). In the embodiment of the application, the CPU can be a single operation core or can comprise multiple operation cores.
And a communication unit 430 for establishing a communication channel so that the storage terminal can communicate with other terminals. Receiving user data sent by other terminals or sending the user data to other terminals.
The application also provides a computer storage medium, which can be a magnetic disk, an optical disk, a read-only memory (ROM) or a random access memory (random access memory, RAM) and the like.
The computer storage medium stores a product demand platformization management program which when executed by the processor performs the steps of:
creating a plurality of baseline demand libraries according to the applicable product range of the baseline demand, and setting attributes for the baseline demand libraries to mark the applicable product range of the contained baseline demand;
creating a product requirement package aiming at a product to be processed, and setting attributes for the product requirement package; wherein the product requirement package setting attribute is consistent with the selectable item content of the attribute set by the baseline requirement library;
based on the set attributes, matching a baseline demand library for the product demand package;
and carrying all the baseline requirements in the matched baseline requirements library into corresponding product requirement packages.
The application realizes the following steps: 1) Customer perceived brand consistency is good: the serial products of the same company are consistent with the appearance characteristics, the user interfaces and the basic functions presented to the clients; 2) The product development cost is reduced: the functions with the same type of characteristics are developed once, the similar products are designed and reused, and the development cost and the development period are reduced; 3) The production cost is reduced: the multiplexing degree of each module among products is high, the types of materials are reduced, the multiplexing degree is high, and the cost can be reduced through mass purchase and production; 4) The quality stability is high: the design multiplexing degree of a new product is high, the verification and confirmation before marketing are sufficient, and the quality stability after marketing is high; 5) The management cost is low: most of the product demands are baseline demands, the baseline demands are uniformly managed, and the product demands can be used for multiple products only by once definition, analysis and decision making, so that the management cost is reduced.
It will be apparent to those skilled in the art that the techniques of embodiments of the present application may be implemented in software plus a necessary general purpose hardware platform. Based on such understanding, the technical solution in the embodiments of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium such as a U-disc, a mobile hard disc, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk or an optical disk, etc. various media capable of storing program codes, including several instructions for causing a computer terminal (which may be a personal computer, a server, or a second terminal, a network terminal, etc.) to execute all or part of the steps of the method described in the embodiments of the present application.
In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The foregoing disclosure is merely illustrative of the preferred embodiments of the application and the application is not limited thereto, since modifications and variations may be made by those skilled in the art without departing from the principles of the application.
Claims (7)
1. The product demand platform management method is characterized by comprising the following steps of:
creating a plurality of baseline demand libraries according to the applicable product range of the baseline demand, and setting attributes for the baseline demand libraries to mark the applicable product range of the contained baseline demand;
creating a product requirement package aiming at a product to be processed, and setting attributes for the product requirement package; wherein the product requirement package setting attribute is consistent with the selectable item content of the attribute set by the baseline requirement library;
based on the set attributes, matching a baseline demand library for the product demand package;
bringing all the baseline requirements in the matched baseline requirements library into corresponding product requirements packages;
wherein, the attributes set by the baseline demand library and the product demand package include: product category, product platform, product algebra;
the method further comprises the steps of:
the baseline demand library is divided into three levels according to the baseline demand applicable product range: l1, L2, and L3 levels;
wherein the baseline requirements in the L1-level baseline requirements library are applicable to all categories of products for all product lines;
the baseline requirements in the L2-level baseline requirements library are applicable to products of specific product categories, and different baseline requirements libraries are respectively established according to all product categories of the product line;
the baseline requirements in the L3-level baseline requirement library are applicable to all technical platforms and all algebraic products, and different baseline requirement libraries are respectively established according to the technical platforms and algebra selected by the product design;
and setting a hardware system baseline demand library and a software system baseline demand library under the L1-level baseline demand library.
2. The product demand platform management method as claimed in claim 1, further comprising the steps of:
performing new adding, modifying and deleting operations on the baseline requirements in the baseline requirements library by a user with authority;
after a new product demand is submitted, identifying whether the product demand can be used as a baseline demand or not in demand decision, and if so, distributing the product demand to a target baseline demand library;
when the requirement decision is made, if a certain baseline requirement in a certain baseline requirement library is identified to be no longer suitable for being placed in the baseline requirement library, executing an operation of deleting the baseline requirement from the baseline requirement library;
when a certain base line demand in a certain base line demand library is changed, after the demand decision agrees, adding the new base line demand after the change into the base line demand library, and deleting the old base line demand before the change.
3. The product demand platform management method as claimed in claim 2, further comprising the steps of:
when the base line demand in a certain base line demand library is changed, notifying a change point to a product management responsible person for evaluation, and confirming whether the corresponding product accepts the changed base line demand;
if the evaluation result is that the received result is received, automatically importing the changed baseline requirement into a product requirement package of the corresponding product;
if the evaluation result is refusal, the product requirement package of the corresponding product is not imported with the changed baseline requirement.
4. A product demand platform management device is characterized by comprising,
a base line demand base creation module: creating a plurality of baseline demand libraries according to the applicable product range of the baseline demand, and setting attributes for the baseline demand libraries to mark the applicable product range of the contained baseline demand;
product demand package creation module: creating a product requirement package aiming at a product to be processed, and setting attributes for the product requirement package; wherein the product requirement package setting attribute is consistent with the selectable item content of the attribute set by the baseline requirement library;
and a matching module: based on the set attributes, matching a baseline demand library for the product demand package;
the demand bringing module: bringing all the baseline requirements in the matched baseline requirements library into corresponding product requirements packages;
wherein, the attributes set by the baseline demand library and the product demand package include: product category, product platform, product algebra;
the base line demand base creation module sets attributes for the base line demand base to mark the range of products applicable to the base line demand contained in the base line demand base, and specifically comprises the following steps: the baseline demand library is divided into three levels according to the baseline demand applicable product range: l1, L2, and L3 levels; wherein the baseline requirements in the L1-level baseline requirements library are applicable to all categories of products for all product lines; the baseline requirements in the L2-level baseline requirements library are applicable to products of specific product categories, and different baseline requirements libraries are respectively established according to all product categories of the product line; the baseline requirements in the L3-level baseline requirement library are applicable to all technical platforms and all algebraic products, and different baseline requirement libraries are respectively established according to the technical platforms and algebra selected by the product design;
and setting a hardware system baseline demand library and a software system baseline demand library under the L1-level baseline demand library.
5. The product demand platformization management apparatus of claim 4, further comprising: the base line demand library management module and the demand change notification processing module;
a baseline demand library management module: the method comprises the steps that a user with authority is used for carrying out new addition, modification and deletion operations on the baseline requirements in a baseline requirement library; after a new product demand is submitted, identifying whether the product demand can be used as a baseline demand or not in demand decision, and if so, distributing the product demand to a target baseline demand library; when the requirement decision is made, if a certain baseline requirement in a certain baseline requirement library is identified to be no longer suitable for being placed in the baseline requirement library, executing an operation of deleting the baseline requirement from the baseline requirement library; when a certain baseline demand in a certain baseline demand library is changed, after the demand decision agrees, adding the new baseline demand after the change into the baseline demand library, and deleting the old baseline demand before the change;
the demand change notification processing module: when the base line demand in a certain base line demand library is changed, notifying a change point to a product management responsible person for evaluation, and confirming whether the corresponding product accepts the changed base line demand; if the evaluation result is that the received result is received, automatically importing the changed baseline requirement into a product requirement package of the corresponding product; if the evaluation result is refusal, the product requirement package of the corresponding product is not imported with the changed baseline requirement.
6. A terminal, comprising:
the memory is used for storing a product demand platform management program;
a processor for implementing the steps of the product demand platformization management method according to any of claims 1-3 when executing the product demand platformization management program.
7. A computer readable storage medium, wherein a product demand platformization management program is stored on the readable storage medium, and the product demand platformization management program, when executed by a processor, implements the steps of the product demand platformization management method according to any one of claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210607729.XA CN114897415B (en) | 2022-05-31 | 2022-05-31 | Product demand platform management method, device, terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210607729.XA CN114897415B (en) | 2022-05-31 | 2022-05-31 | Product demand platform management method, device, terminal and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114897415A CN114897415A (en) | 2022-08-12 |
| CN114897415B true CN114897415B (en) | 2023-11-07 |
Family
ID=82726297
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210607729.XA Active CN114897415B (en) | 2022-05-31 | 2022-05-31 | Product demand platform management method, device, terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114897415B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108958792A (en) * | 2018-07-03 | 2018-12-07 | 郑州云海信息技术有限公司 | Product demand management method and system in a kind of software development process |
| CN110852701A (en) * | 2019-10-18 | 2020-02-28 | 京东数字科技控股有限公司 | Product demand management method, device and system |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11243505B2 (en) * | 2015-03-16 | 2022-02-08 | Rockwell Automation Technologies, Inc. | Cloud-based analytics for industrial automation |
| US10769721B2 (en) * | 2016-10-31 | 2020-09-08 | Accenture Global Solutions Limited | Intelligent product requirement configurator |
| TWI647648B (en) * | 2016-12-30 | 2019-01-11 | 國家中山科學研究院 | Product development management system |
-
2022
- 2022-05-31 CN CN202210607729.XA patent/CN114897415B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108958792A (en) * | 2018-07-03 | 2018-12-07 | 郑州云海信息技术有限公司 | Product demand management method and system in a kind of software development process |
| CN110852701A (en) * | 2019-10-18 | 2020-02-28 | 京东数字科技控股有限公司 | Product demand management method, device and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114897415A (en) | 2022-08-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10318412B1 (en) | Systems, methods, and apparatus for dynamic software generation and testing | |
| US10289409B2 (en) | Systems, methods, and apparatus for migrating code to a target environment | |
| US8266426B2 (en) | Hardware certification based on certifying development processes | |
| CN111143358A (en) | Report configuration method and system | |
| CN110275861A (en) | Date storage method and device, storage medium, electronic device | |
| CN110362473A (en) | Test optimization method and device, storage medium, the terminal of environment | |
| CN110959165A (en) | Techniques for automatically verifying functionality of offers in a cloud service broker system | |
| CN112667695A (en) | Insurance data information generation method and device, server and storage medium | |
| CN115993966B (en) | Application development system and method | |
| US20200379982A1 (en) | Information processing system and method of controlling information processing system | |
| CN112015651A (en) | Data processing method and device | |
| CN112581201A (en) | Mobile open platform for industrial interconnection manufacturing and implementation method | |
| US9495367B2 (en) | System and method for performing a software comparison | |
| CN114897415B (en) | Product demand platform management method, device, terminal and storage medium | |
| CN115130959B (en) | Method, system, terminal and storage medium for generating spare part BOM | |
| CN110795674A (en) | Configuration updating method and device | |
| US8296258B2 (en) | Automated channel market data extraction, validation and transformation | |
| WO2014130790A1 (en) | Supplier analysis and verification system and method | |
| CN113568869A (en) | File management method, management platform and computer readable storage medium | |
| CN113506095A (en) | Order dynamic rule checking and distributing method | |
| US9575973B2 (en) | System and method for systematically removing customer personal information from an electronic device | |
| CN109471790A (en) | Send nuclear parameter comparison method and device, computer installation and readable storage medium storing program for executing | |
| CN112860780B (en) | Data export method and device and terminal equipment | |
| CN116976657A (en) | Method, system, terminal and medium for inquiring job title reporting standard | |
| CN115421776A (en) | Application building method and device, computer storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |