Mismatches due to conflicts between the a priori conceptualization of of the user's domain by the designers and builders of an application and users' conceptualizations and expectations:
- System's private belief: The system's beliefs about the user's domain that is embedded in the components of the system that are hidden from users.
- System's common belief: The part of system's belief about the user's domain that is assumed to be shared with users.
- System's pending belief: The system's belief about users' beliefs of the users' domain.
- System's goal belief: The system's belief about users' goal(s).
- System's common vocabulary belief: The system's belief about the common vocabulary it shares with users.
Mismatches due to maxims the designers and builders AND users ascribe to the data an application captures and the information it reports:
- System tells the truth: The quality of the information the system reports has requisite fidelity to the facts.
- System reports concisely: The quantity of information the system reports says enough, but not too much.
- System reports relevantly: The information the system reports is relevant to the actual needs of users.
- System reports in appropriate form: The system reports information in the appropriate manner.
Mismatches due to the designers' and builders' assumptions about the content and structure of an application's database and users' assumptions:
- Extensional disparities: Users' false assumptions about the content of an application's database.
- Intensional disparities: Users' false assumptions about the structure of an applicaton's database (e.g., assumed non-existing relations by users).
Mismatches due to false assumptions by users about an application's current and future capabilities at the time an application is procured:
- Serviceability mismatches: An application is chosen for its serviceability, rather than its fit.
- Extensibility mismatches: False assumptions are made about an application's feature addition capabilities and carry forward of customizations at its next major upgrade.
- Constraint mismatches: False assumptions are made about external users' access to the system or about gateways enabling data access by other applicatons (e.g., the failure of a vendor to supply data entity keys through an XML gateway for the sake of the vendor's own business interests).
- Atomic requirement mismatches: False assumptions about an application's capability to satisfy users' atomic requirements (i.e., the lowest level requirements of users that are at a specificity that they require no further breakdown).
