Software Components Should Have One Responsibility Only
Software components should have 1 responsibility & 1 reason to change, not like Swiss-army knife which does many tasks. Example: Employee class modified to follow SRP.
Every software component should have one and one responsibility only Software component can be class, method or module Example, a swiss-army knife is a multipurpose tool that violates the single responsibility principle of software development, instead a knife is a good example that follows Single responsibility (as it can only be used for cutting unlike the Swiss-army knife that can be used for cutting, opening can, as a master key, scissors,etc) Since the change is constant be it in the real world or in software development, the definition of the Single Responsibility Principle also changes...