Design Goals for TAMI Retrospective User Interface

Competence Test

[test case] Explain why a statement (from the annotated transaction log), for e.g. "service-refused-event is not-compliant-with MITprivacy-policy" using the corresponding justification trace

Audience:

Input data:

Expected result:

[test case] Show all antecedent-events (from transaction log) for service-refused-event (from transaction log)?

Audience:

Input data:

Expected result:

[test case] Type/load a transaction log and some policies, test if the transaction log is compliant with the policies. Integrate appropriate viewers to show the data, policy, and justification to the compliance test.

Audience:

Input data:

Expected result:

Functions

Let users load/edit transaction log, and policy
Let users call reasoner and see the reasoning results
Button to call justification viewer and log viewer to see the justifications and logs

Prototypes

Dependencies

Functions

Show RDF data, dumped by scheme engine or something else, explaining how the final conclusion is derived
Somehow users are expecting a much smaller subset of transaction log used in the justification
Template for showing justification trace (the graph)
Template for showing nodes in justification trace

Dependencies

[data] Simple conclusion data, e.g. "event1 is-not-compliant-with policyX"
[data] Justification dump. Need scheme to generate it as the input for justification viewer
[link] Log viewer

Functions

Dependencies

Functions

Dependenies

future work'

[MIT] Use Tabulator as a basic implementation for log viewer and justification viewer
[RPI] Develop advance English based implementation for log viewer and justification viewer