In the Netherlands, legal articles are readily available online, while IT systems play a pivotal role in the execution and enforcement of government policies. However, these two crucial domains often operate in isolation. When political shifts lead to policy changes, legal articles require updates. Yet, determining which IT systems require adjustments remains a challenge due to the lack of clear lineage, a concept known as vertical architecture.

Vertical architecture entails always knowing the reciprocal impact of your policies on systems and vice versa. It ensures transparency regarding why a system operates in a particular way and its underlying rationale.

Welcome to the world of CaseTalk, where facts come alive, and data storytelling takes center stage. In the realm of information modeling, it's easy to get lost in the elementary parts, but fear not! With CaseTalk's innovative features, you can effortlessly retrieve the essence of your data story with just a click of a button. Let's explore some of the remarkable features that empower you to craft captivating narratives like never before.

For the people who simply want a quick win and render a diagram, we've made available for free our own testing application. With this application scripts may be edited for Mermaid, PlantUML and GraphViz, and render the output instantly (provided the libraries are installed).

With all the devices put in place everywhere, and software and data engineers jumping on board with streaming data technology, there's one thing that small thing that is not looked at, and it baffles me: data integration and business verification.

Normalization is not always fun, and even in 1989 someone by the name of Marc Rettig tried to make it more fun and easy to absorb. He must have thought, "everybody loves puppies", let's make everybody love normalization by using puppies as an example. Naturally he was right, everybody loves puppies. :-P

Abstract Models are a technical choice to save effort in managing code and modeling effort. There's an advantage in re-use of elements, but also a disadvantage in the need for more rules, potentially more code, and harder to understand. The latter seems counter intuitive, but let this article explain using a simplified example of names.

Why Fact Oriented Modeling?

Fact Oriented Modeling is a data modeling approach which is more business oriented than other more technical oriented ways of working. Fact Oriented Modeling helps you close the gap between business and IT.

Modern data architectures work with the four quadrants of Ronald Damhof, in which one quarter is almost completely defined by Fact Models. It has been applied in the Dutch National Bank, the Tax Department, and now the Department of Justice and Safety in the Netherlands. It supports the vertical data architecture, being the data at rest, from law, regulations, procedures, down to the definitions and implementations in databases.

In general, the path to growth is to realize the business IT gap is real. Once this realization sets it, it is no longer just a new tool which will fix the problem.