ly measure the key quality attributes discussed in the
previous sections of this paper; notably, the quality
factor “dynamism”, the “loose coupling” criteria and
the “physical, syntactic and semantic coupling”
metrics. That being said, it is important to note that
the SOAQE method must be reproduced for every
quality factor identified after having analyzed the
objectives of the company and the set of criteria and
metrics belonging to that quality factor.
4.1 Loose Coupling
Taking as a starting point an existing formula of the
field of “Preliminary analysis of risks” (see formula
3.1) (Mortureux, 2002) our works led to the
identification of a mathematical formula (see
formula 3.2) combining the three couplings studied:
semantic, syntactic and physical.
NB: The simplified formula (see formula 3.1)
usually used in the automotive industry, makes it
possible to measure the default risk of a car
component A is the Criticality of the car component,
B is the Probability of occurrence of a failure on this
component and C is the Probability of non-detection
of this failure.
We associate this concept of risk with our vision
of the coupling. Correlatively, the quintessence of
the coupling is the expression of the dependences
which can exist between two elements and the
principle of dependence defines that one element
cannot be used without the other. Reducing the risk
that the role defined by a service cannot be assured
anymore is decreasing the dependence of the
application in relation to this service and thus
reducing its coupling. The calculation of this risk
takes into account all the characteristics influencing
the coupling by redefining the three variables A, B
and C according to the semantic, syntactic and
physical couplings. The global coupling corresponds
to the sum of the three couplings calculated
individually beforehand. The lower this result is, the
more the coupling is weak.
NB: The criticality A
∈
[(a),(b),(c)] is affiliated to
the semantic coupling. ‘a’ if the service is only
associated to non predominant couplings, ‘b’ for
non predominants and low couplings and ‘c’ for non
predominants,low and high couplings, while ‘Ps’ is
the probability of failure of a service.
5 CONCLUSIONS
The finality of our work is to design a conceptual
framework and, in fine, a semi-automated prototype
(based on past methods, such as ATAM or SAAM)
which could quantify with an accurate value the
quality of the whole service oriented architecture.
Another pursued goal consists in bringing to the
customer "less abstract" documents than those
proposed today. The quality concept remaining a
relative one, we will target the sectors requiring a
special attention by directly addressing the various
development lab teams charged with the relevant
functions.
REFERENCES
Crnkovic, I., Chaudron, M., Larsson, S., 2006.
Component-based development process and
component lifecycle, ICSEA’06, International
Conference on Software Engineering Advances.
Clements, P., Kazman, R., Klein, M., 2001. Evaluating
Software Architectures: Methods and case studied,
published by Addison-Wesley Professional.
Hock-Koon, A., 2011. Contribution à la compréhension et
à la modélisation de la composition et du couplage
faible de services dans les architectures orientées
services. Thesis (PhD). University of Nantes.
Mortureux, Y., 2002. Preliminary risk analysis.
Techniques de l'ingénieur. Sécurité et gestion des
risques.
Perepletchikov, M., Ryan, C., Frampton, K., Tari, Z.,
2007. Coupling metrics for predicting maintainability
in service-oriented designs. ASWEC’07. Australian
Software Engineering Conference
SEI. The Carnegie Mellon Software Engineering Institute.
2011 [Online]. Available From: www.sei.cmu.edu/
architecture/start/glossary/
ISO/IEC 9126-1:2001: Software Engineering – Product
Quality – Part 1: Quality Model. International
Organization For Standardization, Geneva,
Switzerland [Online]. Available From:
Http://Www.Iso.Org/Iso/Iso_Catalogue/Catalogue_Tc/
Catalogue_Detail.Htm?Csnumber=22749
APPENDIX
Figure 3: Defaut risk of a car component (3.1) and global coupling of an architecture (3.2) formulas.
ENASE2012-7thInternationalConferenceonEvaluationofNovelSoftwareApproachestoSoftwareEngineering
202