CN104572120B - A kind of software element reliability computing system of service-oriented coevolution - Google Patents

Abstract

The invention discloses a service-oriented collaborative evolution software component credibility calculation system, which is characterized in that the calculation system includes: an initialization module, a weight module, a rule module, a calculation module, an evolution module and a display module. The present invention takes the service-oriented software component as the object, first establishes the definition and calculation method of trust degree between software components, software component credibility, etc. through the initialization module, and sets relevant initial information; then sets the software component through the weight module according to user needs The weight information in the credibility calculation; then establish the trusted co-evolution reasoning rules of the software components through the rule module; then establish the update model of the software component credibility, and realize the process of co-evolution through the rule module, calculation module and evolution module The trust degree between software components and the dynamic update of the trust degree of software components are displayed in real time through the display module. The invention can provide an effective quantitative calculation method for the credibility of software components in the service-oriented software system cooperative evolution process, and provide a basis for the trusted evolution of subsequent software components.

Description

A Software Component Credibility Calculation System Oriented to Service Co-evolution

technical field

The method relates to the technical field of computer systems, in particular to a service-oriented collaborative evolution software component credibility calculation system.

Background technique

With the continuous development of Internet technology and software technology, especially the development and maturity of technology represented by Web services, the focus of people's attention in developing software systems has gradually shifted from the realization of various functions to how to implement each specific function. These services are assembled together to form a complete system. Service orientation is an emerging software development paradigm that has been widely accepted by industry and academia. The software system developed using this paradigm uses various services distributed on the Internet as the basic unit, and completes the business functions of the system by publishing services statically or dynamically.

However, due to the increasing complexity of the software itself and the software environment, service-oriented software systems are often collaborative, dynamic and uncertain. When faced with synergy, dynamism and uncertainty, service-oriented software needs continuous evolution to enhance vitality and survive of the fittest. The evolution of service-oriented software systems is facing many challenges, especially the credibility guarantee of software evolution has become an important research issue at present. Trustworthy software evolution means that the behavior and results in the process of software evolution meet people's expectations and meet the needs of users. The openness, distributed autonomy and non-central control of the Internet, as well as the heterogeneity, dynamism and collaboration of software services themselves further increase the difficulty of ensuring the credibility of service-oriented software system evolution.

Although current researchers have done some work on the evolution of service-oriented software systems, most methods start with the operations or rules of software system evolution, describe or model the evolution of service-oriented software systems, and seldom consider software evolution Process synergy and credibility issues.

Contents of the invention

The purpose of the present invention is to provide a service-oriented collaborative evolution software component credibility calculation system.

Technical scheme of the present invention:

A software component credibility calculation system oriented to service co-evolution, including:

(1) Initialize the module

It is used to establish the definition and calculation method of trust degree between service-oriented software components, establish the definition and calculation method of service-oriented software component trust degree, initialize each software component in a service-oriented software system, the services provided by software components, and the mutual Information such as service relationship and related initial trust degree.

Among them, the definition and calculation method of establishing trust between service-oriented software components are as follows:

The degree to which software component a trusts a certain service s provided by software component b is denoted as Trust(a,b,s), abbreviated as tr(a,b,s); the degree to which a trusts b is denoted as Trust(a, b), abbreviated as tr(a,b), and at the same time, it is agreed that the degree of trust, that is, the degree of trust, is represented by a continuous variable t (0≤t≤4), where 0≤t≤1 represents the minimum trust, and 1≤t≤ 2 represents general trust, 2≤t≤3 represents very trust, 3≤t≤4 represents complete trust; and the trust degree tr(a,b) of a trust b is equal to the average trust degree of all services provided in a trust b ,Right now Among them, s _i is a service provided by b for a, 1≤i≤n;

The definition and calculation method of establishing service-oriented software component credibility are as follows:

In the process of service-oriented software system evolution, the weighted average of the degree to which other software components trust software component a is called the credibility of a, which is recorded as Credibility(a), abbreviated as cr(a); The calculation method of the degree is based on the trust degree of other software components for this component, and the weighted average calculation is carried out. The specific calculation method is as follows:

Assuming that in the service-oriented software system evolution process, software component a provides services for n software components b _i , and the degree of b _i ’s trust in a is tr( _bi , a), 1≤i≤n, then the reliability of a Reliability

Wherein α _i is the weight of _bi , and α ₁ +α ₂ + . . . + α _n =1.

For example, in the evolution process of a service-oriented software system, software component a only provides services for software component b and software component c, and the trust degree of b trusting a is tr(b, a), namely The trust degree of c trusting a is tr(c,a), that is Among them, s _i is a service provided by a to b, 1≤i≤n, s' _j is a service provided by a to c, 1≤j≤m, and the trust weights of b and c to a are respectively α, β (α+β=1), then the credibility of a

In the process of service-oriented software system evolution, the credibility of software components can be used as an important reference value for other software components to judge whether to choose this component for co-evolution.

(2) Weight module

Through the user interface, according to the needs of users, dynamically set the weight information of the software components that provide services in the system in the calculation of their respective credibility, that is, for each software component a _i , according to the calculation formula of its credibility

As well as user needs, set their corresponding weights α _j , j=1, . . . , n.

(3) Rule module

It is used to establish the trusted co-evolution reasoning rules of service-oriented software components. The trusted co-evolution reasoning rules of service-oriented software components established by the present invention are as follows:

1) Requirement rules:

This rule indicates that if a software component a requires a certain service s, denoted as Need(a, s), then there is at least one software component b _i in a service-oriented software system that can provide service s, denoted as Offer(b _i ,s), where Indicates the "substantial implication" of logical symbols;

2) Execution rules:

①

②

Among them, ① means that if software component b can provide service s, which is recorded as Offer(b, s), and b promises to provide service s to software component a, which is recorded as Promise(b, a, s), then under normal circumstances , b will complete service s for a, recorded as Done(b,a,s); ② means that if b cannot provide service s, but still promises to provide service s to a, then obviously b cannot complete service s for a, here Indicates the logical symbol "not";

3) Trust rules:

①

②

Among them, ① means that software component b promises to provide service s to software component a, recorded as Promise(b,a,s), and b finally completes service s for a, recorded as Done(b,a,s), then a relies on the service s provided by b, which is recorded as Rely(a,b,s); ② means that b promises to provide service s to a, but fails to complete the service s, then a does not trust the service s provided by b;

4) Trust rules:

①

②

Among them, ① means that if the software component a trusts the service s provided by the software component b, denoted as Rely(a,b,s), then the trust degree of a to the service s provided by b (that is, Trust(a,b,s) ) increases by 1, and according to the calculation method of trust degree between software components, the trust degree of a to b (that is, Trust(a,b)) increases; ② means that if a does not trust the service s provided by b, then a provides The trust degree of the service s is reduced by 1, and according to the calculation method of the trust degree between software components, the trust degree of a to b decreases;

5) Credible rules:

①

②

Among them, ① means that if the trust degree of software component a to software component b (i.e. Trust(a,b)) increases, according to the calculation method of software component trust degree, the trust degree of b in the evolution process (i.e. Credibility (b)) rises; ② means that if the trust degree of a to b decreases, according to the calculation method of software component trustworthiness, the trustworthiness of b will decrease in the evolution process.

(4) Calculation module

It is used to calculate the reliability of the software component according to the information, and specifically includes two submodules:

1) The trust degree calculation sub-module is used to calculate the trust degree between service-oriented software components according to the aforementioned calculation method for the trust degree between service-oriented software components, that is, to calculate the trust degree of a for any two software components a and b trustworthiness of b Among them, s _i is a service provided by b for a, 1≤i≤n;

2) The credibility calculation sub-module is used to calculate the credibility of the service-oriented software component according to the aforementioned calculation method of the credibility of the service-oriented software component, that is, for any software component a, calculate the credibility of a Spend

Among them, software component a provides services for n software components b _i , and the degree of b _i ’s trust in a is tr( _bi , a), α _i is the weight of b _i , 1≤i≤n, and α ₁ +α ₂ + . . . +α _n =1.

(5) Evolution module

Through the user input interface, the co-evolution information of each software component in the service-oriented software system is recorded, and according to the trusted co-evolution reasoning rules of the service-oriented software component, the trust degree between the service-oriented co-evolution software components and the component’s trustworthiness are realized. Dynamic update of credibility;

The trust degree between software components and the dynamic updating method of the trust degree of components in service-oriented co-evolution are as follows:

In the process of co-evolution of service-oriented software systems, if a software component promises to provide a service to another software component in advance, it is decided whether to rely on the component service according to the actual completion of the service. If it is trusted, the component service The trust degree of the component service is increased by 1. If its trust degree exceeds 4 at this time, it will remain at 4. If it is not trusted, the trust degree of the component service will be reduced by 1. If its trust degree is less than 0 at this time, it will remain at 0. ; By adjusting the trust degree of the software component service, according to the calculation formula of the trust degree between software components and the trust degree of the software component, the trust degree between the software components and the trust degree of the software component are correspondingly updated;

Among them, in a service-oriented co-evolutionary software system, each software component can provide several kinds of services, and can also accept several kinds of services provided by other software components. For example, a certain service s that software component c can provide, record For Offer(c,s), software component c needs some kind of service s provided by other software components, denoted by Need(c,s).

For example, in the process of service-oriented software evolution, if a software component a promises to provide service s to another software component b ₁ in advance, and finally completes the service, then b ₁ relies on the service s provided by a, so tr(b ₁ ,a,s)=tr(b ₁ ,a,s)+1 (if tr(b ₁ ,a,s)>4, then tr(b ₁ ,a,s)=4); otherwise, if a Finally, the service s is not completed, then b ₁ does not rely on the service s provided by a, so tr(b ₁ ,a,s)=tr(b ₁ ,a,s)-1 (if tr(b ₁ ,a,s) <0, then tr(b ₁ ,a,s)=0); then, according to the calculation formula Correspondingly calculate the trust degree tr(b ₁ , a) that b ₁ trusts in a, and finally according to the calculation formula of the trust degree of a Where α ₁ +α ₂ + . . . +α _n =1, the reliability of a is updated.

The credibility update model of the service-oriented co-evolution software component is shown in Figure 1.

(6) Display module

It is used to display the calculation results of the credibility of each software component in the software system in the process of service-oriented co-evolution through the user interface in real time.

The implementation flow of the software component reliability calculation of the computing system is as follows:

(1) Preset information such as software components in service-oriented software systems, services provided by software components, mutual service relationships, and related initial trust degrees;

(2) Setting the weight information of the relevant software components providing services in the calculation of their respective credibility in the service-oriented software system;

(3) Set up trusted co-evolution reasoning rules for software components in service-oriented software systems;

(4) Obtain the co-evolution information of each software component in the service-oriented software system;

(5) Calculate the trust degree between each software component according to the above information and the calculation formula of trust degree between software components;

(6) Calculate the trustworthiness of each software component according to the trustworthiness among software components and the calculation formula of the trustworthiness of software components;

(7) Display the credibility of each software component in the service-oriented software system.

The advantages of the present invention are:

Compared with the prior art, the method of the present invention can not only realize the quantitative calculation of the trust degree between software components and the credibility of software components in the process of service-oriented software co-evolution, but also, in the process of co-evolution, can complete the According to the actual situation, the trust degree between software components and the trust degree of software components are updated dynamically.

Description of drawings

Fig. 1 is the updating model figure of the software component reliability of service-oriented co-evolution of the present invention;

Fig. 2 is a structural diagram of the software component credibility calculation system oriented to service co-evolution of the present invention;

Fig. 3 is an implementation flowchart of software component credibility calculation oriented to service co-evolution in the present invention.

Detailed ways

The present invention can be further described by the following examples, however, the scope of the present invention is not limited to the following examples.

Embodiment 1: There is a service-oriented book borrowing system, which realizes the sharing service of book resources among universities. For example, through this system, each university provides services such as book borrowing to cooperative university students. At the same time, in order to facilitate students' inquiries , the system also provides online book query services. Suppose a college student x finds out that library A and B both have the existing copies of the books they need. To be on the safe side, x submits the book loan application service s to A and B at the same time, and A and B also accept the book at the same time. apply, and promise to provide book lending services s _A ', s _B '. However, according to the relative timeliness of the service, A and B provide book lending services s _A ', s _B 'requiring x to complete the borrowing service within the specified time. Assuming that within the specified time of library A, x goes to borrow books from A first, but unfortunately the last one has just been borrowed, and x turns to borrow books from library B. However, it has exceeded the specified time of B at this time. In the process of service co-evolution of the system, x, A and B can be regarded as three software components, x provides book borrowing application service s, A provides book query service s _A and book lending service s _A ', B provides book query service service s _B and book lending service s _B '. In order to finally realize book borrowing, x needs the book lending service s _A ' provided by A or B to provide the book lending service s _B ', and to realize book borrowing, A must have x to apply for book borrowing service s, B The situation is similar.

In the co-evolution process of this system, taking library A and student x as an example, the dynamic calculation of its credibility is as follows in the implementation process of the present invention:

(1) In the initialization module, set the trust degree between software components in the book lending system, and the calculation formula of software component credibility is as follows:

1) Student x’s degree of trust in library A tr(x,A)=(tr(x,A,s _A )+tr(x,A,s _A ′))/2, where tr(x,A, s _A ) is the degree of book inquiry service s _A provided by x trust A, where tr(x,A,s _A ′) is the degree of book lending service s _A ’ provided by x trust A;

2) The trust degree of student x to library B tr(x,B)=(tr(x,B,s _B )+tr(x,B,s _B ′))/2, where tr(x,B, s _B ) the degree of book inquiry service s _B provided by x trust B, where tr(x,B,s _B ′) is the degree of book lending service s _B ' provided by x trust B;

3) Library A’s degree of trust in student x tr(A,x)=tr(A,x,s), where tr(A,x,s) is the degree of A’s trust in the book loan application s provided by x;

4) Library B’s degree of trust in student x tr(B,x)=tr(B,x,s), where tr(B,x,s) is the degree to which B trusts the book loan application s provided by x;

5) Credibility of student x cr(x)=α ₁ *tr(A,x)+α ₂ *tr(B,x), where α ₁ and α ₂ are the weights of A and B trusting x respectively;

6) Credibility of library A cr(A)=β ₁ *tr(x,A), where β ₁ is the weight of x trusting A;

7) Credibility of library B cr(A)=β ₂ *tr(x, B), where β ₂ is the weight of x trusting B;

and many more.

Then set information such as the software components of the book lending system, the services provided by the software components, the mutual service relationship, and the relevant initial trust degree. For example, it can be set that when the system starts to evolve, tr(x,A,s _A )=2, tr(x,A,s _A ′)=2, tr(x,B,s _B )=2, tr(x,B,s _B ′)=2, tr(A,x,s)=2, tr (B,x,s)=2.

(2) In the weight module, set the weight information of the software components in the book lending system in calculating their respective credibility, for example, set α ₁ =α ₂ =0.5, β ₁ =β ₂ =1 and so on.

(3) In the rule module, set the trusted co-evolution reasoning rules of software components in the book lending system, including requirement rules, execution rules, trust rules, trust rules and trust rules.

(4) In the calculation module, the calculation of the credibility of the software components in the book lending system is determined as follows:

1) The credibility cr(x) of student x=0.5*tr(A,x)+0.5*tr(B,x);

2) Credibility of library A cr(A)=tr(x,A);

3) Credibility of library B cr(B)=tr(x,B);

And according to the initialization information, calculate the trust degree among the software components in the book lending system, and the initial value of the trust degree of the software component is as follows: tr(A, x)=tr(A,x,s)=2, tr(B, x)=tr(B,x,s)=2, tr(x,A)=(tr(x,A,s _A )+tr(x,A,s _A ′))/2=2, tr( x,B)=(tr(x,B,s _B )+tr(x,B,s _B ′))/2=2, cr(x)=0.5*tr(A,x)+0.5*tr( B, x)=2, cr(A)=tr(x,A)=2, cr(B)=tr(x,B)=2, and display these information in the display module.

(5) In the evolution module, according to the scene information of the book lending system, the credible co-evolution information of library A can be obtained as follows:

1) Student x needs to borrow books, so he submits a request for service s, and libraries A and B accept the service request at the same time, that is, from evolutionary reasoning rule 1, it can be concluded that:

2) Because the last book of A has been lent out by other students before x came to borrow it, the book cannot be lent to x, that is, it can be obtained from evolutionary reasoning rule 2:

3) A fails to complete the service s _A ', which leads to x's distrust of the service s _A ' provided by A, that is, from evolutionary reasoning rule 3, it can be concluded that:

At the same time, for library B, due to student x's own reasons, he failed to go to library B to go through the borrowing procedures in time, so B thinks that x is unreliable, so B's trust in x decreases, thus affecting the credibility of x . The co-evolution information of x is as follows: x makes an application, that is, promises to borrow books from B, but fails to borrow books from B within the specified time, which leads to B’s distrust of the book lending service s provided by x, that is, evolutionary reasoning rule 3 It can be seen that:

According to the above evolution information, the trust degree update of x to A can be calculated as follows:

X's distrust of the service s _A ' provided by A leads to a decline in x's trust in A, which can be drawn from evolutionary reasoning rule 4: According to the trust update model of software components oriented to service co-evolution and the trust update method among software components, it can be known that: tr(x,A,s _A ')=2-1=1, and tr(x,A) =(tr(x,A,s _A )+tr(x,A,s _A '))/2=1.5.

Similarly, calculate B's trust update on x as follows:

B's distrust of the service s provided by x leads to a decline in B's trust in x, which can be known from evolutionary reasoning rule 4: According to the trust update model of software components oriented to service co-evolution and the trust update method among software components, it can be known that: tr(B,x,s)=2-1=1, and tr(B,x)=tr (B,x,s)=1.

Then, according to the calculation formula of the reliability of the software component, the calculation of the reliability of A and x is updated as follows:

The trust degree of x to A decreases, which leads to the decrease of the credibility of A, that is, it can be drawn from evolutionary reasoning rule 5:

According to the update model of software component credibility and the calculation formula of software component credibility for service co-evolution, the credibility of A is updated as follows: cr(A)=tr(x,A)=1.5, that is, at this time The credibility of library A is dynamically updated to 1.5.

B's trust in x decreases, resulting in a decrease in the credibility of x, which is known from evolutionary reasoning rule 5:

According to the update model of software component credibility and the calculation formula of software component credibility for service co-evolution, the credibility of x is updated as follows: cr(x)=0.5×tr(A,x)+0.5×tr (B,x)=0.5×2+0.5×1=1.5, that is, the credibility of student x is dynamically updated to 1.5 at this time.

(6) In the display module, the reliability of real-time update library A and student x are 1.5 and 1.5 respectively.

Claims (7)

1. A kind of 1. software element reliability computing system of service-oriented coevolution, it is characterised in that the computing system bag Include：

   Initialization module：For establishing the definition of degree of belief and computational methods between service-oriented software component, establish towards clothes The definition of the software element reliability of business and computational methods, initialize each software component in service-oriented software systems, soft What part component provided service, mutual service relation and relevant initial trust degree information；

   Weight module：For being arranged as required to the software component of related offer service in system in respective confidence level is calculated Weight information；

   Rule module：For establishing the credible coevolution inference rule of service-oriented software component；

   Computing module：For according to described information, calculating the confidence level of the software component, specifically including two submodules Block：1) degree of belief calculating sub module, for calculating the degree of belief between service-oriented software component；2) confidence level calculates submodule Block, for calculating the confidence level of service-oriented software component；

   Genetic module：For obtaining the coevolution information of each software component in service-oriented software systems, and dynamic updates The confidence level of degree of belief and component between the software component of service-oriented coevolution；

   Display module：The reliability information of each software component in the software systems service-oriented for real-time display；

   The technical solution of the initialization module is as follows：

   The definition of degree of belief and computational methods between service-oriented software component are established, it is credible to establish service-oriented software component The definition of degree and computational methods, initialize each software component in service-oriented software systems, software component provide service, Mutual service relation and relevant initial trust degree information；

   It is as follows wherein to establish the definition of degree of belief and computational methods between service-oriented software component：

   Software component a trusts the degree for certain service s that software component b is provided, and is denoted as Trust (a, b, s), brief note tr (a, b, s)；A trusts the degree of b, is denoted as Trust (a, b), is abbreviated as tr (a, b), arranges at the same time, the degree of trust, i.e. degree of belief, with Continuous variable t represents, wherein, 0≤t≤4,0≤t≤1 represents minimum trust, and 1≤t≤2 represent general trust, the generation of 2≤t≤3 Table is trusted very much, and 3≤t≤4 represent trusts completely；And a trust b degree of belief tr (a, b) be equal to a trust b in be provided with taking The average value of the degree of belief of business, i.e.,Wherein, s_iIt is that one kind that a is provided services for b, 1≤i≤n；

   Definition and the computational methods for establishing service-oriented software element reliability are as follows：

   In service-oriented software systems evolutionary process, other software component trusts the weighted average of the degree of software component a Value, is known as the confidence level of a, is denoted as Credibility (a), is abbreviated as cr (a)；The computational methods of software element reliability be with Based on other software component is to the degree of belief of this component, average computation is weighted, circular is as follows：

   It is located in service-oriented software systems evolutionary process, software component a is n software component b_iService, and b are provided_iTrust a's Degree is tr (b_i, a), the confidence level of 1≤i≤n, then a Wherein α i are b_iWeight, and α₁+α₂+…+α_n=1.
2. 2. computing system as claimed in claim 1, it is characterised in that the technical solution of the weight module is as follows：

   By user interface, according to user's needs, the related software component for providing service is calculating each in dynamic setting system Confidence level in weight information, i.e., for each software component a_i, according to the calculation formula of its confidence level

   And user demand, it is set Corresponding weight α_j, j=1 ..., n.
3. 3. computing system as claimed in claim 1, it is characterised in that the technical solution of the rule module is as follows：

   Establish the credible coevolution inference rule of service-oriented software component, the service-oriented software structure that the present invention establishes The credible coevolution inference rule of part is as follows：

   1) requirement rules：

   The Rule Expression, if software component a needs certain to service s, is denoted as Need (a, s), then in service-oriented software system At least one software component b in system_iThe provided service s of energy, is denoted as Offer (b_i, s), whereinRepresent logical symbol " material implicatic "；

   2) executing rule：

   ①

   ②

   Wherein, 1. represent, if software component b can provide service s, be denoted as Offer (b, s), and b is promised to undertake and carried to software component a For servicing s, Promise (b, a, s) is denoted as, then under normal circumstances, b can be that a completes service s, be denoted as Done (b, a, s)；② Represent, if b cannot provide service s, but still promised to undertake to a and provide service s, then obvious b cannot be that a completes service s, here Represent logical symbol " non-"；

   3) rule is trusted：

   ①

   ②

   Wherein, 1. represent, software component b is promised to undertake to software component a provides service s, is denoted as Promise (b, a, s), and b is final Service s is completed for a, is denoted as Done (b, a, s), then a trusts the service s that b is provided, and is denoted as Rely (a, b, s)；2. represent, b to A, which is promised to undertake, provides service s, but is not finally completed service s, then a does not trust the service s of b offers；

   4) rule is trusted：

   ①

   ②

   Wherein, 1. represent, if software component a trusts the service s that software component b is provided, be denoted as Rely (a, b, s), then a is to b Degree of belief, that is, Trust (a, b, s) increases by 1 of the service s of offer, according to the computational methods of degree of belief between software component, so that a pairs The degree of belief of b, that is, Trust (a, b) rises；2. represent, if the service s that service s, a that a does not trust b offers provide b Degree of belief reduces 1, according to the computational methods of degree of belief between software component, so that a declines the degree of belief of b；

   5) credible rule：

   ①

   ②

   Wherein, 1. represent, if software component a rises degree of belief, that is, Trust (a, b) of software component b, according to software component The computational methods of confidence level, then confidence level, that is, Credibility (b) risings of the b in evolutionary process；2. represent, if a is to b Degree of belief decline, according to the computational methods of software element reliability, then confidence levels of the b in evolutionary process declines.
4. 4. computing system as claimed in claim 1, it is characterised in that the technical solution of the computing module is as follows：

   According to described information, the confidence level of the software component is calculated, specifically includes two submodules：

   1) degree of belief calculating sub module, for the computational methods according to degree of belief between foregoing service-oriented software component, meter Degree of belief between service-oriented software component, i.e., to any two software component a and b, calculate the degree of belief that a trusts bWherein, s_iIt is that one kind that a is provided services for b, 1≤i≤n；

   2) confidence level calculating sub module, for the computational methods according to foregoing service-oriented software element reliability, calculates The confidence level of service-oriented software component, i.e., to any software component a, calculate the confidence level of a

   Wherein software component a is n software structure Part b_iService, and b are provided_iThe degree for trusting a is tr (b_i, a), α_iFor b_iWeight, 1≤i≤n, and α₁+α₂+…+α_n=1.
5. 5. computing system as claimed in claim 1, it is characterised in that the technical solution of the genetic module is as follows：

   By user's input interface, the coevolution information of each software component in service-oriented software systems is recorded, and according to The credible coevolution inference rule of service-oriented software component, realizes the letter between the software component of service-oriented coevolution Appoint the dynamic renewal of the confidence level of degree and component；

   The dynamic updating method of the confidence level of degree of belief and component between the software component of the service-oriented coevolution is such as Under：

   During service-oriented software systems coevolution, carried if certain software component in advance promises to undertake another software component For certain service, then according to the actual performance of the service, determine whether the component service is trusted, if trusted, the structure The degree of belief increase by 1 of part service, if its degree of belief is more than 4 at this time, still maintains as 4, if do not trusted, component clothes The degree of belief of business reduces 1, if its degree of belief is less than 0 at this time, still maintains as 0；Pass through the trust to software component service Degree is adjusted, according to degree of belief between software component and the calculation formula of software element reliability, between corresponding renewal software component Degree of belief and software component confidence level；

   Wherein, in the software systems of service-oriented coevolution, each software component can provide several service, at the same time The several service of other software component offer can also be provided, such as certain service s that software component c can be provided, be denoted as Offer (c, s), software component c need certain service s that other software component provides, are represented with Need (c, s).
6. 6. computing system as claimed in claim 1, it is characterised in that the technical solution of the display module is as follows：

   By the result of calculation of each software element reliability in software systems during service-oriented coevolution, pass through user interface Carry out real-time display.
7. 7. computing system as claimed in claim 1, it is characterised in that what the software element reliability of the computing system calculated Implementing procedure is as follows：

   (1) pre-set software component in service-oriented software systems, software component provide service, mutual service relation with And relevant initial trust degree information；

   (2) power of the related software component for providing service in respective confidence level is calculated in service-oriented software systems is set Weight information；

   (3) the credible coevolution inference rule of software component in service-oriented software systems is set；

   (4) the coevolution information of each software component in service-oriented software systems is obtained；

   (5) according to the calculation formula of degree of belief between above- mentioned information and software component, the degree of belief between each software component is calculated；

   (6) according to the degree of belief and the calculation formula of the confidence level of software component between each software component, each software component is calculated Confidence level；

   (7) confidence level of each software component in service-oriented software systems is shown.