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:
“There is nothing that I shudder at more than the idea of a separation of the Union. Should such an event ever happen, which I fervently pray God to avert, from that date I view our liberty gone.”
—Andrew Jackson (1767–1845)
“The legislative powers of government reach actions only, and not opinions, ... thus building a wall of separation between Church and State.”
—Thomas Jefferson (1743–1826)
“Life is an offensive, directed against the repetitious mechanism of the Universe.”
—Alfred North Whitehead (1861–1947)
“Carlyle said “a lie cannot live.” It shows that he did not know how to tell them. If I had taken out a life policy on this one the premiums would have bankrupted me ages ago.”
—Mark Twain [Samuel Langhorne Clemens] (1835–1910)