Jump to content

Graph-based access control

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Prof schaller (talk | contribs) at 09:52, 3 July 2015 (Created page with '{{User sandbox}} <!-- EDIT BELOW THIS LINE --> '''Work in process''' Looking at the various applications and systems needed for running a business one thing ge...'). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

This sandbox is in the article namespace. Either move this page into your userspace, or remove the {{User sandbox}} template.

Work in process

Looking at the various applications and systems needed for running a business one thing gets obvious: in almost every application there is the need to maintain a model of the organization structure, of the roles and the actors in order to define access rights or assign tasks to employees (in case of a workflow management system). These redundancies lead to a great maintenance overhead that – even for small businesses – can grow to a great burden. This problem can be avoided by deploying one logically central component offering this service to other applications. This component is called an organization server.

Graph-based Access Control

asdf

Heading 2

[1]

[2]

  1. ^ Schaller, Thomas (1998). Organisationsverwaltung in CSCW-Systemen. Bamberg: Bamberg University.
  2. ^ Lawall, Schaller, Reichelt (2014). Enterprise Architecture: A Formalism for Modelling Organizational Structures in Information Systems. Thessaloniki: Enterprise and Organizatinal Modeling and Simulation: 10th International Workshop CAiSE2014.{{cite book}}: CS1 maint: multiple names: authors list (link) CS1 maint: publisher location (link)