An object is a software module in object-oriented design (OOD). An object class, which is made up of two components—structural properties and behavioural methods—defines similar objects. The Unified Modeling Language (UML) class diagram can display an object class. If you think of an object class as the fundamental unit of software, the design of the software structure may be used to identify two different sorts of interactions between a group of objects. has-a or composition relationship and is-a or inheritance relationship between object classes. In the meantime, it is possible to think of the software behaviour design as determining three different kinds of behavioural dynamics among a number of object classes, as follows: Activities of the objects, or procedural or parallel behaviour The object-object interactions sequences Transitions in an entity's state or how events affect an object over time Answer the following questions in light of the online bookshop's website: Give an example of a has-a or composition relationship as well as an example of an is-a relationship. What UML diagrams are suitable for displaying the relationships? Give an example of the behavioural dynamics of each sort of item (i.e., the activity, the sequence, and the state transitions). Which three behavioural dynamics can be presented using UML diagrams?