<Tr> <Td> Check / replace ink </Td> <Td> </Td> <Td> </Td> <Td> </Td> <Td> </Td> <Td> </Td> <Td> </Td> <Td> </Td> <Td>--</Td> </Tr> <Tr> <Td> Check for paper jam </Td> <Td> </Td> <Td> </Td> <Td> </Td> <Td> </Td> <Td> </Td> <Td> </Td> <Td> </Td> <Td>--</Td> </Tr> <P> Of course, this is just a simple example (and it does not necessarily correspond to the reality of printer troubleshooting), but even so, it demonstrates how decision tables can scale to several conditions with many possibilities . </P> <P> Decision tables, especially when coupled with the use of a domain - specific language, allow developers and policy experts to work from the same information, the decision tables themselves . </P>

Causes are the conditions in a decision table