Forum Discussion

powerbiexpert22's avatar
powerbiexpert22
Impactful Individual
1 year ago

data model peer review

- i need to peer review the data model created by developers, what factors i should consider while reviewing the data model ,        below is my understanding

- developers should be aware of the business process flow example , in case of CRM, Leads->Quotes-> Opportunities

- developers should be aware of right relationships betweeen tables, exmaple ( one to many, many to one etc)

- developers should follow best practices , example star schema etc

 

3 Replies

  • powerbiexpert22 

    Key factors to consider when peer-reviewing a data model:

    1. Ensure primary and foreign keys are set up correctly to maintain data integrity.
    2. Validate that relationships have the correct cardinality (one-to-many, many-to-one) and direction.
    3. Verify adherence to best practices like star schema (fact and dimension tables).
    4. Columns should have clear, meaningful names that align with business terminology.
    5. Confirm that unnecessary columns or tables are removed to minimize data load.

    These factors help ensure the model is robust, performant, and aligned with both business and technical requirements.

     

    💌 If this helped, a Kudos 👍 or Solution mark would be great! 🎉
    Cheers,
    Kedar
    Connect on LinkedIn

     

    • powerbiexpert22's avatar
      powerbiexpert22
      Impactful Individual

      Hi Kedar_Pande ,

      who (business or data engineering team) will tell developers which column should be used to join between two tables , example lead and opportunity tables can be joined by using opportunityid which is foreign key available in lead table). as per my understanding it should be someone from business side

      • Kedar_Pande's avatar
        Kedar_Pande
        Super User

        powerbiexpert22 

        Yes, you’re correct: identifying which columns should be used for joins typically requires input from the business side or data engineering team, as they have a deeper understanding of the data’s context and relationships.
        So, while developers handle the implementation, the decision about which columns to join usually rests with the business or data engineering teams.