Spike: The decision table layout is a crucial part for understandability of the tables

[pinussilvestrus]

What should we do?

Investigate the following hypothesis: "The decision table layout is a crucial part for understandability of the tables", cf. DMN Hypothesis Board

Why should we do it?

After we investigated possible ways to view and edit deeper decision logic inside DRDs (cf. #451), we want to have a look at the decision tables now. Decoupled from the current layout we want to investigate different approaches for layouting so that the user can easily understand the logic of a table.

Summary

• Prototype (Layout)
• Prototype (Navigation)
• Summary

Resources

• DMN Hypothesis Board
• Hypothesis 3 Summary Docs
• dmn-prototypes

[pinussilvestrus]

We start to find ideas for the decision table header layout, cf. Sketches

[pinussilvestrus]

We came up with the following layout approach

Next Step: We will create a first prototype on how to navigate between DRD and Decision Tables with this new layout

[pinussilvestrus]

We came up with the following navigation demo (changes to be made)

[pinussilvestrus]

User Tests

[pinussilvestrus]

User Test 6th of March (1)

[pinussilvestrus]

User Test 6th of March (2)

[pinussilvestrus]

We going to test the demo in the next weeks again. Generally, we know what we want to achieve with the split screen and the basic table layout.