Abstract: Like any other modelling or development environment, there exist several modelling style choices in arriving at a Fact Based Model (FBM) schema. What is interesting is that choosing different modelling styles in modelling the same semantics directly affects the degree of programming code developmental efforts.
A Use Case portraying an actual situation is shown where moving from a commonly used approach in modelling temporal based facts to a deeper structure of involved semantic relationships resulted in a marked difference in the reduction of SQL code development.
This paper also highlights the dangers of a possible gap and loss of knowledge between the human roles during the process of semantic transforms from an ORM/NIAM model FBM schema to SQL development. A lessons-learned summary lists some of the real-world compromises, and highlights danger areas using ‘traditional’ Fact Based Modelling practices during implementation.
Author: Baba Piprani, MetaGlobal Systems (Canada)