Table of Contents
Fetching ...

Automating Compliance in Government Organisations using eFLINT

Nina Verheijen

TL;DR

This work investigates creating a user-centered interface for an eFLINT-based prototype to automate normative compliance in government organisations. It combines qualitative interviews and thematic analysis to elicit requirements, then designs, implements, and tests a Dutch-language prototype using Framer, evaluated via cognitive walkthrough and usability testing. Findings indicate the prototype is a promising first step but needs improvements in feedback, editing/transparency, multi-user access, and a functional simulation to realize practical adoption. The study demonstrates a concrete path from requirements to a usable prototype and outlines concrete enhancements to bridge the gap between legal norms and automated compliance in public administration.

Abstract

Ensuring compliance of norms and policies when working on administrative law cases can be difficult to manage for government organisations. Automating this process could save a lot of time, effort and ensure compliance. Prior research resulted in a method to formalize sources of norms. These can be turned into executable specifications using the domain-specific language eFLINT, which can be used for automating compliance. However, the current interface of eFLINT prevents adaption by legal experts. The aim of this research was to bridge this gap by developing a prototype based on eFLINT, for automating compliance within government organisations. To get a better understanding of the needs and requirements of potential users, qualitative research was conducted. This consisted of semi-structured interviews to gather requirements, which were analyzed using a thematic analysis method. Based on the analyzed data, a design for the interface of the prototype was made. The final prototype was evaluated in a user end study which included a cognitive walkthrough and user testing. The prototype proved to be a good first step in the right direction with a lot of room for further development.

Automating Compliance in Government Organisations using eFLINT

TL;DR

This work investigates creating a user-centered interface for an eFLINT-based prototype to automate normative compliance in government organisations. It combines qualitative interviews and thematic analysis to elicit requirements, then designs, implements, and tests a Dutch-language prototype using Framer, evaluated via cognitive walkthrough and usability testing. Findings indicate the prototype is a promising first step but needs improvements in feedback, editing/transparency, multi-user access, and a functional simulation to realize practical adoption. The study demonstrates a concrete path from requirements to a usable prototype and outlines concrete enhancements to bridge the gap between legal norms and automated compliance in public administration.

Abstract

Ensuring compliance of norms and policies when working on administrative law cases can be difficult to manage for government organisations. Automating this process could save a lot of time, effort and ensure compliance. Prior research resulted in a method to formalize sources of norms. These can be turned into executable specifications using the domain-specific language eFLINT, which can be used for automating compliance. However, the current interface of eFLINT prevents adaption by legal experts. The aim of this research was to bridge this gap by developing a prototype based on eFLINT, for automating compliance within government organisations. To get a better understanding of the needs and requirements of potential users, qualitative research was conducted. This consisted of semi-structured interviews to gather requirements, which were analyzed using a thematic analysis method. Based on the analyzed data, a design for the interface of the prototype was made. The final prototype was evaluated in a user end study which included a cognitive walkthrough and user testing. The prototype proved to be a good first step in the right direction with a lot of room for further development.

Paper Structure

This paper contains 49 sections, 13 figures.

Figures (13)

  • Figure 1: Thematic map: Interface requirements
  • Figure 2: Home page.
  • Figure 3: New case page.
  • Figure 4: Case overview page.
  • Figure 5: Overview cases page.
  • ...and 8 more figures