Almost every session I'm in, explaining the power of Fact Modeling, there are questions on how to deal with different departments having an entity called "Customer" while they all mean something else, or use a different identification for it. This little article will show a possible verbalization for this issue.
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 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.
(A follow up article may be found here.)
July 2018
With the recent rush for GDPR compliance, we wanted to show you how simple the extension of new data model requirements can be in CaseTalk. It's a simple two-step procedure to mark all elements sensitive to privacy violations as such. But first, the definition of GDPR:
The General Data Protection Regulation (GDPR) (EU) 2016/679 is a regulation in EU law on data protection and privacy for all individuals within the European Union (EU) and the European Economic Area (EEA). It also addresses the export of personal data outside the EU and EEA areas. The GDPR aims primarily to give control to citizens and residents over their personal data and to simplify the regulatory environment for international business by unifying the regulation within the EU.
Superseding the Data Protection Directive 95/46/EC, the regulation contains provisions and requirements pertaining to the processing of personally identifiable information of individuals (formally called data subjects in the GDPR) inside the European Union, and applies to all enterprises, regardless of location, that are doing business with the European Economic Area. Business processes that handle personal data must be built with data protection by design and by default, ... [source: wikipedia]
Apr 2018
After having FCO-IM described on the English Wikipedia pages, we felt the need to also present this Dutch product on the Dutch Wikipedia pages. Please feel free to add your contributions to it.
In case you use Wikipedia and would like it to continue offering content, please consider making a small donation.
Want to learn how language captures more knowledge into your data models? Join us at DMZ in October. #dmzone https://t.co/57lOaEjqHd pic.twitter.com/G7vPooSbmx
— CaseTalk (@casetalk_dev) September 15, 2017
The new book on FCO-IM shown at #DMZone in Hamburg pic.twitter.com/fV48LnDLso
— CaseTalk (@casetalk_dev) September 28, 2015
Monday we'll be at #DMzone in Chapel Hill. pic.twitter.com/aouz4HRygs
— CaseTalk (@casetalk_dev) September 30, 2015