Answer Posted / musheer

Static model is a time independent view of a system . however static modelling is supposed to detail what preferrably might happen instead of the numerous possibilities. that's why it is more rigid and cannot be changed. therefore, it is called static modelling . use case can be a part of both static and dynamic modelling depending on how it is designed. normally it is, a part of static modelling . it includes
class diagram
object diagram
component diagram
deployment diagram

.Dynamic Modeling
it is time dependent and more appropriately it shows what an object does essentially with many possibilities that may arise. it is flexible but its flexibility is limited to the design on the system.
it includes
use case
interaction
state chart
activity

Explain the use of Vtable and what are the various problems to override the functions?

906

---

Explain about multiple inheritance?

1018

---

Explain method overriding.

1024

---

What does it mean that a method or class is abstract?

930

---

Explain about overriding polymorphism?

1029

---

Difference between encapsulation and data hiding ?

861

---

What is overriding?

997

---

How to achieve data abstraction?

918

---

What are all the operators that cannot be overloaded?

933

---

Explain about inheritance hierarchies?

931

---

Explain the rationale behind object oriented concepts?

1210

---

What is the main advantage of using inheritance?

1029

---

Explain about encapsulation?

990

---

Explain what is polymorphism?

1035

---

Difference between class and an object?

939

---