OCL pre-conditions, post-conditions and invariants are used as a test oracle.
The framework is based on wEASEL, an abstract service model representing services and user tasks in terms of their signature, specification (i.e., context-aware pre-conditions, post-conditions and effects) and conversation (i.e., behaviour with related data-flow and context-flow constraints).
Use cases typically define one or more actors, a workflow, pre-conditions, post-conditions, and alternate scenarios.
A set of pre conditions and post conditions are generated for each code smell to ensure that they can be resolved beforehand.
In order to support service composition, services come with semantic markups that describe their functionalities, properties and conditions (pre and post conditions of the service).
It needs the specifications of pre-conditions and post-conditions for each DB test case.
Dynamic types checking, invariants, pre-conditions and post-conditions are done for run-time errors.
Business rules are specified through the declaration of restrictions, pre-conditions and post-conditions, and invariants in Object Constraint Language (OCL).
The next step is to define the set of rules, pre-conditions, and post-conditions to map to T. The mapping of transition T to the processes used in the MATF, referred to as rules (R).
Pre-conditions and post-conditions can be used to check whether materials and instruments are ready for execution of experiment actions, whether final volumes of solutions are correct, or whether objects are in the correct locations.
In order to address the question whether CA effectiveness might be potentially dependent on the baseline performance of the subjects, we performed linear Pearson-correlation analyses between baseline (pre-condition) and post-condition for all tasks.
