A role shows a job function in an enterprise. In a rolebased access control model, a role is a set of access rights. A subject doing jobs is granted roles showing the jobs. In addition, objects have to be consistent in presence of multiple conflicting transactions. A transaction issued by a subject is associated with a subset of roles granted to the subject, which is named purpose. A method with a more significant purpose is performed before another method with a less significant purpose. We discuss which purpose is more significant than another purpose. We discuss general role-ordering (GRO) schedulers so that multiple conflicting transactions are serializable in the significant order of subjects and purposes. We evaluate the GRO scheduler compared with the traditional two-phase locking protocol.
['Tomoya Enokido', 'Makoto Takizawa']
Concurrency Control in Multi-Role Association