OOPS Concept

 

Basic Concepts

1. What are the four main principles of Object-Oriented Programming (OOP)?

   • Encapsulation: Bundling the data (variables) and the methods (functions) that manipulate the data into a single unit, or class, and restricting access to some of the object's components.
   • Abstraction: Hiding the complex implementation details and showing only the essential features of the object.
   • Inheritance: Creating new classes (derived classes) from existing classes (base classes) to promote code reuse.
   • Polymorphism: The ability of different objects to respond in a unique way to the same message (method call). It can be achieved through method overriding (runtime polymorphism) or method overloading (compile-time polymorphism).

2. What is a class and an object in OOP?

   • Class: A blueprint or template for creating objects. It defines a datatype by bundling data and methods that work on the data into one single unit.
   • Object: An instance of a class. It is a concrete entity based on a class, with actual values assigned to the attributes defined by the class.

3. What is the difference between a class and a struct?

   • Class: A reference type that supports inheritance, can have methods and properties, and is allocated on the heap.
   • Struct: A value type that does not support inheritance, is typically used for small data structures, and is allocated on the stack.

Encapsulation

4. How do you achieve encapsulation in C#?

   • Encapsulation is achieved using access modifiers (private, protected, public, internal). Data members are kept private or protected, and public methods (getters and setters) are used to access and modify the data.

5. What is the difference between a property and a field in C#?

   • Field: A variable of any type that is declared directly in a class or struct.
   • Property: A member that provides a flexible mechanism to read, write, or compute the value of a private field. Properties can have get and set accessors.

Abstraction

6. What is abstraction and how do you implement it in C#?

   • Abstraction involves hiding the complex implementation details and showing only the necessary features. It is implemented using abstract classes and interfaces.

7. What is an abstract class and how is it different from an interface?

   • Abstract Class: A class that cannot be instantiated and can have both abstract methods (without implementation) and non-abstract methods (with implementation). It is used to represent a common base for related classes.
   • Interface: A completely abstract class that defines a contract with no implementation. Classes that implement an interface must provide an implementation for all its members.

Inheritance

8. What is inheritance and how is it implemented in C#?

   • Inheritance is a mechanism where one class (derived class) inherits the properties and methods of another class (base class). It is implemented using the : symbol in C#.

9. What is the difference between single inheritance and multiple inheritance?

   • Single Inheritance: A class inherits from only one base class.
   • Multiple Inheritance: A class can inherit from more than one base class. C# does not support multiple inheritance directly but can achieve it through interfaces.

Polymorphism

10. What is polymorphism and how is it achieved in C#?

    • Polymorphism allows methods to do different things based on the object it is acting upon. It is achieved through method overriding (runtime polymorphism) and method overloading (compile-time polymorphism).

11. What is the difference between method overloading and method overriding?

    • Method Overloading: Multiple methods with the same name but different signatures (parameters). It occurs at compile-time.
    • Method Overriding: A derived class has a definition for one of the methods of the base class. It is marked with the override keyword and occurs at runtime.

Advanced Concepts

12. What is the purpose of the virtual keyword in C#?

    • The virtual keyword is used to declare a method or property that can be overridden in a derived class.

13. What is the purpose of the override keyword in C#?

    • The override keyword is used to extend or modify the abstract or virtual implementation of an inherited method, property, indexer, or event.

14. What is an interface and how is it different from an abstract class?

    • An interface defines a contract that implementing classes must fulfill, with no implementation details. An abstract class can provide some implementation, and can have fields and constructors, which interfaces cannot.

15. What is the difference between is and as operators in C#?

    • is Operator: Checks if an object is compatible with a given type and returns a boolean.
    • as Operator: Tries to cast an object to a given type and returns null if the cast fails.

Design Patterns

16. Can you explain the Singleton pattern and its use case?

    • The Singleton pattern ensures that a class has only one instance and provides a global point of access to it. It is used in scenarios where a single instance of a class is required to coordinate actions across a system.

17. What is the Factory pattern?

    • The Factory pattern defines an interface for creating an object but lets subclasses alter the type of objects that will be created. It is used to create objects without specifying the exact class of object that will be created.

18. What is the Observer pattern?

    • The Observer pattern defines a one-to-many dependency between objects so that when one object changes state, all its dependents are notified and updated automatically. It is commonly used in event handling systems.

19. Class and Object

    • Class: A blueprint or template for creating objects. It defines properties and methods.
    • Object: An instance of a class, representing a specific entity with defined attributes and behaviors.

20. Encapsulation

    • The bundling of data (attributes) and methods (functions) that operate on the data into a single unit (class) and restricting access to some of the object's components. It is typically implemented using access modifiers (private, protected, public).

21. Abstraction

    • The process of hiding the complex implementation details and exposing only the necessary features of an object. It allows focusing on what an object does rather than how it does it.

22. Inheritance

    • A mechanism where a new class (derived or child class) inherits the properties and methods of an existing class (base or parent class). This promotes code reuse and establishes a hierarchical relationship between classes.

23. Polymorphism

    • The ability of different objects to respond in a unique way to the same message (method call). It can be achieved through:
      • Method Overloading (Compile-time Polymorphism): Multiple methods with the same name but different signatures (parameters).
      • Method Overriding (Runtime Polymorphism): A derived class provides a specific implementation of a method that is already defined in its base class.

24. Constructor and Destructor

    • Constructor: A special method called when an object is instantiated. It initializes the object's state.
    • Destructor: A method called when an object is destroyed. It cleans up resources used by the object.

25. Access Modifiers

    • Keywords that set the accessibility of classes, methods, and other members. Common access modifiers include:
      • Private: Accessible only within the class.
      • Protected: Accessible within the class and by derived class instances.
      • Public: Accessible from any other code.
      • Internal: Accessible within the same assembly.

26. Interface

    • A completely abstract class that defines a contract with no implementation. Classes that implement an interface must provide an implementation for all its members.

27. Abstract Class

    • A class that cannot be instantiated and may contain abstract methods (without implementation) as well as concrete methods (with implementation). It serves as a base class for other classes.

28. Static Members

    • Class members that belong to the class itself rather than any object instance. They are shared across all instances of the class.

29. Property

    • A member that provides a flexible mechanism to read, write, or compute the value of a private field. Properties can have get and set accessors.

30. Method

    • A function defined within a class that performs operations on the data members of the class.

31. Overloading

    • Defining multiple methods in the same scope, with the same name but different parameters (signatures).

32. Overriding

    • Providing a new implementation for a method in a derived class that is already defined in its base class. It is marked with the override keyword.

33. Virtual Methods

    • Methods that are declared in a base class using the virtual keyword and can be overridden in derived classes.

34. Abstract Methods

    • Methods that are declared in an abstract class without an implementation. They must be implemented in derived classes.

35. Delegates and Events

    • Delegate: A type-safe function pointer used to encapsulate a method reference.
    • Event: A way for a class to provide notifications to clients when something of interest occurs. It is typically used in combination with delegates.

36. Composition

    • A design principle where a class is composed of one or more objects from other classes, implying a has-a relationship.

37. Aggregation

    • A specialized form of association representing a whole-part relationship between an aggregate (whole) and a component part.

38. Association

    • A relationship between two objects, indicating that one object uses or interacts with another.

39. Dependency Injection

    • A design pattern used to implement IoC (Inversion of Control), allowing the creation of dependent objects outside of a class and providing those objects to the class.