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)
“Reunion after long separation is even better than one’s wedding night.”
—Chinese proverb.
“I’ve never known a Philadelphian who wasn’t a downright “character;” possibly a defense mechanism resulting from the dullness of their native habitat.”
—Anita Loos (1888–1981)
“In the field of world policy I would dedicate this Nation to the policy of the Good Neighbor—the neighbor who resolutely respects himself and, because he does, respects the rights of others—the neighbor who respects his obligations and respects the sanctity of his agreements in and with a world of neighbors.”
—Franklin D. Roosevelt (1882–1945)