Browse Definitions :
Definition

SOLID (software design principles)

Contributor(s): Matthew Haughn

SOLID is a mnemonic acronym for a set of design principles created for software development in object-oriented languages.

The principles in SOLID are intended to foster simpler, more robust and updatable code from software developers. Each letter in SOLID corresponds to a principle for development:

  • Single responsibility
  • Open/closed
  • Liskov substitution
  • Interface segregation
  • Dependency inversion

The Single responsibility principle, created by Robert C. Martin, states that a class should have one, and only one, reason to change. This principle ensures that any class should have only one function, to help ease updating and limit the possible complications by future changes. The principle can be applied to software components or microservices tools.

The Open/closed principle ensures that software entities be open to extension but closed for modification. Bertrand Meyer is mainly credited with the creation of this principle, which focuses on making the abilities of a class easy to enhance by extension but prevents possible complications that could be brought about by modifying the entity and affecting dependencies of other functions that rely on it.

The Liskov principle stipulates that objects of the same type be replaceable with others from this same category without altering function of the program. Created by Barabara Liskov, this principle ensures that more effective means of performing a task can be switched to without unduly affecting the program or requiring substantial code updates.

The Interface segregation principle stipulates that the application’s interfaces should always be kept smaller and separate from one another. This principle ensures that clients need only familiarize themselves with functionality of methods or interfaces that are used, so they can respectively be updated without one complicating the other. This separation made by layers of abstraction provides space to document functionality while avoiding the coupling of dependencies in code.

The Dependency inversion principle specifies a form of decoupling dependencies in code. In dependency inversion, the dependencies in high-level code that set policies are inverted to the low-level dependency modules. This separates the high-level code from the details of low-level modules.

While ideas for the SOLID principles were developed in 1995 by Robert C. Martin, co-author of the Agile Manifesto, the acronym was coined by Michael Feathers in the early 2000s as a way to remember the concepts. Other popular software development methodologies include Agile, KISS principle, GRASP (General Responsibility Assignment Software Principles) and the DRY principle.

This was last updated in October 2018

Continue Reading About SOLID (software design principles)

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

File Extensions and File Formats

Powered by:

SearchCompliance

  • compliance audit

    A compliance audit is a comprehensive review of an organization's adherence to regulatory guidelines.

  • regulatory compliance

    Regulatory compliance is an organization's adherence to laws, regulations, guidelines and specifications relevant to its business...

  • Whistleblower Protection Act

    The Whistleblower Protection Act of 1989 is a law that protects federal government employees in the United States from ...

SearchSecurity

  • brute force attack

    Brute force (also known as brute force cracking) is a trial and error method used by application programs to decode encrypted ...

  • spyware

    Spyware is software that is installed on a computing device without the user's knowledge. Spyware can be difficult to detect; ...

  • ATM black box attack

    An ATM black box attack, also referred to as jackpotting, is a type of banking-system crime in which the perpetrators bore holes ...

SearchHealthIT

SearchDisasterRecovery

  • business continuity and disaster recovery (BCDR)

    Business continuity and disaster recovery (BCDR) are closely related practices that describe an organization's preparation for ...

  • warm site

    A warm site is a type of facility an organization uses to recover its technology infrastructure when its primary data center goes...

  • disaster recovery (DR) test

    A disaster recovery test (DR test) is the examination of each step in a disaster recovery plan as outlined in an organization's ...

SearchStorage

  • enterprise storage

    Enterprise storage is a centralized repository for business information that provides common data management, protection and data...

  • disk array

    A disk array, also called a storage array, is a data storage system used for block-based storage, file-based storage or object ...

  • optical storage

    Optical storage is any storage type in which data is written and read with a laser. Typically, data is written to optical media, ...

Close