The World Wide Web is evolving from being a pure information repository to a more functional and service oriented platform thanks to technologies such as Web Services. This technology offers a homogeneous representation of Web elements and the ways they are communicating that make it possible to deal with the inherent structural and behavioural heterogeneities of the Web. A Web service can be seen as an autonomous functional element that is loosely coupled to other Web services and can be discovered and deployed in Web-based applications. Autonomity and loose coupling make Web services a viable light weight complementary componentbased approach for design and development of dynamic distributed systems for more heavy weight solutions such as OMG’s CORBA and Microsoft’ s DCOM. In this paper, we take the position that if Web Services are going to be considered as reusable commercial of-the-shelf (COTS) components, their Quality of Service (QoS) needs to be expressed explicitly and measured independently. More specifically, we present and discuss possible quality aspects that need to be represented and quantified for Web Services.
[1]
Barry Boehm,et al.
Characteristics of software quality
,
1978
.
[2]
Roger S. Pressman,et al.
Software Engineering: A Practitioner's Approach
,
1982
.
[3]
Victor R. Basili,et al.
A Methodology for Collecting Valid Software Engineering Data
,
1984,
IEEE Transactions on Software Engineering.
[4]
Bev Littleword,et al.
Forecasting Software Reliability
,
1987
.
[5]
Victor R. Basili,et al.
The TAME Project: Towards Improvement-Oriented Software Environments
,
1988,
IEEE Trans. Software Eng..
[6]
簡聰富,et al.
物件導向軟體之架構(Object-Oriented Software Construction)探討
,
1989
.
[7]
Paul Rook,et al.
Software Reliability Handbook
,
1990
.
[8]
Shari Lawrence Pfleeger,et al.
Software Metrics : A Rigorous and Practical Approach
,
1998
.
[9]
Jean-Marc Jézéquel,et al.
Making Components Contract Aware
,
1999,
Computer.