The Object-Oriented (OO) paradigm is a software development philosophy that models a system as a collection of interacting objects. Each object represents a real-world entity or concept and combines both data and the operations that manipulate that data. This approach aims to improve software quality by promoting modularity, reusability, flexibility, and maintainability. Object-Oriented Analysis and Design (OOAD) emphasizes understanding the problem domain through objects, classes, relationships, inheritance, and polymorphism rather than focusing only on functions or processes. The central philosophy is that software should closely resemble the real world, making it easier to understand, design, and modify. The OO paradigm is built upon four fundamental principles: abstraction, encapsulation, inheritance, and polymorphism. Abstraction allows developers to focus on the essential features of an object while ignoring unnecessary details. Encapsulation binds data and methods into a single unit, ensuring that an object's internal state can only be modified through well-defined interfaces. Inheritance enables new classes to acquire the characteristics and behaviors of existing classes, encouraging code reuse. Polymorphism allows objects of different classes to respond differently to the same message, increasing flexibility and extensibility. In contrast, the classical Structured Analysis and Design (SAD) approach is function-oriented. It decomposes a system into processes and functions, using tools such as Data Flow Diagrams (DFDs), Structure Charts, and Entity-Relationship Diagrams (ERDs). Data and functions are treated as separate entities. The primary emphasis is on the sequence of operations and the flow of