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?
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?
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
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?
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?
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
Thanks for the video
The music in the background is however too loud in my opinion and is negatively affecting the quality
So in this model, a Sales Order Row can contain many Products? That's unusual...
hate the background music