Jump to content

User:SukuDan/sandbox

From Wikipedia, the free encyclopedia

Data Product

[edit]

Definition:

[edit]

A Data Product is a curated and trustworthy dataset or a combination of datasets, its lineage is traceable to the primitive sources, such as systems of record or other Digital Data producers.

It is de-coupled from the source or producer and owned by a 'Data Product Owner' responsible for clearly defined Schema and Metadata management. It could be enriched with reference data, designed to meet specific business needs or analytical objectives.

It can be consumed by any authorised user and implements appropriate user access rights governance frameworks; for demonstrated compliance to statutory Requirements.

This concept emphasizes treating data as a product, ensuring it is managed, maintained, and delivered with a service focus on timeliness, quality, usability, and trustworthy value creation.

Key Characteristics of a Data Product:[1]

[edit]

Purpose-Driven: Developed to address operational needs, business questions, analytical requirements and data archives.

Curated and Enriched: Involves the integration of data from multiple sources, including systems of record and reference data, to provide comprehensive insights.

Managed Lifecycle: Subject to continuous management, including updates, quality assurance, and user feedback incorporation.

User-Centric Design: De-Coupled and Structured to be easily discoverable, accessible and interpretable by end-users, facilitating informed decision-making.

Ownership for Governance: Data Products have an Identified "Data Product Owner" who owns the actions related to specifying the Schema, and Quality Parameters for any source to add its data to the Product.

User access rights governance frameworks: Access to Data Products are managed through appropriate access rights framework that implement Security Policies for Access and demonstrate compliance to statutory requirements and Organisational Policies for ensuring quality of data.

Examples of Data Products:

[edit]
  • Trustworthy stream of data: used for analytics and or for integration between systems
  • Dashboards and Reports: Visual representations of key performance indicators (KPIs) derived from various data sources.
  • Recommendation Engines: Systems that analyze user behavior and preferences to suggest products or services.
  • Predictive Models: Analytical tools that forecast future trends based on historical data.
  • Information Archives: Storage of Information for longer term analytical requirements.

Academic Perspectives:

[edit]

The concept of data products has been explored in academic literature. For instance, Hasan and Legner (2023) define data products as “a managed artifact that satisfies recurring information needs and creates value through transforming and packaging relevant data elements into consumable form.” [2]

Additionally Inês Araújo Machado, Carlos Costa, Maribel Yasmina Santos, in their paper presented at International Conference on Enterprise Information Systems / ProjMAN - International Conference on Project MANagement / HCist - International Conference on Health and Social Care Information Systems and Technologies 2021, talk about the Data Product in the chapter 3.1 Features of the Data Mesh.[1]

Significance In Data Management:

[edit]

Adopting a data product approach aligns with modern data management strategies, such as data mesh, which advocates for decentralized data ownership and treating data as a product to improve scalability and agility.

  • Capability to Create a Digital Twin: Organizational data inherently outlives applications, which undergo periodic upgrades, replacements, or migrations as technology evolves. In a data-centric approach, Data Products act as persistent Digital Twins by extracting and holding data from the System of Record (SoR). These Digital Twins ensure that critical data remains accessible and usable beyond the lifecycle of the application that originally generated it.
  • Benefits from De-coupling sources from consumers: By decoupling data from applications, organizations eliminate the disruptions and inefficiencies caused by frequent changes in application landscapes. Instead, new applications can seamlessly utilize the Digital Twin, fostering long-term data integrity and reducing the organizational strain associated with application-centric approaches where data often gets siloed or fragmented as applications come and go.
  • Essential Component of Event-Based Architecture: In an event-based architecture, Data Products play a crucial role in analyzing Business Events that occur within the services of Value Chain Functions. Each event represents a moment in the business process, capturing key details about its role in managing the value stream. By creating Data Products from these events, organizations can extract rich insights—beyond the immediate operational context—into patterns, trends, and anomalies. These insights provide a deeper understanding of the event’s impact on the overall business process, enabling better decision-making, performance optimization, and strategic planning. Furthermore, by decoupling the data from the event’s source application, these Data Products become reusable assets, supporting downstream analytics, AI models, and compliance reporting, ensuring a resilient and insightful approach to managing value streams.
  • Trustworthy Embedded Quality: Trustworthiness and embedded quality are essential characteristics of Data Products. These attributes ensure that data serves as a reliable foundation for analytical and AI engines, driving accurate insights and better business outcomes. By meeting statutory requirements and fostering confidence, trustworthy data becomes a cornerstone for organizational success and compliance.
  • Consumer-Centricity: Like any product, a data product prioritizes the end-user experience, ensuring ease of access, clarity, and relevance.
  • Automated Governance: Data products usually leverage automated governance tools to enforce policies, ensure compliance, and maintain data integrity without manual intervention.
  • Lifecycle Management: Data products are not static; they evolve through a managed lifecycle that includes: - Versioning to track changes, Retirement of outdated or irrelevant products. Feedback loops to incorporate user input and adapt to new requirements.
  • Business Value Alignment: A data product is purpose-driven, directly linked to Operational needs, business objectives or problem solving, making it possible to measure value delivered.
  • Built for Analytics and Action: Data products can be crafted to be directly usable for Analytical purposes (e.g., dashboards, machine learning models), Operational actions (e.g., triggering workflows or notifications) and making predictions.
  • Role in Future Ready Architectures: Data products are a foundational element in future ready Enterprise Architecture placing a Data Mesh as the central nervous system of the Enterprise.
  • Data Fabric: Serving as building blocks in an interconnected data ecosystem and can be woven from multiple data products.
  • Enables Collaborative Autonomy: Data Product-based Streams empower autonomous teams to operate independently within their own application and DevOps environments while seamlessly collaborating across business lines, business units, or other organizational domains. This approach allows data producers to retain control over their processes while sharing data in a standardized and accessible manner. By bridging the gap between autonomous teams, Data Product Streams enable a paradigm of collaborative autonomy, fostering interconnectedness without compromising individual team independence. This dynamic enhances efficiency, innovation, and adaptability across the organization.

References:

[edit]

Data Mesh: Concepts and Principles of a Paradigm Shift in Data Architectures

“Data Product Canvas: A Visual Inquiry Tool Supporting Data Product Design” by M. Redwan Hasan and Christine Legner (2023)[2]

This paper introduces the Data Product Canvas, a tool designed to assist cross-functional teams in understanding, designing, and analyzing data products, thereby fostering a comprehensive product perspective on data.

Springer Link[2]

“Decoding Data Products through the Lens of Work System Theory” by M. Redwan Hasan and Christine Legner (2023)[3]

This research examines how data products transform organizational data management practices, utilizing Work System Theory to identify three types of data products and their implications for enterprise data handling.

ResearchGate[3]

“Understanding Data Products: Motivations, Definition, and Categories” by M. Redwan Hasan and Christine Legner (2023)[4]

This study harmonizes the understanding of data products by identifying their characteristics and exploring the motivations behind their development, contributing to the discourse on scaling data and analytics in enterprises.

AIS Electronic Library (AISeL)[4]

“Designing and Managing Data Products” by EDM Council (2023)[5]

This webinar and its accompanying materials discuss the distinction between data products and data assets, emphasizing the organizational shift needed to prioritize data’s value.

EDM Council Webinar[5]

“What Is Data as a Product (DaaP)?” by IBM (2022)[6]

IBM’s article delves into the concept of treating data as a product, aligning with the principles of data mesh and emphasizing the need for self-service tools and stakeholder alignment.

IBM Topics[6]

“Data Mesh: Delivering Data-Driven Value at Scale” by Zhamak Dehghani (2022)[7]

This seminal book introduces the concept of data mesh, emphasizing the treatment of data as a product.

O’Reilly Media[7]

“Revolutionizing Insights: A Deep Dive into Data Product Architecture” by Scribble Data (2021)[8]

This article explores the components and design considerations of data products, providing insights into their role within modern data architectures.

Scribble Data Blog[8]

“Defining Data Products & Their Role in Data Mesh Architecture” by data.world (2021)[9]

This piece discusses the significance of data products in the context of data mesh, highlighting their importance in scalable data governance.

data.world Blog[9]

“Data Mesh Principles and Logical Architecture” by Zhamak Dehghani (2019)[10]

In this article, Dehghani elaborates on the principles of data mesh, detailing how data products serve as the architectural quantum in a decentralized data architecture.

Martin Fowler’s Blog[10]

“Data Management Body of Knowledge (DMBOK)” by DAMA International (2017)[11]

While not explicitly defining “Data Product,” this comprehensive guide covers related concepts such as data governance, data quality, and data lifecycle management.

DAMA International[11]

  1. ^ a b 1. Machado Inês 2. Carlos 3. Maribel Yasmina, 1, Araújo 2.Costa 3.Santos (2022). "Data Mesh: Concepts and Principles of a Paradigm Shift in Data Architectures,International Conference on ENTERprise Information Systems / ProjMAN - International Conference on Project MANagement / HCist - International Conference on Health and Social Care Information Systems and Technologies 2021. 196: 263–271". https://www.sciencedirect.com/journal/procedia-computer-science. 196: 263–271. {{cite journal}}: External link in |journal= (help)CS1 maint: multiple names: authors list (link) CS1 maint: numeric names: authors list (link)
  2. ^ a b c Hasan, M. Redwan; Legner, Christine (2023). Gerber, Aurona; Baskerville, Richard (eds.). "Data Product Canvas: A Visual Inquiry Tool Supporting Data Product Design". Design Science Research for a New Society: Society 5.0. Cham: Springer Nature Switzerland: 191–205. doi:10.1007/978-3-031-32808-4_12. ISBN 978-3-031-32808-4.
  3. ^ a b https://www.researchgate.net/publication/376353771_Decoding_Data_Products_through_the_Lens_of_Work_System_Theory. {{cite journal}}: Cite journal requires |journal= (help); Missing or empty |title= (help)
  4. ^ a b Hasan, M Redwan; Legner, Christine (2023-05-11). "UNDERSTANDING DATA PRODUCTS: MOTIVATIONS, DEFINITION, AND CATEGORIES". ECIS 2023 Research Papers.
  5. ^ a b "Designing and Managing Data Products – EDM Council". edmcouncil.org. Retrieved 2024-12-11.
  6. ^ a b "What Is Data as a Product (DaaP)? | IBM". www.ibm.com. 2024-02-21. Retrieved 2024-12-11.
  7. ^ a b "Data Mesh[Book]". www.oreilly.com. Retrieved 2024-12-11.
  8. ^ a b admin (2023-08-17). "Revolutionizing Insights: A Deep Dive into Data Product Architecture". Scribble Data. Retrieved 2024-12-11.
  9. ^ a b "Defining Data Products & Their Role in Data Mesh Architecture". data.world. Retrieved 2024-12-11.
  10. ^ a b "Data Mesh Principles and Logical Architecture". martinfowler.com. Retrieved 2024-12-11.
  11. ^ a b "DMBoK - Data Management Body of Knowledge". DAMA. Retrieved 2024-12-11.