Count of Contract Components (CCC):

This metric sums the counts the number of significant

components of a WSDL contract by assuming that the
complexity of developing each component is equal to
every other component.

CCC is defined as follows:

CCC = e + m + p + A
A = 1 if a service aggregation exists. Otherwise, A=0.

Where
e: be the number of Elements in Types
m: be the number of Messages,
p: be the number of Ports, and
A: be service Aggregation.
 Weighted Count of Contract Component (WCCC):

Assuming that a weight can be assigned a priori to every single

component of a contract, this metric will provide more information
than the preceding one.

Where
k Elements (in Types) of complexities e1, e2, … ek,
l messages of complexities m1, m2, … ml,
n ports of complexities p1, p2, … pn,
A Service Aggregation of complexity a,
 Metrics for Orchestration

• Consists of five components: Partner Links, Variables, Fault Handlers, Control Flow,
and Message Correlations.
• The first four components have proxies in other SOA artifacts. Hence, the
developer’s effort will be a function of these proxies.
• Each role in a Partner Link is mapped to exactly one WSDL (contract) Type. A
separate measure for partner link will have almost complete correlation with
measures for WSDL.
• The control flow in orchestration is captured by the control flow measures of the
process model.
• Hence, of the five, only message correlation is the one for which no proxy artifact
exists.
 Orchestration Complexity (OC):

This metric consists of three components. The first two

components represent the fact that a large portion of
orchestration is a function of contracts and its process model. The
third component is the count of the correlation sets.

OC = h(C, P, k)

Where

C be metric of contracts,
P be metric of business process model,
k be the number of correlation sets in a WSBPEL orchestration,
 SOA (Application) Component Density (SOACD):

This metric represents the average number of each component in

a SOA application. It can be used to assess the relative importance
of each type of component in a SOA application. A ranking of the
components could be constructed based on the value of this
metric. More emphasis will be placed on the higher ranked
components for impact analysis and risk assessment.
SOACDc = qc/t

Where
c: be one of the components of the SOA application. That is, cÎ {New
Services, Existing Services,Adapters, Existing Adapters, New Contracts,
Existing Contracts},
qc: be the count of the components of type c in the SOA application,
and
t: be Σ qc,(that is, t is the sum of the count of all the component
types.)
SOA (Application) Weighted Component Density
(SOAWCD):

is an extension to the previous metric. Here, a weight is

assigned to each component. The weights would be
proportional to the relative importance of each component
in the overall development process. For instance, the
relative weights for the development of new services would
be higher than the weights for others.

SOAWSCDc = (qc * wc) / t

 Conclusion

The goal of this research was to identify existing, modified,

or new metrics for estimating application developers’
throughput in SOA environments. We approached this
problem by identifying application artifacts in a SOA
environment. For each artifact, we either identified existing
metrics or developed new ones. Most of these metrics must
be validated empirically.Through validation, weights will be
derived for various components of the metrics
THANK YOU