| dbo:abstract |
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. While most commonly discussed in the context of security mechanisms (authentication and authorization), separation of mechanism and policy is applicable to a range of resource allocationproblems (e.g. CPU scheduling, memory allocation, quality of service) as well as the design of software abstractions. Per Brinch Hansen introduced the concept of separation of policy and mechanism in operating systems in the RC 4000 multiprogramming system. 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. (en) 機構と方針の分離とは、計算機科学における設計原則の1つ。機構（操作の認可と資源配分を制御するシステム実装部分）は、どの操作を認可するかやどの資源を割り当てるかといった決定を行う際の方針を表すべきでない（あるいは過度に制限すべきでない）という考え方である。 主にセキュリティ機構（認証と認可）に関して議論されるが、様々な資源配分問題（CPUスケジューリング、メモリ割り当て、Quality of Serviceなど）にも当てはまる考え方であり、オブジェクト抽象化全般に関わる課題でもある。 機構と方針を分離すべきだと主張した計算機科学者として Per Brinch Hansen がいる。 1987年の論文で Artsyらは「機構と方針を極端に分離」させたオペレーティングシステムの設計技法を論じた。 Chervenakらは2000年の論文で、「機構中立性」と「方針中立性」という原則を提唱した。 (ja) |
| dbo:wikiPageExternalLink |
http://brinch-hansen.net/papers/2001b.pdf http://portal.acm.org/citation.cfm%3Fid=360596&dl=ACM&coll=&CFID=15151515&CFTOKEN=6184618 http://pages.cs.wisc.edu/~miron/ http://hpc.csie.thu.edu.tw/meeting/g93/g932910_Yao-Chun%20Chi/ycc_2005-11-04_The%20Data%20Grid_Towards%20an%20Architecture%20for%20the%20Distributed%20Management%20and%20Analysis%20of%20Large%20Scientific%20Datasets.pdf https://web.archive.org/web/20170705054440/ftp:/ftp.cs.uky.edu/cs/manuscripts/vade.mecum.2.pdf http://portal.acm.org/citation.cfm%3Fid=362278&dl=ACM&coll=GUIDE&CFID=11111111&CFTOKEN=2222222 http://portal.acm.org/citation.cfm%3Fid=364017&coll=portal&dl=ACM http://portal.acm.org/citation.cfm%3Fid=806531&dl=ACM&coll=&CFID=15151515&CFTOKEN=6184618 http://www.cs.wisc.edu/condor/ |
| dbo:wikiPageID |
12155645 (xsd:integer) |
| dbo:wikiPageLength |
9453 (xsd:nonNegativeInteger) |
| dbo:wikiPageRevisionID |
1068239915 (xsd:integer) |
| dbo:wikiPageWikiLink |
dbr:Monolithic_kernel dbr:Per_Brinch_Hansen dbr:Unix_philosophy dbr:Resource_allocation dbr:Memory_allocation dbr:Configuration_file dbr:Application_programming_interface dbr:Computer_science dbr:Keycard_lock dbr:Microkernel dbr:Late_binding dbr:Raphael_Finkel dbr:Quality_of_service dbc:Operating_system_technology dbr:Abstraction_(computer_science) dbc:Programming_principles dbr:Software_design dbr:Authorization dbc:Dichotomies dbr:Operating_system dbr:RC_4000_multiprogramming_system dbr:X_Window_System dbr:Separation_of_concerns dbr:Scheduling_(computing) dbr:Separation_of_protection_and_security dbr:Filesystem_permissions |
| dbp:bot |
InternetArchiveBot (en) |
| dbp:date |
March 2018 (en) |
| dbp:fixAttempted |
yes (en) |
| dbp:wikiPageUsesTemplate |
dbt:Cite_book dbt:Cite_journal dbt:Cite_web dbt:Cn dbt:Dead_link dbt:Reflist |
| dcterms:subject |
dbc:Operating_system_technology dbc:Programming_principles dbc:Dichotomies |
| gold:hypernym |
dbr:Principle |
| rdf:type |
dbo:Agent |
| rdfs:comment |
機構と方針の分離とは、計算機科学における設計原則の1つ。機構（操作の認可と資源配分を制御するシステム実装部分）は、どの操作を認可するかやどの資源を割り当てるかといった決定を行う際の方針を表すべきでない（あるいは過度に制限すべきでない）という考え方である。 主にセキュリティ機構（認証と認可）に関して議論されるが、様々な資源配分問題（CPUスケジューリング、メモリ割り当て、Quality of Serviceなど）にも当てはまる考え方であり、オブジェクト抽象化全般に関わる課題でもある。 機構と方針を分離すべきだと主張した計算機科学者として Per Brinch Hansen がいる。 1987年の論文で Artsyらは「機構と方針を極端に分離」させたオペレーティングシステムの設計技法を論じた。 Chervenakらは2000年の論文で、「機構中立性」と「方針中立性」という原則を提唱した。 (ja) 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. (en) |
| rdfs:label |
機構と方針の分離 (ja) Separation of mechanism and policy (en) |
| owl:sameAs |
freebase:Separation of mechanism and policy wikidata:Separation of mechanism and policy dbpedia-ja:Separation of mechanism and policy https://global.dbpedia.org/id/4v6mA |
| prov:wasDerivedFrom |
wikipedia-en:Separation_of_mechanism_and_policy?oldid=1068239915&ns=0 |
| foaf:isPrimaryTopicOf |
wikipedia-en:Separation_of_mechanism_and_policy |
| is dbo:wikiPageDisambiguates of |
dbr:Policy_(disambiguation) |
| is dbo:wikiPageRedirects of |
dbr:Policies_and_mechanisms dbr:Separation_of_mechanism_from_policy |
| is dbo:wikiPageWikiLink of |
dbr:List_of_pioneers_in_computer_science dbr:Per_Brinch_Hansen dbr:Unix_philosophy dbr:Protection_mechanism dbr:Live,_virtual,_and_constructive dbr:Community_of_interest_(computer_security) dbr:Kernel_(operating_system) dbr:Policy_(disambiguation) dbr:Microkernel dbr:Distributed_operating_system dbr:Recursive_Internetwork_Architecture dbr:IXI_Limited dbr:List_of_software_development_philosophies dbr:Separation_of_protection_and_security dbr:Policies_and_mechanisms dbr:Separation_of_mechanism_from_policy |
| is foaf:primaryTopic of |
wikipedia-en:Separation_of_mechanism_and_policy |