检索规则说明:AND代表“并且”;OR代表“或者”;NOT代表“不包含”;(注意必须大写,运算符两边需空一格)
检 索 范 例 :范例一: (K=图书馆学 OR K=情报学) AND A=范并思 范例二:J=计算机应用与软件 AND (U=C++ OR U=Basic) NOT M=Visual
机构地区:[1]桂林电子科技大学计算机与控制学院,广西桂林541004
出 处:《计算机工程与应用》2008年第3期228-233,共6页Computer Engineering and Applications
基 金:广西自然科学基金( the Natural Science Foundation of Guangxi of China under Grant No.0542036)
摘 要:RBAC(Role Based Access Control)是一种被广泛认可的信息系统访问安全规范管理模型,但RBAC访问安全规范模型如何与组织系统的业务过程规范模型融合,从而更有效地服务于可信业务协同系统的开发实践还值得进一步研究改进。在RBAC模型的基础上,融合协同业务规范中的义务及奖惩元素,提出RBAO(Role Based Access and Obligation)模型。RBAO模型不仅能描述角色在组织中可拥有的访问权力,还能描述角色在组织中可能要承担的义务及义务违反时将受到的处罚。这使得RBAO模型更适合用于组织可信规范业务协同系统的管理建模与开发。以具体实例说明了基于RBAO模型的可信业务协同系统管理的分析与建模方法。RBAC(Role Based Access Control) is a widely accepted model suitable for access control of organizational information system.However there is still a gap need to be filled whenever considering practical application of RBAC in development of trustable organizational system,especially in combination of organizational business collaborative model with RBAC.Based on RBAC model,elements of obligation and reward/sanction in business collaborative model are proposed to extend RBAC to a new model called RBAO(Role Based Access and Obligation).RBAO specifies not only the authorizations of roles in an organization,but also their obligations and associated sanctions or rewards in collaborative business.RBAO is more applicable in trustable business collaborative system development comparing with RBAC.The analysis and modeling process of using RBAO in trustable collaborative business system development is illustrated through a case study.
分 类 号:TP311[自动化与计算机技术—计算机软件与理论]
正在载入数据...
正在载入数据...
正在载入数据...
正在载入数据...
正在载入数据...
正在载入数据...
正在载入数据...
正在链接到云南高校图书馆文献保障联盟下载...
云南高校图书馆联盟文献共享服务平台 版权所有©
您的IP:216.73.216.200