The knowledge system ought to meet user
expectations. Performance typically depends on the standard of explicit/tacit
data hold on within the mental object. For the expert: quality relates to a
reasoning method that produces reliable and correct solutions inside the
knowledge system framework. For the user, quality relates to the system’s
ability to figure with efficiency. For the data developer, quality relates to
however well the data supply is and the way well the user's expectations square
measure written into the mental object.
It is needed to regulate performance,
efficiency, and quality of the mental object.
Logical Testing : to form certain that the
system produces correct results.
User Acceptance : Testing It follows logical
testing and checks the system's behavior during a realistic atmosphere
ISSUES: Subjective nature of data (tacit),Lack
of reliable specifications, Verifying correctness/consistency, Negligence just
in case of testing, Time limitations for data developers to check the system,
Complexity just in case of user interfaces.
Logical Testing Approaches : Verify the mental
object formation, The structure of the data because it relates to circular or
redundant errors is verified.
Consistency, correctness and completeness of
data base rules also are verified, Verify the mental object practicality.
User Acceptance Testing Approaches:
Selecting a person/team for testing, Deciding
on user acceptance check criteria, Developing a collection of check cases,
Maintaining a go surfing totally different versions of the checks and test
results, Field-testing the system.
Test Team/Plan : A testing arrange indicates
WHO is to try to do the testing. Commitment initiates with management support
and a check team with a check arrange. The team is predicted to be freelance of
the design/codification of the system , understand systems technology/knowledge
base infrastructure, be well versed within the organization's business.
Deciding on user acceptance check criteria:
Accuracy, Adaptability, Adequacy, Appeal, Availability, Ease of use,
Performance, Face validity, Robustness, Reliability, Operational/Technical
check.
User Acceptance check Techniques: Face
Validation, Developing a collection of check cases, Subsystem Validation,
Maintaining a go surfing totally different versions of the tests/test results,
Field testing the system.
No comments:
Post a Comment