1999
DOI: 10.1109/2.774917
|View full text |Cite
|
Sign up to set email alerts
|

Making components contract aware

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
208
0
7

Year Published

2003
2003
2017
2017

Publication Types

Select...
4
4
1

Relationship

0
9

Authors

Journals

citations
Cited by 368 publications
(215 citation statements)
references
References 8 publications
0
208
0
7
Order By: Relevance
“…We are aware of the uselessness of our approach if we do not have a working prototype integrated with any of them, such as UDDI or similar. In this way, our quality trader is a component leveled at the top of a pyramid, wherein the lowerer levels are devoted to functional-aspects of WSP [1]. This stage of development is currently starting, but we hope to have a completely functional prototype in the very near future.…”
Section: Discussionmentioning
confidence: 99%
“…We are aware of the uselessness of our approach if we do not have a working prototype integrated with any of them, such as UDDI or similar. In this way, our quality trader is a component leveled at the top of a pyramid, wherein the lowerer levels are devoted to functional-aspects of WSP [1]. This stage of development is currently starting, but we hope to have a completely functional prototype in the very near future.…”
Section: Discussionmentioning
confidence: 99%
“…Programming and design by contract [2,12,13] consist in specifying what a software component, a program or a model does, in order to know how to properly use it. Design by contract also allows at runtime the assessment of what has been computed with respect to the expressed contracts.…”
Section: Contracts and Model Transformation Contractsmentioning
confidence: 99%
“…Programming and design by contract have shown their interest in verifying the execution of software systems [2,12,13]. Contracts ensure a sufficient confidence on the software system through a lightweight verification approach at runtime.…”
Section: Introductionmentioning
confidence: 99%
“…This underspecifies the components and limits their suitability and reuse to a specific area of application and environment. In [2], component contracts have been identified in four different levels: syntactic, behavioral, synchronization, and QoS. The explicit consideration of component QoS contracts aims at simplifying the development of component-based software with non-functional requirements like QoS, but it is also a challenging task.…”
Section: Introductionmentioning
confidence: 99%