(object-oriented programming) A principle stating that any type having a subtype should be replaceable by its subtype without altering any of the desirable properties (such as correctness, task performed, etc.) of the program.

(object-oriented programming) Design principle that states that (1) High- and low-level modules should both depend on abstractions and (2) instead of abstractions depending upon details, details should depend upon abstractions.

(programming, object-oriented programming) A principle that states that software entities (such as classes, modules, and functions) should be open for extension, but closed for modification.

(software, design) a technique by which classes may achieve polymorphic behavior and code reuse by containing other classes that implement the desired functionality instead using inheritance.

(programming, object-oriented programming) The principle that every class should have a single responsibility entirely encapsulated by that class.

(software, user interface, design) A principle that the design should match the user's experience, expectations, and mental models.

(software, object-oriented programming) Synonym of Law of Demeter

(logic) principle of explosion

A principle in biology stating that allele and genotype frequencies in a population will remain constant from generation to generation in the absence of other evolutionary influences.

(business) A rule according to which decisions and transactions need approval from two individuals, typically the CEO and CFO.