The process of evaluating software during or at the end of the development process to determine whether it satisfies specified business requirements.
To ensure
that the product actually meets the user’s needs, and that the specifications
were correct in the first place. In other words, to demonstrate that the
product fulfills its intended use when placed in its intended environment.
Determining
if the system complies with the requirements and performs functions for which
it is intended and meets the organization’s goals and user needs.
Validation is done at the end of the
development process and takes place after verifications are completed.
It answers the question like: Am I building
the right product?
Am I accessing the right data (in terms of
the data required to satisfy the requirement).
It is a High level activity.
Performed after a work product is produced
against established criteria ensuring that the product integrates correctly
into the environment.
Determination of correctness of the final
software product by a development project with respect to the user needs and
requirements.
According to
the Capability Maturity Model(CMMI-SW v1.1) we can also define validation as
The process of evaluating software during or at the end of the development
process to determine whether it satisfies specified requirements.
[IEEE-STD-610].
The most
tested attributes in validation tasks may include, but are not limited to
·
Selectivity/specificity
·
Accuracy
and precision
·
Repeatability
·
Reproducibility
·
Limit
of detection – especially for trace elements
·
Limit
of quantification
·
Curve
fitting and its range
·
System
suitability
No comments:
Post a Comment