Role-Based Access Control Models
Computer
TRBAC: A temporal role-based access control model
ACM Transactions on Information and System Security (TISSEC)
Proposed NIST standard for role-based access control
ACM Transactions on Information and System Security (TISSEC)
Architectural Mismatch: Why Reuse Is So Hard
IEEE Software
Architectural Mismatch: Why Reuse Is So Hard
IEEE Software
Generalized Role-Based Access Control
ICDCS '01 Proceedings of the The 21st International Conference on Distributed Computing Systems
Architectural Prototyping: An Approach for Grounding Architectural Design and Learning
WICSA '04 Proceedings of the Fourth Working IEEE/IFIP Conference on Software Architecture
A Generalized Temporal Role-Based Access Control Model
IEEE Transactions on Knowledge and Data Engineering
The Future of Empirical Methods in Software Engineering Research
FOSE '07 2007 Future of Software Engineering
Architectural Mismatch: Why Reuse Is Still So Hard
IEEE Software
| Hi-index | 0.00 |
Integrating a COTS product in a company's product portfolio is appealing from a business perspective but highly challenging from the perspective of the software architecture. In this paper we outline research challenges regarding authorization in the identity management part of the Danish municipality administration system, called Opus BRS, a system that integrates SAP, legacy mainframe systems, and other systems present in the individual municipalities. Each of these systems defines their own access control model and architecture, which leads to architectural mismatch that impacts security, usability, as well as maintainability. We outline a three-year research project and discuss our research method that will include elements of action research as well as experiments using architectural prototyping. The project is carried out in cooperation with KMD, one of the largest Danish IT companies, who is the producer of the Opus system.