The separation of mechanism and policy is a design principle in computer science. It states that mechanisms (those parts of a system implementation that control the authorization of operations and the allocation of resources) should not dictate (or overly restrict) the policies according to which decisions are made about which operations to authorize, and which resources to allocate.
This is most commonly discussed in the context of security mechanisms (authentication and authorization), but is actually applicable to a much wider range of resource allocation problems (e.g. CPU scheduling, memory allocation, Quality of Service), and the general question of good object abstraction.
Per Brinch Hansen presented arguments in favor of separation of mechanism and policy.
Artsy and Livny, in a 1987 paper, discussed an approach for an operating system design having an "extreme separation of mechanism and policy".
In a 2000 article, Chervenak et al. described the principles of mechanism neutrality and policy neutrality.
Read more about Separation Of Mechanism And Policy: Rationale and Implications, See Also
Famous quotes containing the words separation of, separation, mechanism and/or policy:
“... the separation of church and state means separation—absolute and eternal—or it means nothing.”
—Agnes E. Meyer (1887–1970)
“Like sleep disturbances, some worries at separation can be expected in the second year. If you accept this, then you will avoid reacting to this anxiety as if it’s your fault. A mother who feels guilty will appear anxious to the child, as if to affirm the child’s anxiety. By contrast, a parent who understands that separation anxiety is normal is more likely to react in a way that soothes and reassures the child.”
—Cathy Rindner Tempelsman (20th century)
“Life is an offensive, directed against the repetitious mechanism of the Universe.”
—Alfred North Whitehead (1861–1947)
“War is regarded as nothing but the continuation of state policy with other means.”
—Karl Von Clausewitz (1780–1831)