Content uploaded by C K Gomathy
Author content
All content in this area was uploaded by C K Gomathy on Apr 23, 2019
Content may be subject to copyright.
International Conference on Current Trends in Engineering and Technology, ICCTET’14
►
51
◄
© IEEE 2014
IEEE - 33344
July 8, 2014, Coimbatore, India.
A Software Quality Metric Performance of
Professional Management in Service Oriented
Architecture
C.K.Gomathy
Assistant Professor
Department of computer science and Engineering
SCSVMV University, Enathur,
Tamilnadu, India.
gomathyck@gmail.com
S.Rajalakshmi
Professor
Department of computer science and Engineering
SCSVMV University,Enathur,
Tamilnadu, India.
Abstract –
Service-oriented architecture (SOA) is generally the
way of containing and examines to develop the information
management needs in order to make dealing responsive and elastic
in pace with forceful quality conditions. Adopting, implementing
and running SOA require considerable thought and effort in order
to distribute high-quality metrics data and become conscious the
complete assessment of SOA. In this paper, inspect the sequentially
and quality related metrics issues that have been investigated
organizations in order to uncover the activities in regard to
information quality within their initiatives of implementing SOA.In
the succession of quality behavior that solve certain information
quality and maintenance, development issues therefore, can be
enthusiastically established across any industry to support the
building of high quality and then making SOA solutions. In current
days service oriented architecture design is also incorporated and
potentially distributed with the quality metrics and to perform a
superior evaluation of the representation.
Keywords —
Service-oriented design, Quality of Service
progress, Web Intelligence, Architect performance, and
Quality Management in SOA, System constraints in SOA.
I. INTRODUCTION
An emergent number of associations are gradually
more investing in executing service-oriented architecture (SOA)
initiative for greater agility and for extraordinary level of
flexibility in order to compete in fast-changing universal
promotes spaces. A lot of grouping that implement SOA
initiative is gaining SOA value. SOA initiative that ignores
information issues is likely to fail and this bring to one key
problem that is information quality issue Incomplete, outdated,
incorrect or inconsistent information are examples indicating
poor information quality. These issues have many possible
solutions in which these solutions could be perceived as
activities in regard to information quality (IQ) that SOA team
like carried out throughout thru quality factors of services.
Manipulative structural design achieves its quality
attribute requirements is one of the most demanding tasks an
architect faces. It is demanding for several reasons including a
lack of specificity in the requirements, a shortage of documented
knowledge of how to design for particular quality attributes, and
the trade-offs involved in achieving quality attributes. It would
be desirable to have a method that guides the architect so that
any design produced by the method will reliably meet its quality
attribute requirements.
SOA dictates process and behavioral changes and
initiatives cannot be successful if essential human factors are
ignored. The two most significant cultural implications SOA
introduces are expectation and quality. Potential consumers of
services will typically develop their capabilities and use a
service they can’t explicitly trust. That is why the assurance of
quality and the proof of quality are absolutely essential to the
effectiveness of an SOA. Incentives are another cultural
implication of SOA. SOA demands changes in the behavior of
Service professionals who are used to creating and managing
monolithic applications in highly business settings.
The studies found that information management and
information quality are among the Success factors that makes
SOA implementation initiative a success. It have examined the
procedural factors of SOA success and discovered that
information management contributes to the extent to which
procedures are evident for ensuring data integrity and quality for
technical and business functions. Besides procedural factors, one
study indicates a higher quality output of services as one of
application design success factors for SOA implementation In
addition, defines correctness, performance, interoperability,
usability, maintainability, reliability and portability as some
major critical success factors for testing successful SOA.
Furthermore, a study stated that in order to be successful in SOA
implementation, the critical success factor would be accurate
data infrastructure. As SOA involves an architectural approach
International Conference on Current Trends in Engineering and Technology, ICCTET’14
►
52
◄
© IEEE 2014
IEEE - 33344
July 8, 2014, Coimbatore, India.
to information systems development it is important to look at
information quality applied in information systems research.
Basically, information quality is defined as “fitness for use”
where information that is appropriate for a specific uses and
satisfies the requirements of its consumers.
In this paper we identify some information quality
issues that evolve out of the implementation of SOA initiative
from open zone association/business or organizations. We also
discover the activities taken by their SOA team in regards to
information quality to react to these issues for quality
management. Responding to these issues within each
organization is a complex process in terms of the number of
errors, information systems and interactions.
II. RELATED WORK
Service-oriented architecture has turn into a well-
known in the current business and in order the technology of
SOA proved its worth in any public sector to leverage business
agility and flexibility. SOA is simply and describe it as a
technology for enabling business. The challenge of answering
what is SOA actually has become so important for many
organizations to clearly understand what it means and leverage
the quality value of SOA. Organizations that are pursuing an
SOA initiative and building and integrating systems using
quality approaches need to undertake several steps derived from
leading good services.
Service oriented architecture has defined along with
some other software quality attributes which contributed in
formative assessments of software architecture. The architectural
categories were not constrained by a particular programming
language, or domain. Software engineers have strived for the
strongly adequate software architecture. However, software
architecting was an iterative process and formative
assessments guide the architects to improve the qualitative
aspects in an iterative process. The categories proposed in given
paper have intended to help reviewers in formative assessments.
The role of formative assessments has stressed during the
development process in order to produce revised architectures
from initial work or working progress.
SOA consists of the public sector, business and
processes and rules required to control and guide the business
success of an SOA implementation. SOA provides a means to
ensure the quality, consistency, predictability, change and
interdependencies of services. Its overarching goal is to manage
the complexity created by SOA by ensuring that organizations
are able to capitalize on the powerful promise of SOA without
sacrificing control, predictability and efficiency. Said another
way, SOA is about blending the flexibility of service orientation
with the control of traditional software architectures. Service
oriented Architecture Risk Assessment (SOARA) tool designed
and implemented as a tool for computing and analyzing
architectural level risk factors like maintainability-based risk,
reliability-based risk and requirement-based risk.
III. MOTIVATION
Service oriented architecture is generally the structure
of components in a program or system, their interrelationships,
and the principles and design guidelines that control the design
and evolution in time.
• Service oriented architecture designing must be
completely a service oriented process with quality
aspects
• The effectiveness of Architectural design largely
depends on the quality attributes
• The quality attributes related to execution’s should be
fully supported
• Explore ways to improve the accuracy of architectural
knowledge sharing quality prediction
• For service-centric software systems specific properties
arising from the often distributed and cross-
organizational context are of central importance. The
reliability of a system, the availability of services, and
the individual service and overall system performance
are often essential.
IV. SOA FRAMEWORK
Software ability to work with each other, in the loosely
coupled environment of a service oriented architecture, separate
resources don’t need to know the details of how they each work,
but they need to have enough common ground to reliability
exchange message without error or misunderstanding.
Standardized specifications go a long way towards
creating this common ground, but differences in implementation
may still lead to breakdowns in communication. Interoperability
is when services can interact with each other without
encountering such problem.
SOA design is the activity of planning and organizing
people, infrastructure, communication and material components
of a service, in order to improve its quality and the interaction
between service provider and customers. By designing services
that are based on the needs of the customers the services will be
user friendly, competitive and relevant to the customers.
The Software Architect will be responsible for
contributing specialized technical knowledge in multiple
development efforts using object-oriented analysis & design,
Service Oriented Architecture (SOA), and distributed systems.
Principle responsibility will be the design and implementation of
an enterprise-class platform to enable application supportability
and performance management.SOA is the aggregation of
components that satisfy a design needs. It comprises
components, services, and processes. Components are binaries
that have a defined interface (usually only one), and a service is
International Conference on Current Trends in Engineering and Technology, ICCTET’14
►
53
◄
© IEEE 2014
IEEE - 33344
July 8, 2014, Coimbatore, India.
a grouping of components (executable programs) to get the job
done. This higher level of application development provides a
strategic advantage, facilitating more focus on the business
requirement. SOA isn't a new approach to software design; some
of the notions behind SOA have been around for years. A
service is generally implemented as a coarse-grained,
discoverable software entity that exists as a single instance and
interacts with applications and other services through a loosely
coupled (often asynchronous), message-based communication
model. The most important aspect of SOA is that it separates the
service's implementation from its interface. Service consumers
view a service simply as a communication endpoint supporting a
particular request format or contract
The backbone of SOA is to understand the behavior of
the customers, their needs and what kind of service that is
requested. these customer insights are obtained through quality
based. The desire for enterprise systems that have flexible
architectures, detailed designs, implementation agnostic, and
operate efficiently continues to grow. A major effort toward
satisfying this need is to use Service Oriented Architecture.
Moreover, there is new research and development in order to
achieve more demanding capabilities (e.g., workflow service
composition with run-time adaptation to changing Quality of
service attributes) that have been proposed for service- based
systems, especially in the context of system of systems.
Basic concept is for SOA to enable specifying the
creation of services that can be automatically composed to
deliver desired system dynamics while satisfying multiple
Quality of service attributes. Visibility and Real World Effect
are also key concepts for SOA. Visibility is the capacity for
those with needs and those with capabilities to be able to see and
interact with each other. This is typically implemented by using
a common set of protocols, standards, and technologies across
service providers and service consumers. For consumers to
determine if they can interact with a specific service, Service
Descriptions provide declarations of aspects such as functions
and technical requirements, related constraints and policies, and
mechanisms for access or response. The descriptions must be in
a form (or can be transformed to a form) in which their syntax
and semantics are widely accessible and understandable. The
execution context is the set of specific circumstances
surrounding any given interaction with a service and may affect
how the service is invoked.
A fundamental SOA concept is to enable flexible
composition of independent services in a simple way. The
simple concept is crucial since it separates details of how a
service is created and how it may be used. The technical quality
of SOA focused in quality. This kind of modularity is defined
based on the concept of brokers and its realization as the broker
service. The SOA conceptual framework lends itself to the
separation of concerns ranging from application domains (e.g.,
Figure 1. Technical Quality Framework of SOA
business logic) IT infrastructure to the choices of programming
languages and operating systems.The interoperability at the level
of services means loose coupling of reusable services. The high-
level description of the SOA principals does not account for the
operational dynamics of SOA, especially with respect to time-
based operations. Therefore, understanding the dynamics of a
service-based system using simulation is important. Simulation
can also support specific kinds of service-based software
systems that are targeted for business processes with specialized
domain Knowledge. In this given table1 explores a quality
attributes of timelines, availability, performance, Reliability,
Compos ability, Accessibility and discoverability of software
system.
Table 1. Quality Attributes in SOA
Quality Attributes Description
Proposed
Metrics
Timeliness The ability to respond in a
minimum specified time
period.
Service
Response
Time
Availability This quality attribute
measures the degree to
which service is accessible
and operational when
service consumer request to
use
Service
Support for
Transaction
Performance This quality attribute
measures the capability of
service to provide
appropriate response and
processing times and
throughput rates
Throughput
and
Number of
Services
Accessibility Represents the probability
of which service platform is
accessible while
Reliability It deals with the capability
of services to provide
transparent, reliable and
Service
Failure
Ratio
Technical
Quality
Functiona
lity
Reliability
Usability
Accuracy
Efficiency
Portability
Suitability
Interopera
bility
International Conference on Current Trends in Engineering and Technology, ICCTET’14
►
54
◄
© IEEE 2014
IEEE - 33344
July 8, 2014, Coimbatore, India.
fault tolerant services to its
user
Compos ability This quality attribute
measures the capability of a
service composition to
operate successfully by
composing atomic services
Number of
Version Per
Service
Discoverability A service interface should
use metadata to define the
service capabilities and
Constraints.
Service
Access
Method,
Service
Realization
Pattern
V. MAINTENANCE AND DEVELOPMENT OF
QUALITY IN SOA
Maintenance and development Effect are also key concepts for
SOA. It is the capacity for those with needs and those with
capabilities to be able to see and interact with each other. This is
typically implemented by using a common set of protocols,
standards, and technologies across service providers and service
consumers. For consumers to determine if they can interact with
a specific service, Service Descriptions provide declarations of
aspects such as functions and technical requirements, related
constraints and policies, and mechanisms for access or response.
The descriptions must be in a form or can be transformed to a
form in which their syntax and semantics are widely accessible
and understandable. The execution context is the set of specific
circumstances surrounding any given interaction with a service
and may affect how the service is invoked.
Figure 2. Maintenance and Development of SOA
Given that SOA adoption is fairly recent, much of the
current research has focused on the earlier stages of the life
cycle. In this above fig explores the main functionalities of
maintenance management systems and their interactions of
information systems and supplier relationship and customer
relationship through proper service maintenance. However, as
service-oriented systems are deployed, major concern shifts to
their maintenance and evolution. Service-oriented systems are
significantly different from traditional systems, resulting in new
explore issues that need to be addressed. These differences
include
(1) The diversity of service consumers and service providers
(2) Shorter release cycles because of the capability of rapidly
adapting to changing business needs
(3) The potential to leverage legacy investments with potentially
minimal change to existing systems.
An SOA Explores maintenance and evolution look like in this
dynamic, heterogeneous, and potentially distributed
development and maintenance environment. In this given table2
describes the evaluating formula of quality of software system in
service progress.
Table 2. Quality Metrics formula
Metric Name
Description Evaluating
Formula
Task
Completion
It compute in the form
of binary data’s which
a special type of
discrete data is. The
task completion has
two stages as
Complete(C) and not
complete (NC).
Tc=C for i=0
Nc for i=1
Weighted
Service
Interface
Count
(WSIC)
The weighted number
of exposed interfaces
or operation per
service on the Web
Service
Definition Language
(WSDL) documents
Default Weight =
1
Stateless
Services
(SS)
The fraction of
services which are
stateless
(SLS) as opposed to
state full (SFS) as
defined in the service
resource framework.
SS = SLS/(SLS
+SFS)
Service
Realization
Pattern (SRP)
The fraction of
services that are
realized
through indirect
exposure (IE) in
respect to the total
number of services
that are realized using
both IE and direct
exposure
(DE).
SRM = IE / ( IE
+DE)
International Conference on Current Trends in Engineering and Technology, ICCTET’14
►
55
◄
© IEEE 2014
IEEE - 33344
July 8, 2014, Coimbatore, India.
Service
Access
Method
(SAM)
The fraction of
services accessed
using
virtualization layer,
referred to as
Virtualized Access
Services (VAS), in
respect to the total
number of services
that are VAS or
accessed
point to point (PPS
SAM = VAS /
(VAS
+ PPS)
Time on task Time on task is the
time taken by the
software to execute a
particular task or
program.
T(t)=task(T)/time(
t)
Dynamic vs.
Static
Service
Selection
(DSSS)
The number of
services that are
selected
dynamically (DS)
Over the total number
that
are selected
dynamically or
statically (SS).
DSSE = DS / (DS
+SS)
Number of
Versions
Per Service
(NOVS)
The total number of
versions over the total
number of service
within the SOA
solution.
NOVS=VERSION
S /SERVICES
Service
Response
Time (SRT)
This metric is an
elapsed time between
the end of a request to
a service and the
beginning of the
service’s response
SRT = Time when
Service Consumer
finishes sending
request to the
service
– Time when
Service Consumer
starts
receiving
response from the
service
Service
Failure Ratio
(SFR)
SFR metric is to
measure the ratio of
how many services
failed during a specific
time interval. This
metric can be
calculated with the
following formula.
SFR = Time
Period /
Number of
Failures
Throughput Throughput refers to
the maximum amount
of services provider
can process in a given
time period. The
maximum number of
responses which can
be processed in a unit
time
Throughput =
Number of
requested
processed by
service in
measured time/
Measured time
.
Error Count The error count is the
total number of error
that is generated while
executing the
software. The error
that is generated per
second.
Ec=e/t
Software
Quality
The quality of the
software is thus
evaluated and based
on the quality the
effectiveness
Q=1-Rd
(Defective rate
Rd=Td/Tt)
Td-Total defects,
Tt-Total Task
VI. DESCRIPTION OF THE WORK
Formal methods for service analysis and various quality
attributes such as maintainability, reliability, readability,
usability etc. have to be considered while designing software. In
this work, proposed an efficient Software architecture model
based on Software design a pattern which is based on Service
Oriented Architecture (SOA) with major consideration being the
quality metrics. Architectural and design patterns are recurring
solutions to software design problems. The SOA design is
generally the way of designing a software system to provide
service to either end user or other service through published
interfaces. The usage of service oriented architectural patterns in
design provides reusable and extensible technical solutions to
common design problems in a standard Architectural format.
The architecture design is also incorporated with the quality
metrics like usability and portability to perform a better software
architectural design.
As the system operates based on the service oriented
architectural design process, it has used application software as
the input for which the architectural pattern is designed. The
SOA based design strategy can be more efficient in designing
such application software’s rather than other such methods. The
resulting software must be completely service oriented that
should benefit the user at a larger extend. The performance of
the software can be measured with the help of various metrics
like task completion, time on task (usage time), error counts and
satisfaction scores through a process called quality constraint
International Conference on Current Trends in Engineering and Technology, ICCTET’14
►
56
◄
© IEEE 2014
IEEE - 33344
July 8, 2014, Coimbatore, India.
methods and the development is measured using the quality
method. The proposed method delivers fine outcome in the form
of design metrics when compared with the existing works. A
web service oriented application will be used for this quality
based software architectural design. Design patterns will play an
efficient role in the design of Web service architectures.
VII. CONTRIBUTION OF THE PAPER
The messaging patterns with quality aware software
architecture remain as one of the basic needs while designing of
web sphere resources. Various quality attributes such as
maintainability, reliability, readability, usability etc. have to be
considered while designing software. In this work, we have
proposed an efficient software architecture model and
information system based on Software design a pattern which is
based on Service Oriented Architecture (SOA) with web
services with major consideration being the quality metrics.
quality will assign both supplier and customer. Architectural and
design patterns are recurring solutions to software design
problems. The SOA design is generally the way of designing a
software system to provide service to either end user or other
service through web and published interfaces. The usage of
service oriented architectural patterns in our design provides
reusable and extensible technical solutions to common design
problems in a standard Architectural format. The web service
architecture design is also incorporated with the pattern with
quality metrics like usability and portability to perform a better
software architectural design. In this design patterns will play an
efficient role in the design of Web services architectures.
VIII. CONCLUSION
This paper proposed a new intelligence with service
oriented architect paradigm to enable system quality to connect
with evaluating formulas of software architectural models from
which it is possible to extract precisely information. Our scheme
has been proven software design with quality in the standard
model. A systematic complexity analysis in performance and
development are extensive experiments. It shows that our
proposal is also efficient in terms of computation and non
functional requirements of design network used to describe
different varieties of messages in SOA.These features of service
with network analysis framework scheme a talented solution to
group-service oriented communication with access control in
various types of software system design.
REFERENCES
[1] Lihua Xu, Hadar Ziv, Thomas A. Alspaugh and Debra J.
Richardson,"An architectural pattern for non-functional
dependability requirements”, The Journal of Systems and
Software, Vol.79, pp.1370–1378, 2006.
[2] Jehad Al Dallal,"Software Similarity-Based Functional
Cohesion Metric”, Journal of IET Software, Vol. 3, No.
1,pp.46 - 57,Feb 2009.
[3] qbaldeep Kaur, Parvinder S. Sandhu, Hardeep Singh, and
Vandana Saini ,"Analytical Study of Component Based
Software Engineering",World Academy of Science,
Engineering and Technology,Vol.50,pp.437-442, 2009.
[4] Olaf Zimmermann, Jana Koehler, Frank Leymann, Ronny
Polley and Nelly Schuster,"Managing architectural decision
models with dependency relations, integrity constraints, and
production rules”, The Journal of Systems and Software,
vol.82, pp.1249–1267, 2009.
[5] Adel Smeda, Adel Alti, Mourad Oussalah, and Abdallah
Boukerram,'Cosastudio: A Software Architecture Modeling
Tool ", World Academy of Science, Engineering and
Technology,Vol.49, pp.263-266, 2009.
[6] Iqbaldeep Kaur, Parvinder S. Sandhu, Hardeep Singh, and
Vandana Saini ,"Analytical Study of Component Based
Software Engineering",World Academy of Science,
Engineering and Technology,Vol.50,pp.437-442, 2009.
[7] Chon Abraham,Iris Junglas and Mike Willis, “Systems
Analysis and Design for Service Oriented Architecture
Projects: A Case Study at the Federal Financial Institutions
Examinations Council (FFIEC)",Journal of Emerging Trends
in Computing and Information Sciences,Vol.2,No.1,2010.
[8] A.Appandairaj and Dr. S.Murugappan, "Service Oriented
Architecture Design For Web Based Home Banking Systems
With Cloud Based Service", International Journal of
Emerging Technology and Advanced Engineering, Vol.3,
No.1, 2013.
[9] W.M.Abdelmoez, A.H.Jalali,K.Shaik ,T. Menzies and H.H.
Ammar,"Using Software Architecture Risk Assessment For
Product Line Architectures",In.Proc.of.International
Conference On Communication, Computer And Power
(Icccp'09) Muscat, February 15-18, 2009.
[10] Michael P. Papazoglou and Willem-Jan van den
Heuvel,"Service-Oriented Design and Development
Methodology",Int. J. of Web Engineering and Technology
(IJWET), 2006
[11] Outi Raiha, Erkki Makinen and Timo Poranen ,"Using
Simulated Annealing for Producing Software
Architectures",Thesis,Department Of Computer Sciences
,University Of Tampere, Apr 2009.
[12 ]Suntae Kim , Dae-Kyoo Kim, Lunjin Lu and Sooyong Park
,"Quality-driven architecture development using architectural
tactics",The Journal of Systems and Software, Vol.82,
pp.1211–1231,2009.
[13] Indika Meedeniya ,"Robust Optimization of Automotive
Software Architecture",In.proc.of AutoCRC Technical
Conference,2011.
[14] Weifeng Pan ,"Applying Complex Network Theory to
Software Structure Analysis",World Academy of Science,
Engineering and Technology,Vol.60,pp.1636-1642, 2011.
[15] Liliana Dobrica, Anca Daniela Ioniţa, Radu Pietraru And
AdrianaOlteanu ,"Automatic Transformation Of Software
Architecture Models",U.P.B. Sci. Bull, Series C, Vol. 73, No.
3, pp.3-16, 2011.
International Conference on Current Trends in Engineering and Technology, ICCTET’14
►
57
◄
© IEEE 2014
IEEE - 33344
July 8, 2014, Coimbatore, India.
[16] G. M. Tere and B. T. Jadhav, "Design Patterns for Successful
Service Oriented Architecture Implementation", International
Journal of Information Technology,Vol. 2,No. 2,2010.
[17] Pradip Peter Dey ,"Strongly Adequate Software
Architecture", World Academy of Science, Engineering and
Technology,Vol.60 ,pp.366-369, 2011.
[18] Apostolos Ampatzoglou, Georgia Frantzeskou and Ioannis
Stamelos ,"A methodology to assess the impact of design
patterns on software quality",Information and Software
Technology, Vol.54, pp.331–346,2012.
[19] Raed Shatnawi and Wei Li,"An Empirical Assessment of
Refactoring Impact on Software Quality Using a Hierarchical
Quality Model", International Journal of Software
Engineering and Its Applications, Vol. 5, No. 4, Oct 2011.
[20] Rick Sobiesiak and Yixin Diao,"Quantifying Software
Usability Through complexity Analysis", IBM Press, 2010.
