Programming principles

system where only the inputs and outputs can be viewed, and not its implementation

language mechanism in programming languages that allows external code not to care about the internal workings of an object

acronym for "Keep it simple, stupid"; design principle

In object-oriented programming, SOLID is a mnemonic acronym for five principles intended to make source code more understandable, flexible, and maintainable. Although the principles apply to object-oriented programming, they can also form a core philosophy for methodologies such as agile software development and adaptive software development.

degree to which elements within a module belong together

software development principle with the goal of reducing repetitive software patterns, and replacing them with abstractions that use data normalization to avoid redundancy

in programming, the degree of interdependence between software modules

computer-programming principle that states that every class in a computer program should have responsibility over a single part of that program's functionality, which it should encapsulate

a computer-programming principle that states that software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification

object-oriented programming principle stating that, in a computer program, if S is a subtype of T, then objects of type T may be replaced with objects of type S without altering any of the desirable properties of the program (correctness, etc.)

solution approach where the problem is broken down into parts that can be solved independently of each other, by separating the what from the how

software programming technique in which general framework code calls into business-logic subroutines

use of existing source code to build new software

Guidelines in object-oriented design

collection of guiding principals for python programming language

guideline for object-oriented programming: each unit should have only limited knowledge about other units (only those closely related to the current unit)

principle that result in a specific form of decoupling of software modules that results in reversing of the dependency relationships established from high-level, policy-setting modules to low-level, dependency modules

principle in computer system design

principle of extreme programming that states a programmer should not add functionality until deemed necessary

states that no client should be forced to depend on methods it does not use

principle of segregation of the design decisions in a computer program that are most likely to change, thus protecting other parts of the program from extensive modification if the design decision is changed

form of defensive design intended to ensure the continuing function of a piece of software under unforeseen circumstances

humorous aphorism in computer programming

the idea that quality does not necessarily increase with functionality

system in which each of its components has, or makes use of, little or no knowledge of the definitions of other separate components

developed by Grady Booch

principle that every method should either be a command that performs an action, or a query that returns data to the caller, but not both; asking a question should not change the answer

computer programming refactoring rule of thumb

Discoverability is the degree to which something, especially a piece of content or information, can be found in a search of a file, database, or other information system. Discoverability is a concern in library and information science, many aspects of digital media, software and web development, and in marketing, since products and services cannot be used if people cannot find it or do not understand what it can be used for.

software design rule

coding guidelines by Gerald J. Holzmann

software design pattern

principle for avoiding duplicate information and effort in software engineering