CN116862260A - Method and device for determining implementation level of software project, electronic equipment and medium - Google Patents
Method and device for determining implementation level of software project, electronic equipment and medium Download PDFInfo
- Publication number
- CN116862260A CN116862260A CN202310843012.XA CN202310843012A CN116862260A CN 116862260 A CN116862260 A CN 116862260A CN 202310843012 A CN202310843012 A CN 202310843012A CN 116862260 A CN116862260 A CN 116862260A
- Authority
- CN
- China
- Prior art keywords
- risk
- software
- determining
- index
- target
- 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
- 238000000034 method Methods 0.000 title claims abstract description 51
- 230000003993 interaction Effects 0.000 claims abstract description 60
- 238000011161 development Methods 0.000 claims abstract description 44
- 238000010276 construction Methods 0.000 claims abstract description 27
- 238000011156 evaluation Methods 0.000 claims description 55
- 239000011159 matrix material Substances 0.000 claims description 25
- 230000002452 interceptive effect Effects 0.000 claims description 13
- 238000004519 manufacturing process Methods 0.000 claims description 11
- 238000010586 diagram Methods 0.000 claims description 10
- 238000003860 storage Methods 0.000 claims description 9
- 238000004364 calculation method Methods 0.000 claims description 7
- 238000004590 computer program Methods 0.000 claims description 4
- 230000006870 function Effects 0.000 description 16
- 230000005540 biological transmission Effects 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 238000012552 review Methods 0.000 description 8
- 238000012502 risk assessment Methods 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 7
- 238000004458 analytical method Methods 0.000 description 5
- 230000008901 benefit Effects 0.000 description 5
- 238000006243 chemical reaction Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000009826 distribution Methods 0.000 description 3
- 239000000463 material Substances 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000013139 quantization Methods 0.000 description 3
- 238000011160 research Methods 0.000 description 3
- 230000007613 environmental effect Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 101100070120 Xenopus laevis has-rs gene Proteins 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000001364 causal effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000007704 transition Effects 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
- G06Q10/063—Operations research, analysis or management
- G06Q10/0637—Strategic management or analysis, e.g. setting a goal or target of an organisation; Planning actions based on goals; Analysis or evaluation of effectiveness of goals
-
- 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
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Educational Administration (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Development Economics (AREA)
- Game Theory and Decision Science (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)
- Stored Programmes (AREA)
Abstract
The application provides a method, a device, electronic equipment and a medium for determining implementation level of a software project, wherein the method comprises the following steps: determining a data interaction relationship between the target software item and the existing software item based on the input data and the output data of the target software item; constructing a software influence network reflecting the data interaction relationship, and determining the values of a plurality of software influence network parameters of the software influence network; determining importance of a target software item based on the values of the network parameters affected by the plurality of software; determining the predicted construction period, development cost and risk value under different risk classifications of the target software project; and determining the implementation level of the target software project by using the importance degree, the risk values under different risk classifications, the predicted construction period and the development cost. By adopting the method, the device, the electronic equipment and the medium for determining the implementation level of the software item, the problem that whether the software item can be implemented or not can not be accurately and comprehensively determined is solved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, an electronic device, and a medium for determining a software project implementation level.
Background
Before project establishment, software suppliers conduct scientific prediction and evaluation on potential influences, risks and costs in the project establishment process by comprehensively researching conditions and conditions of markets, resources, technologies, economy, society and the like related to the project according to actual demands of demand parties, examine the technical advancement, applicability, economic rationality, financial profitability and feasibility of construction of the project, and further determine whether to implement the project. In general, from the perspective of project population, the system has to conduct intensive research on aspects of economy, technology, finance, law, environmental protection and the like related to the project, and provides accurate basis for scientific investment decision.
In the prior art, when determining whether an item of software can be implemented, it is generally considered only from the aspect of the risk dimension or implementation cost dimension of implementing the item of software, resulting in a problem that whether the item of software can be implemented cannot be accurately and comprehensively determined.
Disclosure of Invention
In view of the above, the present application aims to provide a method, an apparatus, an electronic device and a medium for determining a software item implementation level, so as to solve the problem that whether the software item can be implemented cannot be accurately and comprehensively determined.
In a first aspect, an embodiment of the present application provides a method for determining an implementation level of a software item, including:
determining a data interaction relationship between the target software item and the existing software item based on the input data and the output data of the target software item;
constructing a software influence network reflecting the data interaction relationship, and determining the values of a plurality of software influence network parameters of the software influence network, wherein the plurality of software influence network parameters comprise the importance weight of the interaction relationship, the output degree and the input degree of the software item;
determining importance of the target software item based on the values of the network parameters affected by the plurality of software, wherein the importance is used for representing the importance of the target software item to the whole production process of the enterprise;
determining the predicted construction period, development cost and risk value under different risk classifications of the target software project;
and determining the implementation level of the target software project by using the importance degree, the risk values under different risk classifications, the predicted construction period and the development cost.
Optionally, determining the importance of the target software item based on the values of the plurality of software-affecting network parameters includes: determining the sum of the outgoing degree and the incoming degree of the target software item as the degree of the target software item; calculating the sum of the importance weights of the interaction relations corresponding to all sides associated with the target software item in the network, and determining the sum as the centrality of the target software item; and determining the ratio of the centrality to the degree as the importance of the target software item.
Optionally, the existing software project comprises a plurality; constructing a software influence network reflecting data interaction relationships, comprising: determining a data interface corresponding to each of the target software item and the plurality of existing software items; selecting interfaces with data interaction relation with a plurality of existing software items from data interfaces corresponding to the target software items as first data interfaces; selecting an interface with a data interaction relation with the target software item from data interfaces corresponding to a plurality of existing software items as a second data interface; respectively taking a first data interface of a target software item and a second data interface of an existing software item as nodes of a software influence network; according to the data input-output relation between the target software project and each existing software project, different nodes are connected through arrows with indicating the data interaction direction, and the software influence network is generated.
Optionally, determining the implementation level of the target software project using the importance level, the risk values under different risk classifications, the estimated time period, and the development cost includes: determining implementation indexes of a target software project, wherein the implementation indexes comprise a first-layer implementation index and a second-layer implementation index, the first-layer implementation index comprises an economic index, a technical index and a social index, the second-layer implementation index corresponding to the economic index comprises an importance degree, a time cost and an economic cost, and the second-layer implementation index corresponding to the technical index comprises an implementation risk; determining a judgment set corresponding to the importance degree index, the time cost index and the economic cost index respectively based on the importance degree, the estimated construction period and the development cost; determining a judgment set corresponding to the implementation risk index based on the risk value; and determining the implementation level of the target software project based on the judgment set corresponding to the importance degree index, the time cost index and the economic cost index and the judgment set corresponding to the implementation risk index.
Optionally, determining the implementation level of the target software item based on the evaluation set corresponding to the importance level index, the time cost index and the economic cost index and the evaluation set corresponding to the implementation risk index respectively includes: determining the value of a judgment matrix corresponding to each first-layer implementation index based on a judgment set corresponding to the importance degree index, the time cost index and the economic cost index and a judgment set corresponding to the implementation risk index respectively; determining a weight vector matrix corresponding to the first layer implementation index and the second layer implementation index; based on the weight vector matrix and the evaluation matrix, evaluating the second implementation index and the first layer implementation index of the target software item in sequence to obtain a comprehensive evaluation result; and taking the grade corresponding to the evaluation result with the largest numerical value in the comprehensive evaluation results as the implementation grade of the target software project.
Optionally, determining the predicted time period, development cost, and risk value under different risk classifications for the target software project includes: measuring the workload and development cost of a target software project by adopting a function point evaluation method, and determining the estimated construction period and development cost of the target software project; and determining risk values of the target software project under different risk classifications.
Optionally, determining the risk value under different risk classifications of the target software item includes: constructing a risk expression weight table for representing different risk levels under the initial risk classification; determining the weight value of a target software item under the initial risk classification, and generating a risk identification situation table and a risk source identification situation table; combining the risk identification situation table and the risk source identification situation table to generate a target risk and a target risk source list; constructing a risk probability Bayesian network based on the target risk and the target risk source list; and calculating to obtain risk values of the target software project under different risk classifications by using a risk probability Bayesian network.
In a second aspect, an embodiment of the present application further provides a device for determining a software project implementation level, where the device includes:
the interactive relation determining module is used for determining a first data interface corresponding to the target software item and a data interactive relation between the target software item and the existing software item based on input data and output data of the target software item;
the network diagram construction module is used for constructing a software influence network reflecting the data interaction relationship, determining the values of a plurality of software influence network parameters of the software influence network, wherein the plurality of software influence network parameters comprise the interaction relationship importance weight, the output degree and the input degree of the software item;
The importance calculating module is used for determining the importance of the target software item based on the values of the network parameters influenced by a plurality of pieces of software, and the importance is used for representing the importance of the target software item to the whole production process of an enterprise;
the risk cost calculation module is used for determining the estimated construction period, development cost and risk value under different risk classifications of the target software project;
and the implementation level determining module is used for determining the implementation level of the target software project by utilizing the importance degree, the risk values under different risk classifications, the predicted construction period and the development cost.
In a third aspect, an embodiment of the present application further provides an electronic device, including: a processor, a memory and a bus, said memory storing machine readable instructions executable by said processor, said processor and said memory communicating via the bus when the electronic device is running, said machine readable instructions when executed by said processor performing the steps of the software item implementation level determination method as described above.
In a fourth aspect, embodiments of the present application also provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of a method for performing a grade determination for an item of software as described above.
The embodiment of the application has the following beneficial effects:
according to the method, the device, the electronic equipment and the medium for determining the implementation level of the software project, a software influence network can be constructed according to the data interaction relation between the target software project and the existing software project, the importance degree parameters representing the importance degree of the target software project to the whole production process of an enterprise are determined through the calculated multiple software influence network parameters, and then the implementation level of the target software project is determined through the importance degree, implementation risk, development period and multiple dimensions of the development cost of the target software project to the enterprise, so that whether the target software project needs to be implemented or not can be determined more accurately and comprehensively.
In order to make the above objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 shows a flow chart of a method for determining the implementation level of a software item provided by an embodiment of the application;
FIG. 2 is a schematic diagram of a software-implemented network according to an embodiment of the present application;
FIG. 3 illustrates a risk probability Bayesian network provided by an embodiment of the present application;
FIG. 4 illustrates a hierarchical structure of a risk probability Bayesian network provided by an embodiment of the present application;
FIG. 5 is a schematic diagram showing the structure of a software project implementation level determining apparatus according to an embodiment of the present application;
fig. 6 shows a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the application, as presented in the figures, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. Based on the embodiments of the present application, every other embodiment obtained by a person skilled in the art without making any inventive effort falls within the scope of protection of the present application.
It is noted that, before the present application is put forward, before project stand implementation, software suppliers carry out scientific prediction and evaluation on potential influence, risk and cost in project implementation process by carrying out comprehensive investigation and research on conditions and conditions of market, resource, technology, economy, society and the like related to the project according to actual demands of the demander, examine the technical advancement, applicability, economic rationality, financial profitability and construction feasibility of the project, and further determine whether to implement the project. In general, from the perspective of project population, the system has to conduct intensive research on aspects of economy, technology, finance, law, environmental protection and the like related to the project, and provides accurate basis for scientific investment decision. In the prior art, the problem of whether the software item needs to be implemented is not considered, and meanwhile, when determining whether the software item is implemented, the problem that whether the software item can be implemented cannot be accurately and comprehensively determined is caused only by considering the risk dimension or the implementation cost dimension of the implemented software item.
Based on this, the embodiment of the application provides a method for determining the implementation level of a software item, so as to improve the accuracy and the comprehensiveness in determining whether the software item can be implemented.
Referring to fig. 1, fig. 1 is a flowchart of a method for determining a level of implementation of a software item according to an embodiment of the present application. As shown in fig. 1, the method for determining the implementation level of a software item provided by the embodiment of the application includes:
step S101, determining a data interaction relationship between the target software item and the existing software item based on the input data and the output data of the target software item.
In this step, the target item of software may refer to an item of software for which an implementation level is to be determined.
The input data may refer to data input to a target software item, and the output data may refer to data output by the target software item.
The input data may be an imported excel document, an excel format, or input data in an input box if the input data is an interactive software item, or interactive data generated by clicking a button with a mouse.
The export data may be, for example, derived excel documents, or data sent to other software items.
The data interaction relationship may refer to a data transmission relationship between different software items, the data interaction relationship including: interactive objects, interactive data content, data transmission direction, interactive logic and control relation.
The logical and control relationship may refer to an interaction flow between different items of software.
By way of example, the interaction object may be a data interface a of item of software a and a data interface B of item of software B.
The interactive data content may be, for example, gender, age, or specific business data.
For example, the interactive procedure may be that the software item a transmits the link data to the software item B, and the software item B receives the link data and opens a web page address corresponding to the link data in response to a clicking operation of the user.
The data transmission direction may be, for example, the transmission from the data interface a of the software item a to the data interface B of the software item B.
In the embodiment of the application, before the target software project is developed, the importance degree, namely the importance degree, of the target software project for the whole production process of the enterprise is firstly determined. Depending on the importance, it can be determined not only whether the target software item is necessary to be implemented, but also whether it can be implemented.
For this purpose, firstly, a data interaction relation between a target software item and an existing software item is determined, before the data interaction relation is determined, a workflow analysis method is adopted to determine a module included in the target software item and a function of each module, and input data, output data and a conversion relation between the input data and the output data of the module are determined for each module. An enterprise refers to an enterprise that needs to develop a target software project, and the enterprise not only develops the target software project, but also develops a plurality of existing software projects, and the target software project cooperates with the existing software projects to complete the whole production process of the enterprise.
Taking an order module in a target software project as an example, the main functions of the order module are to create an order, edit the order and view the order, and input data and output data corresponding to the order module can be determined. In this way, the conversion relationships between all input data and output data of the target software project can be determined.
Meanwhile, input data and output data of the existing software project of the enterprise are determined, and the data interaction relationship between the target software project and the existing software project can be determined according to the interaction object, the interaction data content, the data transmission direction and the interaction logic and control relationship of the data transmission between the target software project and the existing software project.
For example: the input data a of the target software item a is the output data B of the existing software item B, and the input data c of the existing software item B is the output data d of the target software item a, so that the data interaction relationship between the different software items can be determined.
Step S102, a software influence network reflecting the data interaction relationship is constructed, and the values of a plurality of software influence network parameters of the software influence network are determined.
In this step, the software-affected network may be a data-interactive relationship network, which is a network designed to calculate importance, which is a directed weighted graph.
The software-affected network is denoted SIN (Software Influence Network), then the software-affected network can be described as: sin= (V, E), where V represents a set of nodes, and each node in V represents an external data interface of a target software item, or a data interface having a data interaction relationship with the target software item in an external data interface of an existing software item; e is a set of edges (E epsilon V x V), each element e= < a, b, w > in E is an ordered pair, E represents a data interaction relationship, w represents an interaction relationship importance weight, the value range of w is w epsilon [0,1], and a and b represent two nodes on the edge corresponding to E.
The plurality of software-affected network parameters are used to describe the software-affected network, the plurality of software-affected network parameters including an interaction relationship importance weight, an egress degree of the software item, and an ingress degree.
The output degree of the software item may refer to the sum of the output degrees of all network nodes of the target software item, and is used for reflecting the interaction data quantity required to be output by the target software item, and is recorded as: NSP (non-stop phase) out 。
The incomings of the software items can refer to the sum of incomings of all network nodes of the target software items, and are used for reflecting the interaction data quantity required to be input by the target software items and are recorded as: NSP (non-stop phase) in 。
The interaction relation importance weight is used for representing the influence degree of different edges in the software influence network, and the larger the interaction relation importance weight value is, the higher the influence degree is, the smaller the interaction relation importance weight value is, and the lower the influence degree is.
Wherein the degree of entry may refer to the number of arrows directed to the node for the target item of software and the degree of exit may refer to the number of arrows directed from the target item of software to the other nodes.
In an alternative embodiment, the existing software items include a plurality of; constructing a software influence network reflecting data interaction relationships, comprising: determining a data interface corresponding to each of the target software item and the plurality of existing software items; selecting interfaces with data interaction relation with a plurality of existing software items from data interfaces corresponding to the target software items as first data interfaces; selecting an interface with a data interaction relation with the target software item from data interfaces corresponding to a plurality of existing software items as a second data interface; respectively taking a first data interface of a target software item and a second data interface of an existing software item as nodes of a software influence network; according to the data input-output relation between the target software project and each existing software project, different nodes are connected through arrows with indicating the data interaction direction, and the software influence network is generated.
Specifically, the data interface of the target software item is obtained by using the input data, the output data and the conversion relation between the input data and the output data of the target software item, and the data interface of the existing software item is obtained by using the input data, the output data and the conversion relation between the input data and the output data of the existing software item. The data interfaces may be divided into an input data interface and an output data interface, where a single data interface is fixed in data format when transmitting data, for example: data transmission is performed in xlsx, json or xml format.
The construction of a software-affected network is described below with reference to fig. 2.
Fig. 2 is a schematic diagram of a software impact network according to an embodiment of the present application.
As shown in fig. 2, each data interface is abstracted to a network node, and the software-affected network includes node V 1 Node V 2 Node V 3 Node V 4 Node V 5 Node V 6 Node V 7 Wherein the target software item 210 corresponds to node V 1 Node V 2 Node V 3 Existing software item 220 corresponds to node V 4 Existing software item 230 corresponds to node V 5 Existing software project 240 corresponds to node V 6 Existing software item 250 corresponds to node V 7 。
Due to the data slave node V 1 Transmitted to node V 4 So node V 1 And node V 4 The connecting line between the two is provided with a V 1 Pointing to V 4 And similarly, the arrows indicating the direction of data transmission are also provided between other nodes.
Wherein, the node port V 1 Node V 2 Node V 3 The corresponding data interface is a first data interface; node V 4 Node V 5 Node V 6 Node V 7 The corresponding data interface is a second data interface; w (W) 1, ，W 1, ，W 6, W is provided 7,3 The interaction relation importance weights corresponding to different sides are adopted.
Here, the target software item or the existing software item may also comprise other data interfaces, which however do not interact with the existing software item or with the target software item, so that the nodes corresponding to these data interfaces are not present in the software-influencing network.
In fig. 2, the number of arrows pointing to the target software item 210 is 2, so the incoming degree is 2, and the number of arrows pointing from the target software item 210 to the existing software item is 2, so the outgoing degree is 2.
When calculating the importance weight of the interaction relation of each side in the network, the importance weight can be determined by a set importance weight table. The importance degree weight table divides the importance degree into a plurality of importance levels, each level corresponds to a quantization interval, and the quantization interval is the value range of the importance degree weight of the interaction relationship. For each side in the software influence network, determining an importance level according to the data interaction relation corresponding to the side, and selecting a proper value from the quantization interval corresponding to the importance level according to experience to serve as the interaction relation importance weight corresponding to the side. Wherein, the importance weight table can be seen in the following table 1.
Table 1: importance weight table.
Step S103, determining the importance of the target software item based on the values of the network parameters influenced by a plurality of software.
In this step, the importance level is used to characterize the importance level of the target software item for the whole production process of the enterprise.
In an alternative embodiment, determining the importance of the target software item based on the values of the plurality of software-affecting network parameters includes: determining the sum of the outgoing degree and the incoming degree of the target software item as the degree of the target software item; calculating the sum of the importance weights of the interaction relations corresponding to all sides associated with the target software item in the network, and determining the sum as the centrality of the target software item; and determining the ratio of the centrality to the degree as the importance of the target software item.
Specifically, the degree may refer to the sum of the outbound degree and inbound degree of all network nodes (interfaces to be developed) of the target software project, and is recorded as NSP degree It reflects the total interactive data volume of the target software project, NSP degree ＝NSP out +NSP in 。
Centrality may refer to the sum of the weights of the edges associated with all network nodes (interfaces to be developed) of a target item of software, denoted NSP C It reflects the total of the target software itemsThe importance of the amount of interactive data.
Importance may refer to the importance of a target item of software in all software systems of an enterprise, denoted NSP I ＝NSP C /NSP degree ，NSP I ∈[0,1]It reflects the importance of all input and output data of the target software project to the whole production process of the enterprise.
Taking fig. 2 as an example, NSP degree 4, NSP C ＝W 1, +W 1, +W 6, +W 7, Thus, NSP is available I ＝(W 1,4 +W 1, +W 6, +W 7, )/4。
Step S104, determining the predicted construction period, development cost and risk value under different risk classifications of the target software project.
In this step, the estimated time period may refer to the time it takes to complete the development of the target software project.
Development costs may refer to the funds spent completing the development of the target software project.
The risk value may refer to the risk that is required to complete the development of the target software project.
In an alternative embodiment, determining the predicted time period, development costs, and risk values for the target software project under different risk classifications includes: measuring the workload and development cost of a target software project by adopting a function point evaluation method, and determining the estimated construction period and development cost of the target software project; and determining risk values of the target software project under different risk classifications.
Specifically, the function points reflect the number of functions of the target software item, and the function points include two major categories of data function points and transaction function points, and since the scale, workload and cost of the software item are determined by the function point evaluation method, which belong to the prior art, the description is omitted here.
In addition, in addition to determining the predicted construction period and development cost of the target software project, the capability of the target software project to resist different risks needs to be determined, namely, the higher the risk value is, the greater the implementation risk under the risk classification is, and the lower the risk value is, the smaller the implementation risk under the risk classification is.
In an alternative embodiment, determining risk values for the target software item under different risk classifications includes: constructing a risk expression weight table for representing different risk levels under the initial risk classification; determining the weight value of a target software item under the initial risk classification, and generating a risk identification situation table and a risk source identification situation table; combining the risk identification situation table and the risk source identification situation table to generate a target risk and a target risk source list; constructing a risk probability Bayesian network based on the target risk and the target risk source list; and calculating to obtain risk values of the target software project under different risk classifications by using a risk probability Bayesian network.
Specifically, before the target software project stands, the possible risks of the target software project in the implementation process are identified, the possibility of the occurrence of the required risks is analyzed and quantitatively calculated, and on the basis, risk processing suggestions are given to form a risk evaluation report. It mainly includes three stages of risk identification, risk analysis and risk assessment. Among the risks that may occur during implementation include, but are not limited to: demand risk, product scale risk, correlation risk, technical risk, and management risk.
When risk identification is performed, a table look-up mode is adopted to perform risk identification, for this purpose, firstly, a software risk classification table needs to be established, the risk of the target software item is divided into multiple risks, each risk is divided into 5 risk levels, and corresponding risk expression weights are set for each risk level, for example: the risk performance weight of the high risk is 0.9, the risk performance weight of the higher risk is 0.7, the risk performance weight of the general risk is 0.5, the risk performance weight of the lower risk is 0.3, and the risk performance weight of the low risk is 0.1.
Risk classification includes, but is not limited to: functional risk R1, performance risk R2, reliability risk R3, security risk R4, resource risk R5, cost risk R6, maintenance risk R7, analysis method risk R8, software multiplexing risk R9, logic model risk R10, review agency risk R11, system review risk R12, document data review risk R13, product scale risk R14, correlation risk R15, technical risk 16, and management risk 17.
In addition, each risk classification corresponds to different judging standards under different risk expression levels, taking cost risk as an example, the standard of a high risk level is "lack of a great deal of project development experience," the cost and the control progress cannot be estimated, "the standard of a higher risk level is" a certain development experience, "the cost and the control progress cannot be well estimated," the standard of a general risk level is "a considerable development experience," the cost and the control progress can be well estimated, "the standard of a lower risk level is" a great deal of project development experience, "the cost and the control progress can be effectively estimated," the standard of a low risk level is "a great deal of project development experience," and the cost and the control progress can be efficiently estimated.
After determining the software risk classification table, combining comprehensive discussion of project members and expert groups, risk identification can be rapidly completed according to experience to form a risk identification situation table and a risk source identification situation table, wherein the risk identification situation table is shown in table 2, and the risk source identification situation table is shown in table 3.
Table 2: risk identification case table.
| Risk numbering | Risk name | Risk identification situation | Weight value |
| R1 | Risk of function | In general | 0.5 |
| R2 | Performance risk | High height | 0.9 |
| R3 | Reliability risk | Higher height | 0.7 |
| R4 | Security risk | In general | 0.5 |
| R5 | Resource risk | Higher height | 0.7 |
| R6 | Cost risk | In general | 0.5 |
| R7 | Maintenance risk | Lower level | 0.3 |
| R8 | Analysis method risk | Low and low | 0.1 |
| R9 | Software reuse risk | Low and low | 0.1 |
| RA | Logic model risk | Lower level | 0.3 |
| RB | Review agency risk | Lower level | 0.3 |
| RC | System review risk | Lower level | 0.3 |
| RD | Document material review risk | Higher height | 0.7 |
Table 3: the risk source identifies a situation table.
After the risk identification situation table and the risk source identification situation table are determined, the identified risks and the risk sources are integrated into a target risk and target risk source list through operations such as merging similarity, deleting repetition, adding omission and the like, and the target risk and target risk source list is shown in table 4.
Table 4: and the target risk source list.
| Numbering device | Risk name | Numbering device | Risk source |
| R1 | Risk of function | RS1 | Variation of system functions |
| R2 | Performance risk | RS2 | User demand expression ambiguity |
| R3 | Reliability risk | RS3 | Incomplete technology |
| R4 | Security risk | RS4 | Instability of personnel |
| R5 | Resource risk | RS5 | Insufficient resources |
| R6 | Cost risk | RS6 | Server instability |
| RD | Document material review risk | RS7 | Inexperience of experience |
| RS8 | Imperfect project management |
And after the target risk and the target risk source list are formed, risk analysis is carried out.
During risk analysis, a Bayesian network is constructed according to the target risk and the target risk source list identified in the risk identification process, and then the occurrence probability of the software risk is inferred by utilizing an uncertain reasoning algorithm specific to the Bayesian network, wherein the method mainly comprises three stages of establishing a risk Bayesian network topological structure, constructing a risk probability Bayesian network and reasoning of the Bayesian network.
The risk analysis stage aims at acquiring probability information on a topological structure, wherein the probability information comprises prior probability information of an initial software risk and conditional transition probability information of the software risk to a next software risk. When the risk probability Bayesian network is constructed, nodes in the network correspond to software risks identified in the risk identification stage, and edges in the network correspond to causal relations or transfer relations of the risks.
According to the software risk identified in table 4, the risk and the risk source are extracted as initial nodes for constructing the bayesian network, and the node variables considered here take only 2 values: 1 and 0 (1 represents occurrence, 0 represents non-occurrence). On this basis, a risk probability Bayesian network as shown in FIG. 3 is constructed.
Fig. 3 illustrates a risk probability bayesian network provided by an embodiment of the present application.
As shown in fig. 3, each risk and each risk source are one node of the risk probability bayesian network, and then, according to the corresponding relationship between different risks and risk sources, each risk in the risk set 320 and the corresponding risk source in the risk source set 310 are connected through an arrow with an indication direction, so as to form the risk probability bayesian network.
After the risk probability Bayesian network is determined, the probability of occurrence of a risk source corresponding to each node and the conditional probability of occurrence of the risk are obtained through comprehensive analysis of the expert and the item group, a conditional probability distribution table is formed, and the occurrence probability of the software risk is determined based on the conditional probability distribution table. Because the process of acquiring the conditional probability distribution table according to the risk probability bayesian network and the process of determining the occurrence probability of the software risk belong to the prior art, the description is omitted here.
The risk assessment is to sort risks according to a risk probability Bayesian network constructed in the risk analysis stage, evaluate the risks by adopting a hierarchical analysis method, give a risk processing suggestion, and generate an assessment report, and mainly comprises four stages of constructing a judgment matrix of each risk node of a risk layer and a target layer, constructing the judgment matrix for factor layer elements corresponding to each risk node, calculating weights of each risk source corresponding to each software risk, and calculating the risk value of each software risk.
In the risk assessment stage, an analytic hierarchy process is first adopted to assess risk effects. Wind resistance using analytic hierarchy processThe risk impact is evaluated and the Bayesian network needs to be converted into a hierarchical structure diagram. The specific method comprises the following steps: in the Bayesian network shown in FIG. 3, for each risk source corresponding to each risk, the risk source is converted into a one-to-many specific structure, such as R 1 The risk source corresponding to the risk has RS 1 、RS 2 、RS 7 In the hierarchical structure, RS 1 、RS 2 、RS 7 These 3 nodes will become R 1 Is a child node of (a).
Fig. 4 shows a hierarchical structure of a risk probability bayesian network provided by an embodiment of the present application.
As shown in fig. 4, the top layer is set as a T layer, i.e., a reliability total target, and the middle layer R is set as each risk node (R 1 ,R 2 …, RD), the risk source nodes constitute the lowest F layer. And then, constructing a first judgment matrix of each risk node of the risk layer R and the target layer T.
After the first judgment matrix is constructed, a second judgment matrix corresponding to each node in the R layer is constructed for the F layer node corresponding to the node. The weight of each risk source corresponding to each software risk can be calculated through calculating the second judgment matrix, so as to obtain the importance of each risk source for the risk, for example: for risk node R 1 To be specific, the weight of each risk source corresponding to the risk node is { RS ] 1 ,RS 2 ,RS 7 } = {0.6833,0.1999,0.1168}, it can be seen that RS 1 The impact on functional risk is greatest. Because the process of constructing the judgment matrix and calculating the weight value belongs to the prior art, the description is omitted here.
After completing the evaluation of the probability of occurrence of the software risk, P, and the risk impact, E, then according to the Boehm formula: and obtaining a risk value R of each item of software risk by R=P×E, namely obtaining risk values of the target item of software under different risk classifications, as shown in table 5.
Table 5: and (5) comprehensively evaluating the software risk.
| Numbering device | Risk name | Probability of occurrence | Risk influence | Risk value |
| R1 | Risk of function | 0.42 | 0.7319 | 0.3074 |
| R2 | Performance risk | 0.442 | 0.6699 | 0.2961 |
| R3 | Reliability risk | 0.47 | 0.8462 | 0.3977 |
| R4 | Security risk | 0.29 | 0.3874 | 0.1123 |
| R5 | Resource risk | 0.25 | 0.2543 | 0.0636 |
| R6 | Cost risk | 0.37 | 0.1361 | 0.0501 |
| RD | Document material review risk | 0.4364 | 0.1742 | 0.076 |
Step S105, determining the implementation level of the target software project by using the importance degree, the risk values under different risk classifications, the estimated construction period and the development cost.
In this step, the implementation level may refer to an evaluation level at which the target software item may be implemented, and a higher implementation level indicates that the target software item may be implemented higher, and a lower implementation level indicates that the target software item may be implemented lower.
In the embodiment of the application, the implementation level of the target software item is comprehensively evaluated from three aspects, namely economy, technology and society, so as to form the implementation (or feasibility) evaluation report of the target software item.
In an alternative embodiment, determining the implementation level of the target software project using the importance, the risk values under different risk classifications, the estimated time period, and the development cost includes: determining implementation indexes of a target software project, wherein the implementation indexes comprise a first-layer implementation index and a second-layer implementation index, the first-layer implementation index comprises an economic index, a technical index and a social index, the second-layer implementation index corresponding to the economic index comprises an importance degree, a time cost and an economic cost, and the second-layer implementation index corresponding to the technical index comprises an implementation risk; determining a judgment set corresponding to the importance degree index, the time cost index and the economic cost index respectively based on the importance degree, the estimated construction period and the development cost; determining a judgment set corresponding to the implementation risk index based on the risk value; and determining the implementation level of the target software project based on the judgment set corresponding to the importance degree index, the time cost index and the economic cost index and the judgment set corresponding to the implementation risk index.
Specifically, firstly, determining a factor set of a target software item, namely determining implementation indexes of the target software item, wherein the implementation indexes mainly comprise two layers, and the first layer of implementation indexes U are { economic indexes U } 1 Technical index U 2 Social index U 3 Second layer implementation index U 1 = { importance, time cost, economic cost }, U 2 = { implementation risk }, U 3 = { social benefit, legal issue, ethical issue }.
Then, an evaluation set, that is, an evaluation level set of each of the second-layer implementation indexes is determined, and the evaluation levels of the implementation indexes can be classified into high, general, low, and low, so that a software item implementation index evaluation level table as shown in table 6 below can be obtained.
Table 6: the software project implements an index rating table.
It should be noted that, the implementation indexes of the importance degree, the time cost, the economic cost and the implementation risk in the above table may be determined sequentially according to the calculated importance degree, the estimated construction period, the development cost and the risk value, that is, the evaluation set may be determined according to the calculation results of the above steps.
Taking the evaluation set corresponding to the implementation index of determining the time cost as an example, comparing the calculated time cost with the expected time cost, if the calculated time cost is far smaller than the expected time cost, for example (calculated time cost-expected time cost)/expected time cost < -0.3, determining the evaluation level of the time cost as "very high", and determining the corresponding evaluation set, r4= (0.3, 0.4, 0.2, 0.1, 0) for this evaluation level. If the calculated time cost is much greater than the expected time cost, for example (calculated time cost-expected time cost)/expected time cost >0.3, then the evaluation level of the time cost is determined to be "very low", and the corresponding evaluation set, r4= (0, 0.1, 0.15, 0.2, 0.55) is determined for this evaluation level. And so on, the evaluation set of the evaluation indexes such as importance degree, economic cost and implementation risk can be determined.
The values in the evaluation set correspond to the high, general, low, and low evaluation levels in order from left to right, and the specific values in the evaluation set corresponding to the different evaluation levels are preset.
In addition, the above table is further added with implementation indexes of direct economic benefit, indirect economic benefit, technical level, project experience, project complexity and internal technical support of enterprises, and the implementation indexes can more accurately and comprehensively determine the implementation level of the target software project, and the implementation indexes can be used for determining a specific evaluation set by an expert according to experience.
In an alternative embodiment, determining the implementation level of the target software item based on the evaluation set corresponding to the importance level index, the time cost index, and the economic cost index, and the evaluation set corresponding to the implementation risk index, respectively, includes: determining the value of a judgment matrix corresponding to each first-layer implementation index based on a judgment set corresponding to the importance degree index, the time cost index and the economic cost index and a judgment set corresponding to the implementation risk index respectively; determining a weight vector matrix corresponding to the first layer implementation index and the second layer implementation index; based on the weight vector matrix and the evaluation matrix, evaluating the second implementation index and the first layer implementation index of the target software item in sequence to obtain a comprehensive evaluation result; and taking the grade corresponding to the evaluation result with the largest numerical value in the comprehensive evaluation results as the implementation grade of the target software project.
Specifically, after determining the evaluation set of each second-layer implementation index, a judgment matrix corresponding to each first-layer implementation index may be constructed. If the evaluation sets corresponding to the importance degree, the time cost and the economic cost are respectively marked as r1, r2 and r3, the economic index U can be obtained 1 The corresponding evaluation matrix, denoted as r1, r1= (R1, R2, R3), and so on, can determine the technical index U, respectively 2 Social index U 3 And respectively corresponding judgment matrixes R2 and R3.
And then, determining weight vector matrixes corresponding to the first-layer implementation indexes and the second-layer implementation indexes respectively according to experience. Taking the example that the economic index and the technical index in table 6 correspond to 5 second-layer implementation indexes, assume that a weight vector matrix corresponding to the first-layer implementation index is denoted as a, a= (0.45, 0.4, 0.15); u in second layer implementation index 1 The corresponding weight vector matrix is denoted as a1, a1= (0.3, 0.2, 0.1), U in the second layer implementation index 2 The corresponding weight vector matrix is denoted as a2, a2= (0.25, 0.2, 0.15), U in the second layer implementation index 3 The corresponding weight vector matrix is denoted as a3, a3= (0.3, 0.5, 0.2).
From M ([ lambda ] v, ], M ([ lambda ],and selecting one of the four operators as a calculation basis to calculate the implementation level of the target software item. Firstly, the implementation index of the second layer is evaluated, and B1, B2 and B3 can be obtained through calculation according to the following formulas: b1 =a1° R1, b2=a2° R2, b3=a3° R3, and then performing comprehensive evaluation to obtain a comprehensive evaluation result B, +. >Wherein r= [ B1, B2, B3 ]] T ，/>Representing the operator-corresponding calculator selected from the four operators listed aboveIn this way, the calculation methods of the above four operators belong to the prior art, and are not described here again.
Finally, determining the position of the maximum value in the comprehensive evaluation result B, and taking the grade corresponding to the position as the implementation grade of the target software item, for example: b= [0.2,0.5,0.1,0.2,0], it is found that the value 0.5 is maximum, and the implementation level corresponding to the value is high, and therefore, the implementation level of the target software item is determined to be high.
Compared with the implementation level determining method of the software project in the prior art, the method can construct a software influence network according to the data interaction relation between the target software project and the existing software project, determine importance parameters representing the importance degree of the target software project to the whole production process of the enterprise through a plurality of calculated software influence network parameters, and then determine the implementation level of the target software project from the importance degree, implementation risk, development period and development cost of the target software project to the enterprise, thereby being capable of determining whether the target software project needs to be implemented more accurately and comprehensively, and solving the problems that whether the software project needs to be implemented or not and whether the software project can be implemented cannot be determined accurately and comprehensively.
Based on the same inventive concept, the embodiment of the present application further provides a software item implementation level determining device corresponding to the software item implementation level determining method, and since the principle of solving the problem by the device in the embodiment of the present application is similar to that of the software item implementation level determining method in the embodiment of the present application, the implementation of the device can refer to the implementation of the method, and the repetition is omitted.
Referring to fig. 5, fig. 5 is a schematic structural diagram of a device for determining implementation level of a software item according to an embodiment of the present application. As shown in fig. 5, the software item implementation level determining apparatus 400 includes:
the interaction relation determining module 401 is configured to determine, based on input data and output data of a target software item, a first data interface corresponding to the target software item and a data interaction relation between the target software item and an existing software item;
the network diagram construction module 402 is configured to construct a software-affected network that reflects a data interaction relationship, determine values of a plurality of software-affected network parameters of the software-affected network, where the plurality of software-affected network parameters include an interaction relationship importance weight, an egress degree and an ingress degree of a software item;
The importance calculating module 403 is configured to determine an importance of the target software item based on the values of the plurality of software-affecting network parameters, where the importance is used to characterize an importance of the target software item to an entire production process of the enterprise;
a risk cost calculation module 404, configured to determine a predicted period of time, development cost, and risk value under different risk classifications for the target software project;
the implementation level determining module 405 is configured to determine an implementation level of the target software project using the importance level, the risk values under different risk classifications, the estimated time period, and the development cost.
Referring to fig. 6, fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the application. As shown in fig. 6, the electronic device 500 includes a processor 510, a memory 520, and a bus 530.
The memory 520 stores machine-readable instructions executable by the processor 510, and when the electronic device 500 is running, the processor 510 communicates with the memory 520 through the bus 530, and when the machine-readable instructions are executed by the processor 510, the steps of the method for determining a level of implementation of a software item in the method embodiment shown in fig. 1 can be executed, and a specific implementation is referred to the method embodiment and will not be described herein.
The embodiment of the present application further provides a computer readable storage medium, where a computer program is stored, where the computer program when executed by a processor may perform the steps of the method for determining a level of implementation of a software item in the method embodiment shown in fig. 1, and a specific implementation manner may refer to the method embodiment and will not be described herein.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
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. The above-described apparatus embodiments are merely illustrative, for example, the division of the units is merely a logical function division, and there may be other manners of division in actual implementation, and for example, 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 through some communication interface, device or unit indirect coupling or communication connection, 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 functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer readable storage medium executable by a processor. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Finally, it should be noted that: the above examples are only specific embodiments of the present application, and are not intended to limit the scope of the present application, but it should be understood by those skilled in the art that the present application is not limited thereto, and that the present application is described in detail with reference to the foregoing examples: any person skilled in the art may modify or easily conceive of the technical solution described in the foregoing embodiments, or perform equivalent substitution of some of the technical features, while remaining within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application. Therefore, the protection scope of the application is subject to the protection scope of the claims.
Claims (10)
1. A method for determining the implementation level of a software item, comprising:
determining a data interaction relationship between a target software item and an existing software item based on input data and output data of the target software item;
constructing a software influence network reflecting the data interaction relationship, and determining the values of a plurality of software influence network parameters of the software influence network, wherein the plurality of software influence network parameters comprise interaction relationship importance weights, the output degree and the input degree of the software items;
Determining importance of the target software item based on the values of the network parameters influenced by the plurality of software, wherein the importance is used for representing the importance degree of the target software item to the whole production process of an enterprise;
determining the predicted construction period, development cost and risk value under different risk classifications of the target software project;
and determining the implementation level of the target software project by using the importance degree, the risk values under different risk classifications, the estimated construction period and the development cost.
2. The method of claim 1, wherein determining the importance of the target item of software based on the values of the plurality of software-affecting network parameters comprises:
determining the sum of the output degree and the input degree of the target software item as the degree of the target software item;
calculating the sum of the interaction relation importance weights corresponding to all sides associated with the target software item in the software influence network, and determining the sum as the centrality of the target software item;
and determining the ratio of the centrality to the centrality as the importance of the target software item.
3. The method of claim 1, wherein the existing software project comprises a plurality of;
The construction of the software influence network reflecting the data interaction relation comprises the following steps:
determining the data interfaces corresponding to the target software item and the plurality of existing software items respectively;
selecting interfaces with data interaction relation with a plurality of existing software items from data interfaces corresponding to the target software items as first data interfaces;
selecting an interface with a data interaction relation with the target software item from the data interfaces corresponding to the plurality of existing software items as a second data interface;
respectively taking the first data interface of the target software item and the second data interface of the existing software item as nodes of a software influence network;
and according to the data input-output relation between the target software project and each existing software project, connecting different nodes through arrows with indicating the data interaction direction, and generating a software influence network.
4. The method of claim 1, wherein determining the implementation level of the target software project using the importance, risk values under different risk classifications, estimated time period, and development costs comprises:
determining implementation indexes of the target software project, wherein the implementation indexes comprise a first-layer implementation index and a second-layer implementation index, the first-layer implementation index comprises an economic index, a technical index and a social index, the second-layer implementation index corresponding to the economic index comprises an importance degree, a time cost and an economic cost, and the second-layer implementation index corresponding to the technical index comprises an implementation risk;
Determining an importance index, a time cost index and a judgment set corresponding to the economic cost index respectively based on the importance, the estimated construction period and the development cost;
determining a judgment set corresponding to the implementation risk index based on the risk value;
and determining the implementation level of the target software project based on the evaluation set corresponding to the importance degree index, the time cost index and the economic cost index and the evaluation set corresponding to the implementation risk index.
5. The method of claim 4, wherein determining the implementation level of the target software item based on the evaluation set corresponding to the importance level index, the time cost index, and the economic cost index, and the evaluation set corresponding to the implementation risk index, respectively, comprises:
determining the value of a judgment matrix corresponding to each first-layer implementation index based on the judgment set corresponding to the importance degree index, the time cost index and the economic cost index respectively and the judgment set corresponding to the implementation risk index;
determining a weight vector matrix corresponding to the first layer implementation index and the second layer implementation index;
based on the weight vector matrix and the evaluation matrix, evaluating the second implementation index and the first layer implementation index of the target software item in sequence to obtain a comprehensive evaluation result;
And taking the grade corresponding to the evaluation result with the largest numerical value in the comprehensive evaluation results as the implementation grade of the target software item.
6. The method of claim 1, wherein the determining the predicted time period, development costs, and risk values under different risk classifications for the target item of software comprises:
measuring the workload and development cost of the target software project by adopting a function point evaluation method, and determining the estimated construction period and development cost of the target software project;
and determining risk values of the target software item under different risk classifications.
7. The method of claim 6, wherein the determining risk values for the target item of software under different risk classifications comprises:
constructing a risk expression weight table for representing different risk levels under the initial risk classification;
determining the weight value of the target software item under the initial risk classification, and generating a risk identification situation table and a risk source identification situation table;
combining the risk identification situation table and the risk source identification situation table to generate a target risk and a target risk source list;
constructing a risk probability Bayesian network based on the target risk and a target risk source list;
And calculating the risk value of the target software item under different risk classifications by using the risk probability Bayesian network.
8. A software item implementation level determining apparatus, comprising:
the interactive relation determining module is used for determining the data interactive relation between the target software item and the existing software item based on the input data and the output data of the target software item;
the network diagram construction module is used for constructing a software influence network reflecting the data interaction relationship, determining the values of a plurality of software influence network parameters of the software influence network, wherein the plurality of software influence network parameters comprise interaction relationship importance weights, the output degree and the input degree of the software items;
the importance calculating module is used for determining the importance of the target software item based on the values of the network parameters influenced by the plurality of software, and the importance is used for representing the importance of the target software item to the whole production process of an enterprise;
the risk cost calculation module is used for determining the estimated construction period, development cost and risk value under different risk classifications of the target software project;
and the implementation level determining module is used for determining the implementation level of the target software project by utilizing the importance degree, the risk values under different risk classifications, the estimated construction period and the development cost.
9. An electronic device, comprising: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating over the bus when the electronic device is running, the processor executing the machine-readable instructions to perform the steps of the software item implementation level determination method of any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that it has stored thereon a computer program which, when executed by a processor, performs the steps of the software item implementation level determining method according to any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310843012.XA CN116862260A (en) | 2023-07-10 | 2023-07-10 | Method and device for determining implementation level of software project, electronic equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310843012.XA CN116862260A (en) | 2023-07-10 | 2023-07-10 | Method and device for determining implementation level of software project, electronic equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116862260A true CN116862260A (en) | 2023-10-10 |
Family
ID=88228189
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310843012.XA Pending CN116862260A (en) | 2023-07-10 | 2023-07-10 | Method and device for determining implementation level of software project, electronic equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116862260A (en) |
-
2023
- 2023-07-10 CN CN202310843012.XA patent/CN116862260A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11853724B2 (en) | Graph outcome determination in domain-specific execution environment | |
| Yang et al. | Friend or frenemy? Predicting signed ties in social networks | |
| Kumar et al. | Integrated blockchain and internet of things in the food supply chain: Adoption barriers | |
| Gyani et al. | MCDM and various prioritization methods in AHP for CSS: A comprehensive review | |
| Hayashi et al. | Structural characteristics of stakeholder relationships and value chain network in data exchange ecosystem | |
| Jamshidi et al. | Uncertain SBM data envelopment analysis model: A case study in Iranian banks | |
| CN109711849B (en) | Ether house address portrait generation method and device, electronic equipment and storage medium | |
| Loyola-González | Process mining: software comparison, trends, and challenges | |
| US20140156544A1 (en) | Non-Tangible Assets Valuation Tool | |
| Moreno et al. | Combining economic forecasts by using a maximum entropy econometric approach | |
| Lee et al. | An entropy decision model for selection of enterprise resource planning system | |
| Sukmana | The Evaluation of ITSM Open | |
| CN114862282B (en) | Business and financial cooperative management method and system based on data analysis | |
| Chen et al. | A PROMETHEE II approach based on probabilistic hesitant fuzzy linguistic information with applications to multi-criteria group decision-making (ICSSE 2020) | |
| CN116862260A (en) | Method and device for determining implementation level of software project, electronic equipment and medium | |
| Bendechache et al. | A Systematic Survey of Data Value: Models, Metrics, Applications and Research Challenges | |
| Utkin et al. | Combining of judgments in imprecise voting multi-criteria decision problems | |
| Esmaeili et al. | Conformance checking of the activity network with the social relationships structure in the context of social commerce | |
| Lim et al. | Evolving relationships between social networks and stakeholder involvement in software projects | |
| Wu | A comprehensive approach for the evaluation of the impact of blockchain on photovoltaic supply chain using hybrid data analytic method | |
| Wachs | Making markets for information security: the role of online platforms in bug bounty programs | |
| Kolesnikova et al. | Markov Principles of Project Effectiveness | |
| Indrasari et al. | ELECTRE III for Human Resource Management: A Study of Recruitment and Retention Strategies | |
| Elgazzar et al. | Incorporating fuzzy AHP in SCOR model for measuring supply chain operations performance: a case study of an Egyptian natural bottled water company | |
| Paulauskaite-Taraseviciene et al. | Service quotation generation using robotic process automation technology |
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 |