Hi there Data Strategy Pro,
Heads up that today is the last day to enter our March Giveaway of Agile Data Warehouse Design by Lawrence Corr and Jim Stagnitto.
|
|
To enter, you must:
1. Be subscribed to this newsletter
2. Send the newsletter to at least one friend or colleague
You'll receive one giveaway entry per friend or colleague to whom you forward this newsletter.
Then email the Community Organizer to let her know this has been done. The winner will be selected at the end of the month. Cheers and happy modelstorming, you guys!
|
|
|
The small print: when you email the Community Organizer, you must include the email addresses of your friends / colleagues to whom you've forwarded the newsletter. They will be added to the mailing list as double opt-in. This means that before we can email them, they have to opt-in to receiving communications from Data Strategy Professionals. This way, we ensure no one receives any emails they consider to be spam.
|
|
Let's finish March strong, closing out our focus on Data Architecture and launching into Data Modeling.
Here are a few things learned this month:
- A primary objective of a Data Architect is to enable consistent data standardization and integration across the enterprise. The Data Architect bridges business strategy and technical execution. The Data Architect creates and maintains organizational knowledge about data and systems. They help identify opportunities for data usage, cost reduction, and risk mitigation. They implement and enforce semantics via common business vocabulary.
- The Zachman Framework is an enterprise architectural framework from 1980s. It shows what models should exist - this concept is called reification transformation and refers to the transformation of abstract ideas into concrete instances.
- The Enterprise Data Model (EDM) is a holistic, enterprise-level, implementation-independent conceptual or logical data model providing a common consistent view of data across the enterprise.
Cheers,
Nicole
Seeking a new job? Your Moment of Zen.
|
|
|
|
