Fact Oriented Modeling represents a data modeling approach that places a stronger emphasis on business-centric considerations as opposed to more technically-oriented methodologies. This approach serves as a vital bridge connecting the realms of business and IT.
Within modern data architectures, the framework laid out by Ronald Damhof featuring four quadrants highlights the substantial role of Fact Models in one of these quarters. Its effectiveness is underscored by its successful implementation within prominent institutions, including the Dutch National Bank, the Tax Department, and most recently, the Department of Justice and Safety in the Netherlands. Fact Oriented Modeling offers unwavering support for the vertical data architecture, encompassing the full spectrum of data elements, from legal frameworks, regulations, and procedures, all the way down to the precise definitions and their practical implementations in databases.
The Amsterdam, Rotterdam and Utrecht Universities of Applied Sciences have received a SPRONG grant from Regieorgaan-SIA, with which they - together with 24 partners from the field - can build an infrastructure for a powerful research group. A group that is regionally and nationally recognised as the centre for practice-based research in the field of Responsible Applied AI.
Casetalk is part of the curriculum at several universities, high schools and in secondary education. Students learn the basics of FCO-IM using CaseTalk and often the final assignment is to make a model of an existing organization of their choice.
Ever wondered where your entities came from? Entities may exist in your source code, databases, business glossaries, and in your data models themselves?
The Ensemble Logical Model (ELM) is an enterprise-wide business model which, in an agile way, maps the business concepts within a given organization into an agile and adaptable model. ... The Ensemble Logical model is a backbone model containing the Core Business Concepts and the way these are related. The high level modeling of concepts in this approach is in need for a trickle down approach which further integrates the communication and their examples. FCO-IM is an excellent candidate for that. Previously we showed the icons which depict concept types such as Person, Location, Event, etc.
The solid modeling method FCO-IM is great for bottom-up modeling, where every little detail is communicated and registered.
And yet, sometimes, we also need some support for top-down modeling. This would allow easy scoping while ignoring details that are needed at the end of the analysis. This high level scoping and registering of concepts and the ability to nest them in containers, is of great help in early stages of modeling and for high level information model views.
With CaseTalk version 12 we add the support for that. Below is a preview of a simple diagram mixing both top-down and bottom-up in a single model and diagram.
The Ensemble Logical Model (ELM) is an enterprise-wide business model which, in an agile way, maps the business concepts within a given organization into an agile and adaptable model. ... The Ensemble Logical model is a backbone model containing the Core Business Concepts and the way these are related. The high level modeling of concepts in this approach is in need for a trickle down approach which further integrates the communication and their examples. FCO-IM is an excellent candidate for that. ELM has a number of artifacts, the first is the so called Core Business Concept List. With the new concepts in CaseTalk it has become very easy to enter these:
Temporal modeling is a hot topic in data warehouse and BI environments. The data vault approach or anchor modeling are an attempt to make those environments more manageable. From the information modeling perspective however, these are mostly technical in nature. Though the information model could capture those technical requirements, it would be an information model with an implementation in mind, and not simply capture the business communication. We would be modeling the data warehouse implementation itself and not the way the business communicates about their data.
This is a follow up to the initial article to be found here.