#Single responsibility principle java software

This approach prevents the creation of God objects objects that know too much or do too much. The Single Responsibility Principle (SRP) is one of five design principles of the SOLID design framework for object-oriented software design. Annotations (2) Arrays & Lists (25) atomic (1) Binary Tree (8) Bit Algorithms (5) Caching (1) Class Loaders (2) Cloning (9) Code Coverage (5) Coding Interview (4) Collection (45) Core Java (239) Data Structure & Algorithms (85) DBMS (3) Design Patterns (23) Divide & Conquer (1) Dynamic programming (13) enum (10) Exception (19) Executor (2) Flipkart (1) Garbage Collection (14) GCD-LCM (1) Generics (1) Geometric (2) Goldman Sachs (1) Greedy (2) Hibernate (11) Idempotency (3) Immutability (2) Index (1) Interviewer (1) Java bugs (1) Java Hacks (18) Java IO (5) Java Networking (1) JDBC (2) jdk 1.7 (3) jdk 1.8 (1) JVM (17) Map Interface (19) Mathematical (1) Message Formatting (2) Multithreading (67) Must Do (1) Networking (1) Object Oriented Design problem (1) Object Oriented Programming (21) Probability (1) Puzzle (1) Queue (3) Reflection (1) Secure coding (5) Security (3) Semaphore (1) Serialization (26) SGM (10) Shutdown Hook (2) Software Testing (1) SOLID principles (6) SONAR Rules (2) Sorting & Searching (4) Spring (28) SQL (5) Stack (1) Struts 2. Single Responsibility Principle (SRP) is one of the most important object-oriented coding principle which, if followed religiously, can help you write a very good quality code. The single responsibility principle is founded on one of the basic, general ideas of object-oriented programming the so-called divide and conquer principle solving a problem by solving its multiple sub-problems.