1998
DOI: 10.1109/2.675643
|View full text |Cite
|
Sign up to set email alerts
|

Providing trusted components to the industry

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
13
0

Year Published

2002
2002
2015
2015

Publication Types

Select...
6
2
2

Relationship

0
10

Authors

Journals

citations
Cited by 38 publications
(13 citation statements)
references
References 0 publications
0
13
0
Order By: Relevance
“…Those constraints, if really needed, are best enforced by the business logic that manipulates the software repository, e.g. following Design-By-Contract [22], as recommended by best practices evolved over the years for the architecture of multi-tier information systems.…”
Section: Incremental Integrity Checking For Oclmentioning
confidence: 99%
“…Those constraints, if really needed, are best enforced by the business logic that manipulates the software repository, e.g. following Design-By-Contract [22], as recommended by best practices evolved over the years for the architecture of multi-tier information systems.…”
Section: Incremental Integrity Checking For Oclmentioning
confidence: 99%
“…If that was the case, any component could reasonably be expected to behave exactly as promised, and to use only those resources it required. Indeed, works are in progress that aim at providing so-called "trusted components" [15,12,14]. Hence, there is hope that, in the future, contract monitoring will not necessarily be required in all circumstances.…”
Section: Resource Contracting In Jamusmentioning
confidence: 99%
“…It is widely recognized that no single technique can produce completely trusted components [12]. The uniqueness of this paper is in identifying a problem that leads to creation of untrustworthy components and in using sophisticated algorithms developed in the area of secure communication protocol to solve it.…”
Section: Related Workmentioning
confidence: 99%