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, mechanism and/or policy:
“The scholar was not raised by the sacred thoughts amongst which he dwelt, but used them to selfish ends. He was a profane person, and became a showman, turning his gifts to marketable use, and not to his own sustenance and growth. It was found that the intellect could be independently developed, that is, in separation from the man, as any single organ can be invigorated, and the result was monstrous.”
—Ralph Waldo Emerson (1803–1882)
“When one of us dies of cancer, loses her mind, or commits suicide, we must not blame her for her inability to survive an ongoing political mechanism bent on the destruction of that human being. Sanity remains defined simply by the ability to cope with insane conditions.”
—Ana Castillo (b. 1953)
“Make Policy Not Coffee”
—Feminist political button, c. 1970. ?....