plural of principiation

(archaic) analysis into primary or elemental parts

Relating to principles or beginnings.

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

(programming, object-oriented programming) principle that states that once an interface has become too large, it needs to be split into smaller and more specific interfaces so that any client of the interface will only know about the methods that pertain to itself. (In other words: no client should be forced to depend on methods it does not use.)

(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.

(software, object-oriented design) Synonym of General Responsibility Assignment Software Patterns

(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.