How to read Conceptual Data Models - Ellie.ai

Поделиться
HTML-код
  • Опубликовано: 5 апр 2023
  • Conceptual Data Models help you create a high-level representation of your company in terms of data. Each model acts as a slice of your business reality and when models are linked together, create a visual, easy-to-grasp common map of meaning.
    In this video, Ellie.ai's CPO, Juha Korpela, explains how to read Conceptual Data Models. It is a must-watch if you're getting familiar with data modeling.
    Interested in applying Conceptual Data Modeling across your organization? Take advantage of Ellie.ai's 30-day trial and see how you can take advantage of business-focused data modeling!
    Get your trial here - www.ellie.ai/trial-page
  • НаукаНаука

Комментарии • 6

  • @Neomadra
    @Neomadra 10 дней назад

    Isn't the sales order row redundant? That's an instance of the sales order entity and not really a conceptual entity, right? Or why do we have a sales order row entity, but not a address row or product row for example?

  • @mehdee2
    @mehdee2 5 месяцев назад

    Thanks for the video
    The music in the background is however too loud in my opinion and is negatively affecting the quality

  • @GC-qe8vc
    @GC-qe8vc Месяц назад

    So in this model, a Sales Order Row can contain many Products? That's unusual...

  • @rupanag
    @rupanag 4 месяца назад

    I have a question. In conceptual model, can two entities be associated with both direct and indirect relationship?
    e.g. engineer inspects item. This inspection generates inspection report.
    So entity 'engineer ' can have a relationship 'inspects' with entity 'item'. Also entity 'engineer 'can have a relation 'conducts' with entity 'item inspection'. Entity 'item' will have a relationship 'undergoes' with entity 'item inspection'.
    Is it valid?

    • @ellietechnologies
      @ellietechnologies  4 месяца назад +1

      Hi, our in-house modeling expert's response:
      "A valid model would be something like this (image link added).
      We don't need a direct relationship between 'Item' and 'Engineer' since 'Item' is not dependent on 'Engineer' (and vice versa). One 'Item Inspection' relates to exactly one 'Engineer' and exactly one 'Item'. So one instance of 'Item Inspection' tells the story needed to show that an 'Engineer' inspects an 'Item'.
      drive.google.com/file/d/1UXZUOCSPp3O_DsGJqtKzHhYv8GGgw2-N/view

  • @aqssee
    @aqssee 3 месяца назад

    hate the background music