CN104572120A - Service co-evolution software component reliability computing system - Google Patents

Abstract

The invention discloses a service co-evolution software component reliability computing system. The system is characterized by comprising an initializing module, a weighing module, a ruler module, a computing module, an evolution module and a displaying module. A service software components serve as an object; firstly, the initializing module establishes the definition and computation methods of software component credibility and reliability and sets the relevant initial information; secondly, the weighing module sets the weighing information of the computation of the software component reliability according to user's requirements; thirdly, the ruler module establishes the reliable co-evolution inference rules of the software component; fourthly, an updating model of the software component reliability is established, and the dynamic updating of the software component credibility and reliability in the co-evolution process can be implemented through the ruler module, the computing module and the evolution module and is displayed in real time through the displaying module. The effective quantitative computing method is provided for the software component reliability in the co-evolution process, and basis is provided for the subsequent reliable evolution of the software component.

Description

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

Technical field

This method relates to computer systems technology field, particularly relates to a kind of software element reliability computing system of service-oriented coevolution.

Background technology

Along with the development of Internet technology and software engineering, be particularly that the development of the technology of representative is with ripe with Web service, the emphasis that people pay close attention in the system of developing software has been transferred to gradually from the realization of each function and how have been existed by the various Service Assembly realizing concrete function, forms complete system.Service-oriented is a kind of emerging software development pattern, is widely accepted by industry member and academia.The software systems using this pattern to develop with the various services that internet distributes for elementary cell, by business function that is static or dynamically issuing service completion system.

But because the complicacy of software itself and software environment increases day by day, service-oriented software systems often have concertedness, dynamic and uncertainty.When in the face of concertedness, dynamic and uncertainty, service-oriented software more needs constantly to develop and could strengthen vitality, could the survival of the fittest.The credibility guarantee that the evolution of service-oriented software systems is faced with a lot of challenge, particularly Software Evolution becomes current important studying a question.Software Evolution is credible refers to that behavior in software evolution process and result meet the expection of people, meets the demand of user.The opening of Internet, Distributed Autonomous and no center control, and the feature such as the isomerism of software service itself, dynamic and concertedness further increases and ensures that service-oriented software systems develop credible difficulty.

Although current researcher has done a few thing in service-oriented software systems evolution, but most methods be all from software systems develop operation or rule start with, to describe or the service-oriented software systems of modeling develop, seldom consider concertedness and the Dependability Problem of software evolution process.

Summary of the invention

The object of the present invention is to provide a kind of software element reliability computing system of service-oriented coevolution.

Technical scheme of the present invention:

A software element reliability computing system for service-oriented coevolution, comprising:

(1) initialization module

For setting up definition and the computing method of degree of belief between service-oriented software component, set up definition and the computing method of service-oriented software element reliability, the service that in the software systems that initialization is service-oriented, each software component, software component provide, the mutually information such as service relation and relevant initial trust degree.

Definition and the computing method of wherein setting up degree of belief between service-oriented software component are as follows:

Software component a trusts the degree of certain service s that software component b provides, and is designated as Trust (a, b, s), brief note tr (a, b, s); A trusts the degree of b, is designated as Trust (a, b), be abbreviated as tr (a, b), arrange, the degree of trust simultaneously, i.e. degree of belief, represent with continuous variable t (0≤t≤4), wherein 0≤t≤1 represents minimum trust, and 1≤t≤2 represent general trust, 2≤t≤3 representative is trusted very much, and 3≤t≤4 representative is trusted completely; And the degree of belief tr (a, b) that a trusts b equals all mean value providing the degree of belief of service in a trust b, namely wherein, s _ifor the one service that b provides for a, 1≤i≤n;

Definition and the computing method of setting up service-oriented software element reliability are as follows:

In service-oriented software systems evolutionary process, other software components trust the weighted mean value of the degree of software component a, are called the confidence level of a, are designated as Credibility (a), be abbreviated as cr (a); The computing method of software element reliability are that be weighted average computation, circular is as follows by other software components to based on the degree of belief of this component:

Be located in service-oriented software systems evolutionary process, software component a is n software component b _iservice is provided, and b _ithe degree of trusting a is tr (b _i, a), 1≤i≤n, the then confidence level of a $\mathrm{cr}\left(a\right)={\mathrm{\α}}_1\mathrm{tr}(b_1,a)+{\mathrm{\α}}_2\mathrm{tr}(b_2,a)+...+{\mathrm{\α}}_n\mathrm{tr}(b_n,a)=\underset{i=1}{\overset{n}{\mathrm{\Σ}}}{\mathrm{\α}}_i\mathrm{tr}(b_i,a),$ Wherein α _ifor b _iweight, and α ₁+ α ₂+ ... + α _n=1.

Such as, in a service-oriented software systems evolutionary process, software component a only for software component b and software component c provides service, the degree of belief that b trusts a be tr (b, a), namely c trust the degree of belief of a be tr (c, a), namely wherein, s _ifor the one service that a provides for b, 1≤i≤n, s' _jfor the one service that a provides for c, 1≤j≤m, and b, c trust weight to a is respectively α, β (alpha+beta=1), then the confidence level of a $\mathrm{cr}\left(a\right)=\mathrm{\α}\mathrm{tr}(b,a)+\mathrm{\βtr}(c,a)=\mathrm{\α}\underset{i=1}{\overset{n}{\mathrm{\Σ}}}\mathrm{tr}(b,a,s_i)/n+\mathrm{\β}\underset{j=1}{\overset{m}{\mathrm{\Σ}}}\mathrm{tr}(c,a,{s^{\′}}_j)/m.$

In service-oriented software systems evolutionary process, the confidence level of software component can be used as other software components and judges whether to select this component to carry out the important references value of coevolution.

(2) weight module

By user interface, according to user's needs, dynamically arranging in system is correlated with provides the software component of service calculating the weight information in respective confidence level, namely for each software component a _i, according to the computing formula of its confidence level $\mathrm{cr}\left(a_i\right)={\mathrm{\α}}_1\mathrm{tr}(b_1,a_i)+{\mathrm{\α}}_2\mathrm{tr}(b_2,a_i)+...+{\mathrm{\α}}_n\mathrm{tr}(b_n,a_i)=\underset{j=1}{\overset{n}{\mathrm{\Σ}}}{\mathrm{\α}}_j\mathrm{tr}(b_j,a_i),$ And user's request, its corresponding weight α is set _j, j=1 ..., n.

(3) rule module

For setting up the credible coevolution inference rule of service-oriented software component, the credible coevolution inference rule of the service-oriented software component that the present invention sets up is as follows:

1) requirement rules: $\mathrm{Need}(a,s)\⇒\mathrm{Offer}(b_i,s)$

This Rule Expression, if software component a needs certain service s, is designated as Need (a, s), then in service-oriented software systems, has a software component b at least _iservice s can be provided for it, be designated as Offer (b _i, s), wherein presentation logic symbol " material implicatic ";

2) executing rule:

①

②

Wherein, 1. represent, if software component b can provide service s, be designated as Offer (b, s), and b promise provides service s to software component a, is designated as Promise (b, a, s), then under normal circumstances, b can complete service s for a, is designated as Done (b, a, s); 2. represent, if b can not provide service s, but still promise to undertake to a and provide service s, then obviously b can not complete service s for a, here presentation logic symbol " non-";

3) rule is trusted:

①

②

Wherein, 1. represent, software component b promises to undertake to software component a provides service s, is designated as Promise (b, a, s), and b finally for a complete service s, be designated as Done (b, a, s), then a trusts the service s that b provides, and is designated as Rely (a, b, s); 2. represent, b promises to undertake to a provides service s, but does not but finally complete service s, then a does not trust the service s that b provides;

4) rule is trusted:

① $\mathrm{Rely}(a,b,s)\⇒\mathrm{Trust}(a,b,s)+1\⇒\↑\mathrm{Trust}(a,b);$

②

Wherein, 1. represent, if software component a trusts the service s that software component b provides, be designated as Rely (a, b, s), then a to degree of belief (i.e. Trust (a, the b of the service s that b provides, s)) 1 is increased, according to the computing method of degree of belief between software component, thus a rises to the degree of belief (i.e. Trust (a, b)) of b; 2. represent, if a does not trust the service s that b provides, then a reduces 1 to the degree of belief of the service s that b provides, and according to the computing method of degree of belief between software component, thus a declines to the degree of belief of b;

5) credible rule:

① $\↑\mathrm{Trust}(a,b)\⇒\↑\mathrm{Credibility}\left(b\right);$

② $\↓\mathrm{Trust}(a,b)\⇒\↓\mathrm{Credibility}\left(b\right);$

Wherein, 1. represent, if software component a rises to the degree of belief (i.e. Trust (a, b)) of software component b, according to the computing method of software element reliability, then the confidence level of b in evolutionary process (i.e. Credibility (b)) rises; 2. represent, if a declines to the degree of belief of b, according to the computing method of software element reliability, then the confidence level of b in evolutionary process declines.

(4) computing module

For according to described information, the confidence level of described software component is calculated, specifically comprises two submodules:

1) degree of belief calculating sub module, for the computing method according to degree of belief between aforesaid service-oriented software component, calculates the degree of belief between service-oriented software component, namely to any two software component a and b, calculates the degree of belief that a trusts b wherein, s _ifor the one service that b provides for a, 1≤i≤n;

2) confidence level calculating sub module, for the computing method according to aforesaid service-oriented software element reliability, calculates the confidence level of service-oriented software component, namely to arbitrary software component a, calculates the confidence level of a $\mathrm{cr}\left(a\right)={\mathrm{\α}}_1\mathrm{tr}(b_1,a)+{\mathrm{\α}}_2\mathrm{tr}(b_2,a)+...+{\mathrm{\α}}_n\mathrm{tr}(b_n,a)=\underset{i=1}{\overset{n}{\mathrm{\Σ}}}{\mathrm{\α}}_i\mathrm{tr}(b_i,a),$ Wherein software component a is n software component b _iservice is provided, and b _ithe degree of trusting a is tr (b _i, a), α _ifor b _iweight, 1≤i≤n, and α ₁+ α ₂+ ... + α _n=1.

(5) genetic module

By user's input interface, record the coevolution information of each software component in service-oriented software systems, and according to the credible coevolution inference rule of service-oriented software component, dynamically updating of the degree of belief between the software component realizing service-oriented coevolution and the confidence level of component;

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

In service-oriented software systems coevolution process, there is provided certain to serve if certain software component is promised to undertake another software component in advance, then according to the actual performance of this service, determine whether this component service is trusted, if trusted, then the degree of belief of this component service increases by 1, if now its degree of belief more than 4, then still remains 4, if do not trusted, then the degree of belief of this component service reduces 1, if now its degree of belief is less than 0, then still remains 0; By adjusting the degree of belief of software component service, according to the computing formula of degree of belief between software component and software element reliability, the degree of belief between corresponding update software component and the confidence level of software component;

Wherein, in the software systems of service-oriented coevolution, each software component can provide several service, also can accept the several service that other software components provide, such as simultaneously, certain service s that software component c can provide, be designated as Offer (c, s), certain service s that software component c needs other software components to provide, represent with Need (c, s).

Such as, in service-oriented software evolution process, if certain software component a is in advance to another software component b ₁promise provides service s, and finally completes this service, then b ₁trust the service s that a provides, thus tr (b ₁, a, s) and=tr (b ₁, a, s) and+1 (if tr is (b ₁, a, s) and >4, then tr (b ₁, a, s)=4); Otherwise, if a does not finally complete service s, then b ₁do not trust the service s that a provides, thus tr (b ₁, a, s) and=tr (b ₁, a, s) and-1 (if tr is (b ₁, a, s) and <0, then tr (b ₁, a, s)=0); Then, according to computing formula corresponding calculating b ₁trust the degree of belief tr (b of a ₁, a), finally according to the computing formula of the confidence level of a $\mathrm{cr}\left(a\right)={\mathrm{\&alpha;}}_1\mathrm{tr}(b_1,a)+{\mathrm{\&alpha;}}_2\mathrm{tr}(b_2,a)+...+{\mathrm{\&alpha;}}_n\mathrm{tr}(b_n,a)=\underset{i=1}{\overset{n}{\mathrm{\&Sigma;}}}{\mathrm{\&alpha;}}_i\mathrm{tr}(b_i,a),$ Wherein α ₁+ α ₂+ ... + α _n=1, upgrade the confidence level of a.

The belief update model of the software component of this service-oriented coevolution as shown in Figure 1.

(6) display module

For the result of calculation by each software element reliability in software systems in service-oriented coevolution process, shown in real time by user interface.

The implementing procedure that the software element reliability of described computing system calculates is as follows:

(1) service, the mutually information such as service relation and relevant initial trust degree that in service-oriented software systems, software component, software component provide is pre-set;

(2) the relevant software component of service that provides in service-oriented software systems is set and is calculating the weight information in respective confidence level;

(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 computing 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 computing formula of the confidence level of the degree of belief between each software component and software component, the confidence level of each software component is calculated;

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

Advantage of the present invention is:

Compared with prior art, method of the present invention not only can realize the quantitative calculating of degree of belief in service-oriented software collaboration evolutionary process between software component and software element reliability, and, in coevolution process, the actual conditions that can complete according to service dynamically update the confidence level of degree of belief between software component and software component.

Accompanying drawing explanation

Fig. 1 is the Renewal model figure of the software element reliability of service-oriented coevolution of the present invention;

Fig. 2 is the structural drawing of the software element reliability computing system of service-oriented coevolution of the present invention;

Fig. 3 is the implementing procedure figure that the software element reliability of service-oriented coevolution in the present invention calculates.

Embodiment

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

Embodiment 1: be provided with a service-oriented book lending system, achieve the share service of library resource between colleges and universities, such as, each colleges and universities are by this system, service is waited to the college student Open book public use of cooperation, meanwhile, for convenience of student's inquiry, this system additionally provides online book inquiry service etc.Be provided with existing of the books that certain college student x has oneself to need in online enquiries to library A and B, to be on the safe side, x have submitted book borrowing and reading application service s, A and B to A and B simultaneously and also receives this application simultaneously, and promise provides Books Lent to serve s _a', s _b'.But according to the relative time of service, A, B provide Books Lent to serve s _a', s _b' require that x must complete Borrowing Service in official hour.Suppose within the stipulated time of library A, x first goes A to check out, and last is just borrowed by people unfortunately, and x transfers whereabouts library B and checks out, but, now more than the stipulated time of B.In this system service coevolution process, x, A and B can regard 3 software components as, and x provides book borrowing and reading application to serve s, A provides Books Search to serve s _awith Books Lent service s _a', B provides Books Search to serve s _bwith Books Lent service s _b'.X is in order to finally realize book borrowing and reading, and the Books Lent needing A to provide serves s _a' or B provide Books Lent serve s _b', and A will realize Books Lent, then x must be had to carry out the situation of book borrowing and reading application service s, B then similar.

In the coevolution process of this system, for library A and student x, the dynamic calculation of its confidence level is as follows in implementation process of the present invention:

(1) in initialization module, arrange the degree of belief in book lending system between software component, software element reliability computing formula as follows:

1) student x is to the degree of belief tr (x, A) of library A=(tr (x, A, s _a)+tr (x, A, s _a'))/2, wherein tr (x, A, s _a) for x trust A provide Books Search service s _adegree, wherein tr (x, A, s _a') for x trust A provide Books Lent service s _a' degree;

2) student x is to the degree of belief tr (x, B) of library B=(tr (x, B, s _b)+tr (x, B, s _b'))/2, wherein tr (x, B, s _b) for x trust B provide Books Search service s _bdegree, wherein tr (x, B, s _b') for x trust B provide Books Lent service s _b' degree;

3) library A is to degree of belief tr (A, the x)=tr (A, x, s) of student x, and wherein tr (A, x, s) trusts the degree of book borrowing and reading application s that x provides for A;

4) library B is to degree of belief tr (B, the x)=tr (B, x, s) of student x, and wherein tr (B, x, s) trusts the degree of book borrowing and reading application s that x provides for B;

5) confidence level cr (the x)=α of student x ₁* tr (A, x)+α ₂* tr (B, x), wherein α ₁, α ₂be respectively the weight that A, B trust x;

6) confidence level cr (the A)=β of library A ₁* tr (x, A), wherein β ₁for the weight that x trust A carries;

7) confidence level cr (the A)=β of library B ₂* tr (x, B), wherein β ₂for the weight that x trust B carries;

Etc..

The software component of this book lending system is then set, service that software component provides, the mutually information such as service relation and relevant initial trust degree, as can be arranged on this system start to develop time, 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 weight module, software component in book lending system is set and, calculating the weight information in respective confidence level, e.g., α is set ₁=α ₂=0.5, β ₁=β ₂=1 etc.

(3) in rule module, the credible coevolution inference rule of software component in book lending system is set, comprises requirement rules, executing rule, trust rule, trust rule and credible rule.

(4) in computing module, determine that in book lending system, the confidence level of software component is calculated as follows:

1) confidence level cr (x)=0.5*tr (A, the x)+0.5*tr (B, x) of student x;

2) confidence level cr (the A)=tr (x, A) of library A;

3) confidence level cr (the B)=tr (x, B) of library B;

And according to initialization information, the initial value of the degree of belief in calculating book lending system between software component, the confidence level of 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 in display module, show these information.

(5) in genetic module, according to book lending system scene information, the credible coevolution information that can obtain library A is as follows:

1) student x needs to borrow books, therefore have submitted service s request, and library A, B receive services request simultaneously, namely can be drawn by evolution inference rule 1: $\mathrm{Need}(x,{s_B}^{\&prime;})\&DoubleRightArrow;\mathrm{Offer}(B,{s_B}^{\&prime;});$

2) A is because last this book, before x borrows, is lent by outside other classmates, then can not be checked out to x, namely can be drawn by evolution inference rule 2:

3) A has failed to serve s _a', result in the service s that x provides A _a' do not trust, namely can be drawn by evolution inference rule 3:

Meanwhile, for library B, because the reason of student x self, fail to handle to library B in time to borrow formality, therefore B thinks that x is untrustworthy, thus B declines to the degree of belief of x, thus affect the confidence level of x.The coevolution information of x is as follows: x files an application, and namely promises to undertake to B and checks out, but does not check out to B at the appointed time, result in B not trusting, namely from evolution inference rule 3 the book borrowing and reading service s that x provides:

According to above evolution-information, x can be calculated and upgrade as follows to the degree of belief of A:

The service s that x provides A _a' do not trust, cause x to decline to the degree of belief of A, can be drawn by evolution inference rule 4: according to the degree of belief update method between the belief update model of the software component of service-oriented coevolution and software component, known: 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.

In like manner, calculating B upgrades as follows to the degree of belief of x:

B does not trust the service s's that x provides, causes B to decline to the degree of belief of x, from evolution inference rule 4: according to the degree of belief update method between the belief update model of the software component of service-oriented coevolution and software component, known: tr (B, x, s)=2-1=1, and tr (B, x)=tr (B, x, s)=1.

Then, according to the computing formula of the confidence level of software component, the belief update calculating A and x is as follows:

X declines to the degree of belief of A, causes the confidence level of A to decline, namely can be drawn by evolution inference rule 5: according to the Renewal model of the software element reliability of service-oriented coevolution and the confidence level computing formula with software component, the belief update of A is as follows: cr (A)=tr (x, A)=1.5, namely now the reliability dynamic of library A is updated to 1.5.

B declines to the degree of belief of x, causes the confidence level of x to decline, namely from evolution inference rule 5: according to the Renewal model of the software element reliability of service-oriented coevolution and the confidence level computing formula with software component, the belief update of x is as follows: cr (x)=0.5 × tr (A, x)+0.5 × tr (B, x)=0.5 × 2+0.5 × 1=1.5, namely now the reliability dynamic of student x is updated to 1.5.

(6) in display module, the confidence level of real-time update library A and student x is respectively 1.5 and 1.5.

Claims (8)

1. a software element reliability computing system for service-oriented coevolution, is characterized in that described computing system comprises:

Initialization module: for setting up definition and the computing method of degree of belief between service-oriented software component, set up definition and the computing method of service-oriented software element reliability, the service that in the software systems that initialization is service-oriented, each software component, software component provide, the mutually information such as service relation and relevant initial trust degree;

Weight module: calculating the weight information in respective confidence level for arranging the relevant software component of service that provides in system as required;

Rule module: for setting up the credible coevolution inference rule of service-oriented software component;

Computing module: for according to described information, calculate the confidence level of described software component, specifically comprises two submodules: 1) degree of belief calculating sub module, for calculating the degree of belief between service-oriented software component; 2) confidence level calculating sub module, 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 the confidence level of degree of belief between the software component dynamically updating service-oriented coevolution and component;

Display module: for showing the reliability information of each software component in service-oriented software systems in real time.

2. as weighed the computing system as described in 1, it is characterized in that, the technical scheme of described initialization module is as follows:

Set up definition and the computing method of degree of belief between service-oriented software component, set up definition and the computing method of service-oriented software element reliability, the service that in the software systems that initialization is service-oriented, each software component, software component provide, the mutually information such as service relation and relevant initial trust degree;

Definition and the computing method of wherein setting up degree of belief between service-oriented software component are as follows:

Software component a trusts the degree of certain service s that software component b provides, and is designated as Trust (a, b, s), brief note tr (a, b, s); A trusts the degree of b, is designated as Trust (a, b), be abbreviated as tr (a, b), arrange, the degree of trust simultaneously, i.e. degree of belief, represent with continuous variable t (0≤t≤4), wherein 0≤t≤1 represents minimum trust, and 1≤t≤2 represent general trust, 2≤t≤3 representative is trusted very much, and 3≤t≤4 representative is trusted completely; And the degree of belief tr (a, b) that a trusts b equals all mean value providing the degree of belief of service in a trust b, namely wherein, s _ifor the one service that b provides for a, 1≤i≤n;

Definition and the computing method of setting up service-oriented software element reliability are as follows:

In service-oriented software systems evolutionary process, other software components trust the weighted mean value of the degree of software component a, are called the confidence level of a, are designated as Credibility (a), be abbreviated as cr (a); The computing method of software element reliability are that be weighted average computation, circular is as follows by other software components to based on the degree of belief of this component:

Be located in service-oriented software systems evolutionary process, software component a is n software component b _iservice is provided, and b _ithe degree of trusting a is tr (b _i, a), 1≤i≤n, the then confidence level of a $\mathrm{cr}\left(a\right)={\mathrm{\&alpha;}}_1\mathrm{tr}(b_1,a)+{\mathrm{\&alpha;}}_2\mathrm{tr}(b_2,a)+...+{\mathrm{\&alpha;}}_n\mathrm{tr}(b_n,a)=\underset{i=1}{\overset{n}{\mathrm{\&Sigma;}}}{\mathrm{\&alpha;}}_i\mathrm{tr}(b_i,a),$ Wherein a _ifor b _iweight, and a ₁+ a ₂+ ... + a _n=1.

3. as weighed the computing system as described in 1, it is characterized in that, the technical scheme of described weight module is as follows:

By user interface, according to user's needs, dynamically arranging in system is correlated with provides the software component of service calculating the weight information in respective confidence level, namely for each software component a _i, according to the computing formula of its confidence level $\mathrm{cr}\left(a_i\right)={\mathrm{\&alpha;}}_1\mathrm{tr}(b_1,a_i)+{\mathrm{\&alpha;}}_2\mathrm{tr}(b_2,a_i)+...+{\mathrm{\&alpha;}}_n\mathrm{tr}(b_n,a_i)=\underset{i=1}{\overset{n}{\mathrm{\&Sigma;}}}{\mathrm{\&alpha;}}_j\mathrm{tr}(b_j,a_i),$ And user's request, its corresponding weight a is set _j, j=1 ..., n.

4. as weighed the computing system as described in 1, it is characterized in that, the technical scheme of described rule module is as follows:

Set up the credible coevolution inference rule of service-oriented software component, the credible coevolution inference rule of the service-oriented software component that the present invention sets up is as follows:

1) requirement rules: $\mathrm{Need}(a,s)\&DoubleRightArrow;\mathrm{Offer}(b_i,s)$

This Rule Expression, if software component a needs certain service s, is designated as Need (a, s), then in service-oriented software systems, has a software component b at least _iservice s can be provided for it, be designated as Offer (b _i, s), wherein presentation logic symbol " material implicatic ";

2) executing rule:

①

②

Wherein, 1. represent, if software component b can provide service s, be designated as Offer (b, s), and b promise provides service s to software component a, is designated as Promise (b, a, s), then under normal circumstances, b can complete service s for a, is designated as Done (b, a, s); 2. represent, if b can not provide service s, but still promise to undertake to a and provide service s, then obviously b can not complete service s for a, here presentation logic symbol " non-";

3) rule is trusted:

①

②

Wherein, 1. represent, software component b promises to undertake to software component a provides service s, is designated as Promise (b, a, s), and b finally for a complete service s, be designated as Done (b, a, s), then a trusts the service s that b provides, and is designated as Rely (a, b, s); 2. represent, b promises to undertake to a provides service s, but does not but finally complete service s, then a does not trust the service s that b provides;

4) rule is trusted:

① $\mathrm{Rely}(a,b,s)\&DoubleRightArrow;\mathrm{Trust}(a,b,s)+1\&DoubleRightArrow;\&UpArrow;\mathrm{Trust}(a,b);$

②

Wherein, 1. represent, if software component a trusts the service s that software component b provides, be designated as Rely (a, b, s), then a to degree of belief (i.e. Trust (a, the b of the service s that b provides, s)) 1 is increased, according to the computing method of degree of belief between software component, thus a rises to the degree of belief (i.e. Trust (a, b)) of b; 2. represent, if a does not trust the service s that b provides, then a reduces 1 to the degree of belief of the service s that b provides, and according to the computing method of degree of belief between software component, thus a declines to the degree of belief of b;

5) credible rule:

① $\&UpArrow;\mathrm{Trust}(a,b)\&DoubleRightArrow;\&UpArrow;\mathrm{Credibility}\left(b\right);$

② $\&DownArrow;\mathrm{Trust}(a,b)\&DoubleRightArrow;\&DownArrow;\mathrm{Credibility}\left(b\right);$

Wherein, 1. represent, if software component a rises to the degree of belief (i.e. Trust (a, b)) of software component b, according to the computing method of software element reliability, then the confidence level of b in evolutionary process (i.e. Credibility (b)) rises; 2. represent, if a declines to the degree of belief of b, according to the computing method of software element reliability, then the confidence level of b in evolutionary process declines.

5. as weighed the computing system as described in 1, it is characterized in that, the technical scheme of described computing module is as follows:

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

1) degree of belief calculating sub module, for the computing method according to degree of belief between aforesaid service-oriented software component, calculates the degree of belief between service-oriented software component, namely to any two software component a and b, calculates the degree of belief that a trusts b wherein, s _ifor the one service that b provides for a, 1≤i≤n;

2) confidence level calculating sub module, for the computing method according to aforesaid service-oriented software element reliability, calculates the confidence level of service-oriented software component, namely to arbitrary software component a, calculates the confidence level of a $\mathrm{cr}\left(a\right)={\mathrm{\&alpha;}}_1\mathrm{tr}(b_1,a)+{\mathrm{\&alpha;}}_2\mathrm{tr}(b_2,a)+...+{\mathrm{\&alpha;}}_n\mathrm{tr}(b_n,a)=\underset{i=1}{\overset{n}{\mathrm{\&Sigma;}}}{\mathrm{\&alpha;}}_i\mathrm{tr}(b_i,a),$ Wherein software component a is n software component b _iservice is provided, and b _ithe degree of trusting a is tr (b _i, a), a _ifor b _iweight, 1≤i≤n, and a ₁+ a ₂+ ... + a _n=1.

6. as weighed the computing system as described in 1, it is characterized in that, the technical scheme of described genetic module is as follows:

By user's input interface, record the coevolution information of each software component in service-oriented software systems, and according to the credible coevolution inference rule of service-oriented software component, dynamically updating of the degree of belief between the software component realizing service-oriented coevolution and the confidence level of component;

The dynamic updating method of the degree of belief between the software component of described service-oriented coevolution and the confidence level of component is as follows:

In service-oriented software systems coevolution process, there is provided certain to serve if certain software component is promised to undertake another software component in advance, then according to the actual performance of this service, determine whether this component service is trusted, if trusted, then the degree of belief of this component service increases by 1, if now its degree of belief more than 4, then still remains 4, if do not trusted, then the degree of belief of this component service reduces 1, if now its degree of belief is less than 0, then still remains 0; By adjusting the degree of belief of software component service, according to the computing formula of degree of belief between software component and software element reliability, the degree of belief between corresponding update software component and the confidence level of software component;

Wherein, in the software systems of service-oriented coevolution, each software component can provide several service, also can accept the several service that other software components provide simultaneously, as certain service s that software component c can provide, be designated as Offer (c, s), certain service s that software component c needs other software components to provide, represents with Need (c, s).

7. as weighed the computing system as described in 1, it is characterized in that, the technical scheme of described display module is as follows:

By the result of calculation of each software element reliability in software systems in service-oriented coevolution process, shown in real time by user interface.

8., as weighed the computing system as described in 1, it is characterized in that the implementing procedure that the software element reliability of described computing system calculates is as follows:

(1) service, the mutually information such as service relation and relevant initial trust degree that in service-oriented software systems, software component, software component provide is pre-set;

(2) the relevant software component of service that provides in service-oriented software systems is set and is calculating the weight information in respective confidence level;

(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 computing 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 computing formula of the confidence level of the degree of belief between each software component and software component, the confidence level of each software component is calculated;

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