Validation
by
Kyriakos Kritikos
—
last modified
Apr 26, 2012 15:29
—
filed under:
KnowledgeModel
Definition of the term Validation
Definitions
Term: Validation |
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) |
The aim of Validation is to check if a system
being built or already built is the right one. Validation typically
involves the final user / client and is context dependent: the environment in which
the system is to be installed / executed has to be taken into account, as well as HCI issues. It is, therefore, difficult to formalize it fully, and it partly is a subjective process. [PO-JRA-2.2.1][Wikipedia] {ETC: Verification} |
Competencies
- UniDue: Quality Assurance; http://www.sse.uni-due.de/wms/en/?go=111;
Klaus Pohl, Andreas Metzger
- FBK: Service-Oriented Applications;http://soa.fbk.eu/research.php; Marco Pistore, Antonio Bucchiarone, Raman Kazhamiakin
- INRIA: Testing;http://www.irisa.fr/triskell/perso_pro/bbaudry/; Benoit Baudry