2 ай бұрын
4 ай бұрын
6 ай бұрын
9 ай бұрын
9 ай бұрын
Жыл бұрын
Пікірлер
@ramano522 17 күн бұрын
Great explanation thank you.
@BlueRidgeValues 3 ай бұрын
disappointing . The idea that a conceptual is business centric and logical is specific to an individual use case contradicts 40 years of concepts from the folks that developed this discipline (Codd, Date, etc.) I guess they're pushing their agenda for their software. Feel free to google the difference between a conceptual and logical model -- you'll get a different answer.
@Graham_Wideman 4 ай бұрын
Wow -- it would be difficult to make a more unhelpful video. Diagrams to illustrate the concepts don't show up unti 4:10, and even then they are unrelated to each other and hence fail to illustrate the contrast between conceptual and logical, other than different style of graphics.
@nathnaeltesfaye4530 4 ай бұрын
A great explanation but I think it lacks an example. Some kind of illustration would more help full
@Neomadra 5 ай бұрын
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?
@DrJoySmithMaxwell 5 ай бұрын
please no background sound; it's easier to understand without it. Thank you
@GC-qe8vc 5 ай бұрын
So in this model, a Sales Order Row can contain many Products? That's unusual...
@aqssee 7 ай бұрын
stop using background music
@aqssee 7 ай бұрын
hate the background music
@BeshrSabbagh 8 ай бұрын
Your content is good. However, I dont prefer background music during the entire video (just a suggestion) 😊
@udayshankarchejerla9738 3 ай бұрын
I totally agree. Its distracting.
@juanc.alcazar7507 8 ай бұрын
👍
@srem1971 9 ай бұрын
Very well explained. Thank you!
@rupanag 9 ай бұрын
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 9 ай бұрын
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
@mehdee2 10 ай бұрын
Thanks for the video The music in the background is however too loud in my opinion and is negatively affecting the quality
@ChouatenYann 10 ай бұрын
Good video, will recommend👍
@emanno3man924 11 ай бұрын
Thanks🥺💗💗💗💗💗💗💗💗💗💗💗💗💗💗
@Milhouse77BS 11 ай бұрын
Nice overview.
@edwinmoore72 Жыл бұрын
Promo*SM
@2happyknight Жыл бұрын
Thank you, very clear and useful explanation
@anttipikkusaari4855 3 жыл бұрын
When it comes to Business - Data dialogue, this webinar is an absolute gem. The dialogue is not only about comms but, in fact, how data capabilities are to be built overall. Concept design is foundational to pretty much everything else.