Whats the difference between Statestep and decision table tools?
You can use Statestep merely as a decision table tool. Used in this way, Statestep has a unique interface that allows you to easily create new rules for uncovered cases even if you’re trying to manage millions or billions of combinations – whereas a regular decision table tool may start to become unwieldy with only hundreds of combinations. Also, Statestep allows for impossible cases to be dealt with much more efficiently than the dummy rule strategy of decision table tools. Further, you’re not even limited to a tabular representation of rule conditions: you can use formulas wherever it would be inefficient or awkward to use only a table. However, Statestep can also be used to create a finite state machine model as a way of describing system behaviour; indeed this is what it’s designed for. And it’s also possible to use the constraint table as a standalone element to explore logical relationships, find contradictions, etc.
Related Questions
- What is the difference between "Access of data within a table type" and "Use of a table types value in a FROM clause"?
- Whats the difference between QUSRTOOL and the TAA Productivity Tools product?
- Whats the difference between QUSRTOOL and the TAA Productivity Tools product?
- Whats the difference between Statestep and decision table tools?
- WHAT IS DIFFERENCE BETWEEN TABLE LEVEL AND ROW LEVEL TRIGGERS?
- WHAT IS DIFFERENCE BETWEEN TABLE LEVEL AND ROW LEVEL TRIGGERS?
