Data Policy
by
Benedikt Liegener
—
last modified
Dec 01, 2010 16:36
—
filed under:
QualityAttribute,
KnowledgeModel
Definitions
| Term: Data Policy |
Domain: Cross-cutting issues | ||||
|---|---|---|---|---|---|
| Engineering and Design (KM-ED) |
Adaptation and Monitoring (KM-AM) |
Quality Definition, Negotiation and
Assurance (KM-QA) |
Generic (domain independent) |
||
| D o m a i n : L a y e r s |
Business Process Management (KM-BPM) |
||||
| Service Composition and
Coordination (KM-SC) |
|||||
| Service Infrastructure (KM-SI) |
|||||
| Generic (domain independent) |
When a service fails and then restarts, the client
needs to know if data returned by the service is still valid. To
specify this, we need to associate data policy with entities such as
return values or arguments. [CD-JRA-1.3.2] {GEN: Data-Related Quality} |
The data policy details the commitement to support the
management of the data in any organizations. |
|||
Competencies
- UCBL: Privacy-aware Web Services; http://liris.cnrs.fr/equipes?id=61&set_language=en; Salima Benbernou.
Scenarios
TBD
References
- [CD-JRA-1.3.2] "Quality reference model for service-based applications"
- Salima Benbernou, Hassina Meziane, Yin Hua Li, Mohand-Said Hacid: A Privacy Agreement Model for Web Services. IEEE SCC 2007: 196-203
