Really good videos! Much needed.

Simple & Crisp explanation buddy, summed up at the end with very decent example, thanks a lot, Keep creating the content in similar way

@thecodemate7048

2 жыл бұрын

Glad you liked it

Please continue this series sir

why is the relationship b/w Order and OrderDetails an aggregation and not composition as when the order is destroyed order details will be destroyed too.

Very nice video. It really helps me to understand all basics.🙏. Thanks a lot !!!

@thecodemate7048

3 жыл бұрын

I am glad that it helped you.

In the Car - Engine composition example, should the relation be such that Car cannot exist without Engine i.e A can't exist without B?

At 6:24, Bi-directional, if city can call state, shouldn't City class should have getState() method?

Well Explanation, Great job sir.

@thecodemate7048

3 жыл бұрын

Glad you liked it .

@code Mate In the above overall order_placed diagram. Since order_details can't exist without order. I think it should be ideally composition instead of Aggregation

Nice explanation, Thank You!

@thecodemate7048

3 жыл бұрын

Glad you liked it

Why OrderDetails is being modelled as a seperate entity , should'nt it be a value object with all its fields inlined as part of Order itself ?

Order detail can exist without order? Shouldn't that be composition?

@vishnuthuletiya3199

2 ай бұрын

yes it should be composition

Shouldn't the arrow be from Payment to Order, as Payment is dependent on Order entity ?

Hi, thank you for your explanation. What is the difference between unidirectional association and aggregation? Can they be used interchangeably?

@nakulsuresh6476

2 жыл бұрын

Also, can there be an inheritance and dependency relationship between 2 entities?

Please share platform used for drawing class diagram

Shouldn't the Order and OrderDetails be a composition relationship?

@Isoldier333

3 жыл бұрын

I came down in the comments to point out the same mistake. How can an order class have multiple order details? makes no sense. Both order and orderdetails are composition class.

@abhishekrana9626

3 жыл бұрын

yes had the same doubt, saw the first comment is this only

@omkarjadhav6291

2 жыл бұрын

i was searching for this comment

@t-distributedkid3825

Жыл бұрын

Same doubt

can you please add more topic for the system design begginers to advance

7:08 for unidirectional, banks have customers, but customer may have bank or may not have bank, I 'm confused

amazing work

@thecodemate7048

3 жыл бұрын

Thanks for the visit

Well explained.

@thecodemate7048

3 жыл бұрын

Thanks Nitin

What's the difference between association and dependency??

I think in Aggregation and composition we should say it is not an arrow, it is an diamond arrow

Nice and waiting SOLID principles

@thecodemate7048

3 жыл бұрын

Thanks Ganesh, I am working on the same, Soon it will be available.

At the last class diagram, is it possible that one item can have multiple orderdetails or something is wrong over there.??

@thecodemate7048

3 жыл бұрын

Hi Prakash, one item can associated with multiple orders.

@amarlearning

3 жыл бұрын

@@thecodemate7048 True. But order details can also have multiple items? Please correct me If I am wrong.

@thecodemate7048

3 жыл бұрын

Yes you are correct, example I took is just for understanding.

@rajeshdansena

3 жыл бұрын

My understanding is : one item can be part of many orderDetail and one orderDetail can have many items. So, this says Item and OrderDetail has many-to-many relationship and this should be Uni-Directional Association relation as OrderDetail can have listOfItem but item should not have OrderDetail. @@thecodemate7048 thoughts???

So in aggregation example, is it only -"Customers can exist without bank" or can "Bank also exist without customer" ?

@thecodemate7048

3 жыл бұрын

It depends on the requirement for example what is use of bank without customer.

I don't know why you are not passing the age param in the setAge method.

@thecodemate7048

3 жыл бұрын

Thanks Prakash for highlighting, it's a typo, it's a normal getter and setter, so yes age should be a param for the method.

I think order and orderdetails should be in composition relationship rather than a aggregation since order details cannot exist without order and order details will change based on order. Only if there is a thing as "empty order" can order details and order be in aggregation which is not thr case i guess.. Pls respond

Is there any website where can i practice ooad principles?

@thecodemate7048

2 жыл бұрын

I am not sure but best way to practice is to share your implementation ideas with your colleagues and seek the feedback.

awesome why I am not seeing more videos from you Boss?

@thecodemate7048

Жыл бұрын

Sorry havent seen your comment before, working on different project which is kind of opensource.

Please share the github link of the slides which you are explaining, so that we can revise them later. Thanks!

@thecodemate7048

2 жыл бұрын

Hey Dileep, at this moment ppt havent put on github. will update you once its available.

One doubt on last diagram 1. Why there is no composition between customer class and order class instead association. Because order can not exist without customer, if order is created then it will be by customer only ?

Class diagram will write for entire project ? Class diagram for every class need to draw? Or class diagram write for module ?

@thecodemate7048

3 жыл бұрын

You don't need to draw it for whole project. Having it for core entities should work.

@subbumotepalli

3 жыл бұрын

@@thecodemate7048 Thank you.whose responsibility to draw class diagram

@thecodemate7048

3 жыл бұрын

Candidate who is giving the interview.

please provide documented notes

@thecodemate7048

Жыл бұрын

I think its already there in the video. I havent documented anything apart from the basic slides.

@thecodemate7048

Жыл бұрын

Sorry havent seen your comment. Thanks for the response.