Welcome!
To use the personalized features of this site, please log in or register.
If you have forgotten your username or password, we can help.
|
 |
Can Component/Service-Based Systems Be Proved Correct?
| |
|
Can Component/Service-Based Systems Be Proved Correct?
Christian Attiogbé21 
| (21) |
LINA, UMR CNRS 6241, University of Nantes, France |
Abstract
Component-oriented and service-oriented approaches have gained a strong enthusiasm in industries and academia with a particular
interest for service-oriented approaches. A component is a software entity with given functionalities, made available by a
provider, and used to build other application within which it is integrated. The service concept and its use in web-based
application development have a huge impact on reuse practices. Accordingly a considerable part of software architectures is
influenced; these architectures are moving towards service-oriented architectures. Therefore applications (re)use services
that are available elsewhere and many applications interact, without knowing each other, using services available via service
servers and their published interfaces and functionalities.
Industries propose, through various consortium, languages, technologies and standards. More academic works are also undertaken
concerning semantics and formalisation of components and service-based systems.
We consider here both streams of works in order to raise research concerns that will help in building quality software.
Are there new challenging problems with respect to service-based software construction, to service construction, an especially
to software verification? Besides, what are the links and the advances compared to distributed systems?
A specific emphasis should be put on correctness properties of services and on service-based systems in order to ensure their
quality and therefrom the durability of information systems and applications. Therefore an important research issue is to
reason on the correctness of software applications that will dynamically use or embed existing services. For example, additionally
to the formal specification of its functionalities, a service may embed its specific properties and the certificate/proof
that guarantees these properties.
Fulltext Preview (Small, Large)
 References secured to subscribers.
|
|
|
|
|
|