CN115934040A - Demand analysis method and device, electronic equipment and storage medium - Google Patents
Demand analysis method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115934040A CN115934040A CN202211460728.3A CN202211460728A CN115934040A CN 115934040 A CN115934040 A CN 115934040A CN 202211460728 A CN202211460728 A CN 202211460728A CN 115934040 A CN115934040 A CN 115934040A
- Authority
- CN
- China
- Prior art keywords
- software development
- requirement
- causal relationship
- requirements
- sub
- 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.)
- Pending
Links
Images
Classifications
-
- 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
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses a demand analysis method, a demand analysis device, electronic equipment and a storage medium, wherein the method comprises the following steps: acquiring a software development requirement, and splitting the software development requirement to obtain a plurality of sub-requirements; establishing a problem map based on a plurality of the sub-requirements; generating a plurality of causal relationship links based on the causal relationship in the problem map; and analyzing the software development requirement based on a plurality of causal relationship links to judge whether the software development requirement is reasonable. The invention solves the technical problems that whether the demand is reasonable or not and the field involving change cannot be judged quickly in the prior art, and the demand is inconvenient to deal with when meeting the demand change.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a demand analysis method and device, electronic equipment and a storage medium.
Background
The need essentially pertains to a capability or goal that the system or software must meet. Demand management belongs to a systematic mode, can accurately acquire, organize and record all kinds of demands, and present demand management has many places not enough, specific:
the requirement is not clear, namely, the user cannot put forward a complete detailed requirement, so that the requirement is not clear, the requirement of the user cannot be completely known at one time, and the requirement of the user to participate in the system development process is excessive; ambiguous requirements account for the resulting software rework and valuable time waste;
the change has a large influence on the project, causes a large amount of resource consumption, and simultaneously reduces the quality of the product;
the demand frequently changes: the requirements change too much, the changing or adding requirements mean that a user temporarily puts down the current project work, modifies the previous program according to the request, continuously changes the new functions to be realized, the completion of the project seems to be remote and indefinite, which seems to be the problem of the user, but also exposes the fault of the developer in the project management;
a demand management state: the change state is difficult to master and control, and real-time tracking is lacking.
Therefore, a method for analyzing a software development requirement capable of analyzing whether a requirement is reasonable is needed, which can quickly determine whether the requirement is reasonable and quickly deal with the requirement change in the field of the change of the requirement, so as to quickly make a processing scheme.
Disclosure of Invention
The present invention is directed to overcoming the above technical deficiencies, and providing a method, an apparatus, an electronic device and a storage medium for analyzing a demand in the field of financial technology or other related technologies, which solve the technical problems in the prior art that it is not possible to quickly determine whether the demand is reasonable, and the field involves changes, and the demand is inconvenient to deal with when changing.
In order to achieve the technical purpose, the invention adopts the following technical scheme:
in a first aspect, the present invention provides a demand analysis method, including the steps of:
acquiring a software development requirement, and splitting the software development requirement to obtain a plurality of sub-requirements;
establishing a problem map based on a plurality of the sub-requirements;
generating a plurality of causal relationship links based on the causal relationship in the problem map;
and analyzing the software development requirement based on a plurality of causal relationship links to judge whether the software development requirement is reasonable.
In some embodiments, the obtaining a software development requirement, and splitting the software development requirement to obtain a plurality of sub-requirements includes:
the method comprises the steps of obtaining software development requirements, and generating a plurality of problem domains representing sub-requirements based on the software development requirements, wherein the problem domains have sharing phenomena and causal relationships among the sharing phenomena.
In some embodiments, said creating a problem map based on a plurality of said sub-requirements comprises:
modeling the software development requirement based on each sub-requirement to obtain an initial problem map;
and expanding the initial problem map based on the initial problem map and the sharing phenomena and the causal relationship among the sharing phenomena among the problem domains corresponding to the sub-demands, so as to add a causal relationship attribute to the initial problem map and obtain the problem map.
In some embodiments, the problem map is plotted by UML.
In some embodiments, the generating a number of causal links based on the causal relationships in the problem map comprises:
converting the problem graph into a script, wherein the script has path information representing a causal relationship;
and analyzing the script, and generating a plurality of causal relationship links based on the path information in the script.
In some embodiments, the analyzing the software development requirement to determine whether the software development requirement is reasonable based on a number of the causal links includes:
and judging whether redundant processes exist in the causal relationship links or not based on the plurality of causal relationship links, if so, judging whether the software development requirement is reasonable, otherwise, judging that the software development requirement is unreasonable.
In some embodiments, the demand analysis method further comprises:
and when the software development requirement is unreasonable, sending out prompt information of requirement error.
In a second aspect, the present invention further provides a demand analysis apparatus, including:
the requirement splitting module is used for acquiring a software development requirement and splitting the software development requirement to obtain a plurality of sub-requirements;
the problem map building module is used for building a problem map based on the plurality of sub-requirements;
the causal relationship link establishing module is used for generating a plurality of causal relationship links based on the causal relationship in the problem map;
and the analysis module is used for analyzing the software development requirement based on the causal relationship links so as to judge whether the software development requirement is reasonable.
In a third aspect, the present invention also provides an electronic device, including: a processor and a memory;
the memory having stored thereon a computer program executable by the processor;
the processor, when executing the computer program, implements the steps in the demand analysis method as described above.
In a fourth aspect, the present invention also provides a computer readable storage medium storing one or more programs, the one or more programs being executable by one or more processors to implement the steps in the demand analysis method as described above.
Compared with the prior art, the demand analysis method, the demand analysis device, the electronic equipment and the storage medium provided by the invention have the advantages that firstly, the software development demand is obtained, and the software development demand is split to obtain a plurality of sub-demands; then establishing a problem map based on a plurality of the sub-requirements; then generating a plurality of causal relationship links based on the causal relationship in the problem map; and finally, analyzing the software development requirement based on a plurality of causal relationship links to judge whether the software development requirement is reasonable. The problem domain oriented requirement change analysis method can help products to better analyze requirements, and provides a method for checking whether the association of each domain is correct or not and whether the relationship chain of the problem domain is complete or not through the causal relationship, wherein the newly added requirements are directly added into the problem diagram to regenerate a new relationship diagram according to the causal relationship, so that whether the relationship chain of the current requirements is reasonable or not can be clearly seen. Therefore, whether the requirement is reasonable or not and the field involving change can be judged, and the treatment scheme can be rapidly made by rapidly responding when the requirement is changed.
Drawings
FIG. 1 is a flow chart of a method for demand analysis provided by an embodiment of the present invention;
FIG. 2 is a diagram illustrating an embodiment of a causal link in a demand analysis method according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating another embodiment of a causal link in a demand analysis method according to an embodiment of the present invention;
fig. 4 is a flowchart of step S200 in the demand analysis method according to the embodiment of the present invention;
FIG. 5 is a flowchart of step S300 in the demand analysis method according to the embodiment of the present invention;
FIG. 6 is a functional block diagram of a demand analysis apparatus according to an embodiment of the present invention;
fig. 7 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Referring to fig. 1, fig. 1 is a schematic flow chart of a demand analysis method according to an embodiment of the present invention, which can be used in software development demand analysis in the financial field to facilitate management of software development demands. The demand analysis method according to the present invention can be executed by an electronic device, which can perform operations such as receiving or sending data, and can be various electronic devices that have a display screen and support web browsing, including but not limited to smart phones, tablet computers, portable computers, desktop servers, and the like. As shown in fig. 1, the method specifically includes the following steps S100 to S400.
S100, acquiring a software development requirement, and splitting the software development requirement to obtain a plurality of sub-requirements.
In this embodiment, in order to implement modeling of software development requirements, multiple relation chains need to be found, and a complex requirement is split into multiple sub-requirements, thereby simplifying a problem model. Specifically, the method provided by the invention focuses on the problem corresponding to the software development requirement, the software development requirement splitting is the splitting of the problem, a complex problem is split into a plurality of simple problems, the sharing phenomenon among the sub-requirements and the causal relationship among the sharing phenomena can be obtained after the splitting, and the business process of the system is understood by analyzing the sharing phenomenon among the sub-requirements and the causal relationship among the sharing phenomena and combining the real scene behind the requirement. Wherein the sharing phenomenon is shared by two or more problem domains which are related to each other, but can be controlled by only one problem domain.
For example, the requirement is that a device capable of identifying an access card judges the access right through a sensor, and the information of the access card swiped is stored in a database and used for judging the basis of information such as attendance at the later stage. The overall problem can therefore be broken down into three problems: the embodiment of the invention does not pay attention to what the solution of the modification is, but pay attention to what the problem is, that is, what problem needs to be solved, and the function that the system needs to realize to solve the problem.
S200, establishing a problem map based on the plurality of sub-requirements.
In this embodiment, after the problem corresponding to the software development requirement is split, the problem framework is used to model the software development requirement, and a problem graph is established, which is composed of a set of machine domain, problem domain, and requirement, and explicitly expresses the interaction relationship between the computing component and the physical component. The problem map comprises a machine domain, a problem domain and a requirement, wherein the machine domain and the requirement are in an interface interaction connection mode, and the requirement and the problem domain are in a requirement reference connection mode.
S300, generating a plurality of causal relationship links based on the causal relationship in the problem map.
In this embodiment, a causal link in the demand, that is, a is found based on the causal relationship, and a series of subsequent processes are directly triggered by the causal link, which is called a causal link, where the causal link is a set composed of multiple shared phenomena between the machine field and the demand, and the causal relationships in the same direction exist between adjacent elements in the set, and the causal link can be obtained from the problem map according to the problem map. The requirements can be visually represented through the causal relationship link, and whether the requirements are reasonable or not is analyzed. Specifically, whether the association of each domain is correct or not is checked, whether the relation chain of the problem domain is complete or not is checked, the newly added requirement is directly added into the problem graph, and the new relation graph is regenerated according to the causal relation, so that whether the relation chain of the current requirement is reasonable or not can be clearly seen, whether the requirement is reasonable or not and the fields involving change can be judged, the requirement can be rapidly responded when the requirement is changed, and the processing scheme can be rapidly made.
Illustratively, if a phenomenon S causes R to occur, S and R are direct causal relationships, and if a path is found that contains S to R, it is a subset of the problematic paths. The causal link in the graph is obtained from the requirement to the machine domain and back to the model of the requirement according to the problem framework model. For example, if there is a sharing phenomenon d in the problem diagram, which results in another sharing phenomenon b, and the sharing phenomenon b results in a sharing phenomenon a, and the sharing phenomenon a results in a sharing phenomenon d, then a causal link, denoted as d- > b- > a- > e, can be obtained where the sharing phenomenon a results in the sharing phenomenon b, which results in the sharing phenomenon c, which results in the sharing phenomenon d.
S400, analyzing the software development requirement based on the plurality of causal relationship links to judge whether the software development requirement is reasonable.
In this embodiment, the entrance guard for card swiping of a company is taken as an example for explanation: fig. 2 is a problem diagram drawn based on causal relationships between problem domains, all existing functions should be in the causal relationship diagram, and if one function alone is not in the causal relationship diagram, it is very likely that a vulnerability exists in the system. The overall process that routing according to the cause and effect relationship is from the requirement to the machine field to the requirement shows that two cause and effect links d- > b- > a- > e and f- > c- > a- > e coexist in the diagram, so that the requirement can be visually represented and analyzed. If the effect shown in fig. 3 is shown, it can be seen that the data warehousing domain is not in any causal link, so that it is problematic, and the data warehousing domain needs to be structured, that is, the causal link has a redundant flow or has a problem, and it is obvious through the causal link.
According to the embodiment of the invention, firstly, a software development requirement is obtained, and the software development requirement is split to obtain a plurality of sub-requirements; then establishing a problem map based on a plurality of the sub-requirements; then generating a plurality of causal relationship links based on the causal relationship in the problem map; and finally, analyzing the software development requirement based on a plurality of causal relationship links to judge whether the software development requirement is reasonable. The problem domain oriented requirement change analysis method can help products to better analyze requirements, and provides a method for checking whether the association of each domain is correct or not and whether the relationship chain of the problem domain is complete or not through the causal relationship, wherein the newly added requirements are directly added into the problem diagram to regenerate a new relationship diagram according to the causal relationship, so that whether the relationship chain of the current requirements is reasonable or not can be clearly seen. Therefore, whether the requirement is reasonable or not and the field involving change can be judged, and the requirement can be quickly dealt with when meeting the requirement change, so that a processing scheme can be quickly made.
In some embodiments, the step S100 specifically includes:
the method comprises the steps of obtaining software development requirements, and generating a plurality of problem domains representing sub-requirements based on the software development requirements, wherein shared phenomena and causal relationships among the shared phenomena exist among the problem domains.
In this embodiment, before modeling the demand, multiple relation chains are found, and the complex demand is split into multiple sub-demands, so that the problem model is simplified, and the split sub-demands have a sharing phenomenon and a causal relationship of the sharing phenomenon.
In some embodiments, referring to fig. 4, the step S200 specifically includes:
s210, modeling the software development requirement based on each sub-requirement to obtain an initial problem map;
s220, expanding the initial problem map based on the initial problem map, the sharing phenomena among the problem domains corresponding to the sub-requirements and the causal relationship among the sharing phenomena, so as to add a causal relationship attribute to the initial problem map, and then obtaining the problem map.
In this embodiment, a problem framework is first adopted to model user requirements to obtain an initial problem map, which is composed of a set of machine fields, problem fields, and requirements, and then cause-effect attributes are added to the problem map, the designed initial problem map is expanded, and cause-effect relationships between shared phenomena are also represented in the problem map, where a relationship is directly triggered, a phenomenon between problem domains is controlled by some problem domains, and these phenomena trigger other phenomena, which are referred to as cause-effect relationships between these two phenomena.
In some embodiments, the problem map is plotted by UML.
In this embodiment, the modeling is performed by UML, and Un-enhanced model i ng Language (UML), also called unified modeling Language or standard modeling Language, is an OMG standard, which is a graphical Language supporting modeling and software system development, and provides modeling and visualization support for all stages of software development, including from requirement analysis to specification, to configuration and configuration. The method not only unifies the expression methods of Booch, rumbaugh and Jacobson, but also further develops the expression methods, and finally unifies the expression methods into the standard modeling language accepted by the public.
In some embodiments, referring to fig. 5, the step S300 specifically includes:
s310, converting the problem graph into a script, wherein the script has path information representing a causal relationship;
s320, analyzing the script, and generating a plurality of causal relationship links based on the path information in the script.
In this embodiment, the causal relationship chain is obtained by analyzing a problem graph, the problem graph may be converted into a script, and the causal relationship chain is obtained by analyzing a path relationship in the script. And then, judging whether the demands are reasonable or not by looking at the condition that the demands of the function points are not in a complete chain from the complete demands to the machine domain to the demands.
In some embodiments, the step S400 specifically includes:
and judging whether the causal relationship links have redundant processes or not based on the plurality of causal relationship links, if so, judging whether the software development requirement is reasonable, otherwise, judging that the software development requirement is unreasonable.
In the embodiment, whether the software development requirement is reasonable is judged through the causal relationship link, if the causal relationship link has a redundant flow or has a problem, the software development requirement is unreasonable, otherwise, the software development requirement is reasonable, the method is simple and convenient, and can help a product to better analyze the requirement. Therefore, whether the requirement is reasonable or not and the field involving change can be judged, and the treatment scheme can be rapidly made by rapidly responding when the requirement is changed.
In some embodiments, the demand analysis method further comprises:
and when the software development requirement is unreasonable, sending out prompt information of requirement error.
In the embodiment, when the software development requirement is unreasonable, prompt information of a requirement error is sent out, and the prompt information can prompt the reason of the requirement error, such as which causal relationship link is wrong, so that a worker can change and adjust the requirement quickly and conveniently, and the software development speed is accelerated.
According to the technical scheme provided by the invention, firstly, a software development requirement is obtained, and the software development requirement is split to obtain a plurality of sub-requirements; then establishing a problem map based on a plurality of the sub-requirements; then generating a plurality of causal relationship links based on the causal relationship in the problem map; and finally, analyzing the software development requirement based on a plurality of causal relationship links to judge whether the software development requirement is reasonable. The problem domain oriented requirement change analysis method can help products to better analyze requirements, and provides a method for checking whether the association of each domain is correct or not and whether the relationship chain of the problem domain is complete or not through the causal relationship, wherein the newly added requirements are directly added into the problem diagram to regenerate a new relationship diagram according to the causal relationship, so that whether the relationship chain of the current requirements is reasonable or not can be clearly seen. Therefore, whether the requirement is reasonable or not and the field involving change can be judged, and the treatment scheme can be rapidly made by rapidly responding when the requirement is changed.
Referring to fig. 6, the demand analysis apparatus according to another embodiment of the present invention includes a demand splitting module 11, a problem map establishing module 12, a causal link establishing module 13, and an analysis module 14.
The requirement splitting module 11 is configured to obtain a software development requirement, split the software development requirement to obtain multiple sub-requirements.
The problem map creating module 12 is configured to create a problem map based on the plurality of sub-requirements.
The causal relationship link establishing module 13 is configured to generate a plurality of causal relationship links based on causal relationships in the problem map.
The analysis module 14 is configured to analyze the software development requirement based on a plurality of causal relationship links to determine whether the software development requirement is reasonable.
In the embodiment, a software development requirement is firstly obtained, and the software development requirement is split to obtain a plurality of sub-requirements; then establishing a problem map based on a plurality of the sub-requirements; then generating a plurality of causal relationship links based on the causal relationship in the problem map; and finally, analyzing the software development requirement based on a plurality of causal relationship links to judge whether the software development requirement is reasonable. The problem domain oriented requirement change analysis method can help products to better analyze requirements, and provides a method for checking whether the association of each domain is correct or not and whether the relationship chain of the problem domain is complete or not through the causal relationship, wherein the newly added requirements are directly added into the problem diagram to regenerate a new relationship diagram according to the causal relationship, so that whether the relationship chain of the current requirements is reasonable or not can be clearly seen. Therefore, whether the requirement is reasonable or not and the field involving change can be judged, and the treatment scheme can be rapidly made by rapidly responding when the requirement is changed.
It should be noted that the modules referred to in the present invention refer to a series of computer program instruction segments capable of performing specific functions, and are more suitable for describing the execution process of metadata completeness detection than a program.
In some embodiments, the requirement splitting module 11 is specifically configured to:
the method comprises the steps of obtaining software development requirements, and generating a plurality of problem domains representing sub-requirements based on the software development requirements, wherein shared phenomena and causal relationships among the shared phenomena exist among the problem domains.
In some embodiments, the problem map creation module is specifically configured to:
modeling the software development requirement based on each sub-requirement to obtain an initial problem map;
and expanding the initial problem map based on the initial problem map and the sharing phenomena and the causal relationship among the sharing phenomena among the problem domains corresponding to the sub-demands, so as to add a causal relationship attribute to the initial problem map and obtain the problem map.
In some embodiments, the problem map is plotted by UML.
In some embodiments, the causal link establishing module 13 is specifically configured to:
generating a plurality of causal links based on the causal relationships in the problem map, including:
converting the problem graph into a script, wherein the script has path information representing a causal relationship;
and analyzing the script, and generating a plurality of causal relationship links based on the path information in the script.
In some embodiments, the analysis module 14 is specifically configured to:
and judging whether the causal relationship links have redundant processes or not based on the plurality of causal relationship links, if so, judging whether the software development requirement is reasonable, otherwise, judging that the software development requirement is unreasonable.
In some embodiments, the requirement analysis device further comprises a prompt module for sending out a prompt message of requirement error when the software development requirement is unreasonable.
Another embodiment of the present invention provides an electronic device, as shown in fig. 7, an electronic device 10 includes:
one or more processors 110 and a memory 120, where one processor 110 is illustrated in fig. 7, the processor 110 and the memory 120 may be connected by a bus or other means, and where fig. 6 illustrates a bus connection.
The processor 110 is used to implement various control logic for the electronic device 10, which may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a single chip microcomputer, an ARM (Acorn RISC Machine) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of these components. Also, the processor 110 may be any conventional processor, microprocessor, or state machine. Processor 110 may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP, and/or any other such configuration.
The memory 120 is a non-volatile computer-readable storage medium, and can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as program instructions corresponding to the demand analysis method in the embodiment of the present invention. The processor 110 executes various functional applications and data processing of the electronic device 10, i.e. implements the demand analysis method in the above-described method embodiments, by running the non-volatile software programs, instructions and units stored in the memory 120.
The memory 120 may include a storage program area and a storage data area, wherein the storage program area may store an application program required for operating the platform, at least one function; the stored data area may store data created from use of the electronic device 10, and the like. Further, the memory 120 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, the memory 120 optionally includes memory located remotely from the processor 110, which may be connected to the electronic device 10 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
One or more units are stored in the memory 120, which when executed by the one or more processors 110, perform the demand analysis method in any of the method embodiments described above, e.g., performing the method steps S100-S400 in fig. 1 described above.
Another embodiment of the present invention provides a computer-readable storage medium storing computer-executable instructions for execution by one or more processors, for example, to perform method steps S100-S400 of fig. 1 described above.
By way of example, computer-readable storage media can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as Synchronous RAM (SRAM), dynamic RAM, (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The disclosed memory components or memory of the operating environment described herein are intended to comprise one or more of these and/or any other suitable types of memory.
In summary, according to the demand analysis method, the demand analysis device, the electronic device and the storage medium provided by the invention, firstly, a software development demand is obtained, and the software development demand is split to obtain a plurality of sub-demands; then establishing a problem map based on a plurality of the sub-requirements; then generating a plurality of causal relationship links based on the causal relationship in the problem map; and finally, analyzing the software development requirement based on a plurality of causal relationship links to judge whether the software development requirement is reasonable. The problem domain oriented requirement change analysis method can help a product to better analyze the requirements, and provides the method for checking whether the association of each domain is correct or not and whether the relationship chain of the problem domain is complete or not through the causal relationship, wherein the newly added requirements are directly added into the problem diagram to regenerate a new relationship diagram according to the causal relationship, so that whether the relationship chain of the current requirements is reasonable or not can be clearly seen. Therefore, whether the requirement is reasonable or not and the field involving change can be judged, and the treatment scheme can be rapidly made by rapidly responding when the requirement is changed.
The above-described embodiments of the present invention should not be construed as limiting the scope of the present invention. Any other corresponding changes and modifications made according to the technical idea of the present invention should be included in the protection scope of the claims of the present invention.
Claims (10)
1. A method for demand analysis, comprising the steps of:
acquiring a software development requirement, and splitting the software development requirement to obtain a plurality of sub-requirements;
establishing a problem map based on a plurality of the sub-requirements;
generating a plurality of causal relationship links based on the causal relationship in the problem map;
and analyzing the software development requirement based on a plurality of causal relationship links to judge whether the software development requirement is reasonable.
2. The demand analysis method according to claim 1, wherein the obtaining a software development demand, and splitting the software development demand to obtain a plurality of sub-demands comprises:
the method comprises the steps of obtaining software development requirements, and generating a plurality of problem domains representing sub-requirements based on the software development requirements, wherein the problem domains have sharing phenomena and causal relationships among the sharing phenomena.
3. The demand analysis method of claim 2, wherein the building a problem map based on the plurality of sub-demands comprises:
modeling the software development requirement based on each sub-requirement to obtain an initial problem map;
and expanding the initial problem map based on the initial problem map and the sharing phenomena and the causal relationship among the sharing phenomena among the problem domains corresponding to the sub-demands, so as to add a causal relationship attribute to the initial problem map and obtain the problem map.
4. The demand analysis method of claim 3, wherein the problem map is plotted by UML.
5. The demand analysis method of claim 4, wherein generating a number of causal links based on the causal relationships in the problem map comprises:
converting the problem graph into a script, wherein the script has path information representing a causal relationship;
and analyzing the script, and generating a plurality of causal links based on the path information in the script.
6. The demand analysis method of claim 5, wherein the analyzing the software development demand based on a number of the causal links to determine whether the software development demand is reasonable comprises:
and judging whether the causal relationship links have redundant processes or not based on the plurality of causal relationship links, if so, judging whether the software development requirement is reasonable, otherwise, judging that the software development requirement is unreasonable.
7. The demand analysis method of claim 6, further comprising:
and when the software development requirement is unreasonable, sending out prompt information of requirement error.
8. A demand analysis apparatus, comprising:
the requirement splitting module is used for acquiring a software development requirement and splitting the software development requirement to obtain a plurality of sub-requirements;
the problem map building module is used for building a problem map based on the plurality of sub-requirements;
the causal relationship link establishing module is used for generating a plurality of causal relationship links based on the causal relationship in the problem map;
and the analysis module is used for analyzing the software development requirement based on the causal relationship links so as to judge whether the software development requirement is reasonable.
9. An electronic device, comprising: a processor and a memory;
the memory having stored thereon a computer program executable by the processor;
the processor, when executing the computer program, implements the steps in the demand analysis method according to any of claims 1-7.
10. A computer-readable storage medium, comprising: a processor and a memory;
the memory having stored thereon a computer program executable by the processor;
the processor, when executing the computer program, implements the steps in the demand analysis method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211460728.3A CN115934040A (en) | 2022-11-17 | 2022-11-17 | Demand analysis method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211460728.3A CN115934040A (en) | 2022-11-17 | 2022-11-17 | Demand analysis method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115934040A true CN115934040A (en) | 2023-04-07 |
Family
ID=86649915
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211460728.3A Pending CN115934040A (en) | 2022-11-17 | 2022-11-17 | Demand analysis method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115934040A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116795330A (en) * | 2023-08-25 | 2023-09-22 | 深圳市兴意腾科技电子有限公司 | Method and system for developing storage software of compiling computer based on software development kit |
-
2022
- 2022-11-17 CN CN202211460728.3A patent/CN115934040A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116795330A (en) * | 2023-08-25 | 2023-09-22 | 深圳市兴意腾科技电子有限公司 | Method and system for developing storage software of compiling computer based on software development kit |
| CN116795330B (en) * | 2023-08-25 | 2023-11-24 | 深圳市兴意腾科技电子有限公司 | Method and system for developing storage software of compiling computer based on software development kit |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3279816A1 (en) | Data analysis processing method, apparatus, computer device, and storage medium | |
| CN113343312B (en) | Page tamper-proof method and system based on front-end embedded point technology | |
| CN111435367B (en) | Knowledge graph construction method, system, equipment and storage medium | |
| CN113138757B (en) | Front-end code automatic generation method, device, server, system and medium | |
| CN112948275A (en) | Test data generation method, device, equipment and storage medium | |
| US20210406004A1 (en) | System and method for implementing a code audit tool | |
| CN117289904A (en) | Artificial intelligence model construction method, system, equipment and storage medium | |
| CN115934040A (en) | Demand analysis method and device, electronic equipment and storage medium | |
| CN116186755A (en) | Privacy calculating method, device, terminal equipment and storage medium | |
| US10025697B2 (en) | Generation of automated unit tests for a controller layer system and method | |
| CN110309062B (en) | Use case generation method, device, electronic equipment and storage medium | |
| CN107092671B (en) | Method and equipment for managing meta information | |
| CN110908644A (en) | Configuration method and device of state node, computer equipment and storage medium | |
| CN114706787A (en) | Service test method, service test device, equipment and storage medium | |
| CN115562662A (en) | Application page creating method and device, computer equipment and storage medium | |
| CN112947984B (en) | Application program development method and device | |
| CN115437940A (en) | API (application programming interface) testing method suitable for financial cloud platform | |
| CN114610309A (en) | Object configuration method, device, equipment and storage medium | |
| CN113419738A (en) | Interface document generation method and device and interface management equipment | |
| US20200371900A1 (en) | System for intelligent restructuring of automation test beds | |
| US11960560B1 (en) | Methods for analyzing recurring accessibility issues with dynamic web site behavior and devices thereof | |
| CN115639988A (en) | Persistent integration method, persistent integration platform and computer-readable storage medium | |
| CN118690369A (en) | Code scanning method, device, equipment and medium | |
| US10853888B2 (en) | Computing validation and error discovery in computers executing a multi-level tax data validation engine | |
| CN117608992A (en) | Method, device, computer equipment and storage medium for tracking log information |
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 |