4.13 Elementary Method "Decision Table Technique" (DTAB)
4.13 Elementarmethode "Entscheidungstabellentechnik" (ETAB)
/DIN 66241, 1978/ pp. 1-4
Objective and Purpose
The Decision Table Technique (DTAB) is a means to represent decision situations in a clear, unambiguous, and brief manner.
The decision tables used in this connection are composed of a number of decision rules relevant in a certain situation. A decision rule defines an action or a sequence of actions that are to be executed for a certain combination of satisfied conditions.
Means of Representation
A decision table consists of
Decision tables can be linked with follow-up decision tables, depending on the complexity of the decision situation to be represented.
- the condition part listing the conditions relevant in the decision situation,
- the action part containing a list of all possible actions,
- the condition indicating part containing the combinations of the states possible for the conditions, and
- the action indicating part that can be used to define the corresponding actions to be carried out.
The application is realized with the following steps:
Returns and loops within complex decision processes can be represented, though not in a very clearly set up way. Checking completeness, redundancy, and consistency requires the support of a tool.
- Recording of the initial situation
- The conditions and actions are defined and listed.
- All combinations of condition indicators that are formally possible are specified.
- The action indicators are completed rule by rule.
- The table is checked if unambiguous and complete.
- Selection of the applying decision rule
If the current condition constellation is known the decision rule applying to this case will be selected.
- Execution of the actions
With the execution of the action defined in the selected rule the decision process is completed.
SD2.6 - Specification of System Integration
SD4.3 - Specification of SW Integration
On the one hand, applying the decision table technique allows the description of the integration steps required to combine the segments to the system, the SW/HW Units to Segments and the SW Components, SW Modules and the Databases to SW Units. Also described are, e. g., requirements needed for the individual segment integrations and which combinations are possible or necessary.
On the other hand, the integration instructions for all integration steps are described, as e. g.
The subproduct Integration Plan.Integration Instructions (for System, Segment, SW) is completely covered .
- organizational requirements
- allocation of roles
- parts of the development environment and target computer
- assessment environment
- available software
SD3.3 - Definition of Requirements for the Functionality
The conditions and actions of a function are represented in the form of rules and of depending actions.
The subproduct Technical Requirements.Overall Function of Element is covered with regard to the difference between cases in the functions.
- not applicable -
/DIN 66241, 1978/ DIN 66241: Entscheidungstabellentechnik für den Informationsaustausch
/Elben, 1973/ Entscheidungstabellentechnik - Logik, Methodik und Programmierung
/Strunz, 1977/ Entscheidungstabellentechnik: Grundlagen und Anwendungsmöglichkeiten bei der Gestaltung rechnergestützter Informationssysteme
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster