The Versatile Geek

A design philosophy is OOP. Object Oriented Programming is what it stands for. In contrast to outdated procedural programming languages, object-oriented programming (OOP) employs a separate set of programming languages. In OOP, everything is categorised as self-sustaining "objects". As a result, you achieve re-usability using the four core concepts of object-oriented programming. Programmes are organised around objects and data rather than action and logic in the object-oriented programming (OOP) paradigm.    Let's use your "Leg" as an example to grasp the object orientation clearly. The class "Leg" is one. Left and right legs are objects of type Leg on your body. A series of electrical impulses supplied through your body parts (through an interface) are what manage or control their primary functions. As a result, the body part serves as an interface between your body and your legs. The Leg is a well-designed class. The attributes of the Leg are m

Why Using Factory “Creates objects without exposing the instantiation logic to the client. It refers to the newly created object through a common interface.” This is exactly Factory pattern. Software design principles represent a set of guidelines. These guidelines help us to create a good design. There are some characteristics of bad design, 1.      Hard to change: changes affect too many other part of the system. 2.      System breaks while changing. 3.      Hard to reuse. I am going to start with 3 tier architecture.   Basically we know in three tier architecture the UI code is in the client section, business layer is nothing but business classes which has the business validation and the data access layer does all the database operations. If we study these 3 sections most changes happening in business layer. Business rules change time by time. Client changes depend on user interface but it won’t be as much as business layer. Then data layer, compared to other lay