Role-based Model Research Articles

CUSTOMIZING COMPONENT-BASED SOFTWARE USING COMPONENT COORDINATION MODEL: A USE-CONTEXT DRIVEN APPROACH TOWARD ROLE-BASED MODEL

In this paper, we introduce a component coordination model (CCM) that is embedded into the applications during software architecture design. The CCM is driven by the use-context model, which directly reflects the role-based model that abstracts system behaviors as a computational organization comprising various role relationships. It then focuses on exposing the design of software components to be separated from their execution contexts. These separate concerns — computation, coordination, and policies imposed on a given use-context — form the principal concept of our approach. Finally, a case study using the proposed model has been demonstrated in order to provide the feasibility of the introduced approach.

The ARBAC97 model for role-based administration of roles

In role-based access control (RBAC), permissions are associated with roles' and users are made members of roles, thereby acquiring the roles; permissions. RBAC's motivation is to simplify administration of authorizations. An appealing possibility is to use RBAC itself to manage RBAC, to further provide administrative convenience and scalability, especially in decentralizing administrative authority, responsibility, and chores. This paper describes the motivation, intuition, and formal definition of a new role-based model for RBAC administration. This model is called ARBAC97 (administrative RBAC '97) and has three components: URA97 (user-role assignment '97), RPA97 (permission-role assignment '97), and RRA97 (role-role assignment '97) dealing with different aspects of RBAC administration. URA97, PRA97, and an outline of RRA97 were defined in 1997, hence the designation given to the entire model. RRA97 was completed in 1998. ARBAC97 is described completely in this paper for the first time. We also discusses possible extensions of ARBAC97.

Multiagent Design of a Role-Based Model for Project Management

The project management approach we propose is based on three main concepts: the project life cycle with the different steps to carry out and the possibility of defining recursive projects, the transition system which describes the project behavior th

Analysis, comparison and design of role-based security specifications

The need to analyze and compare the security specifications of different applications can arise in different contexts, such as the federated environments, to provide a unification layer for the federation, or, in the construction of security components, to support the reusability of security specifications. In this paper, we propose similarity criteria and associated metrics to compare security specifications of different applications and evaluate their similarities. We consider security specifications defined according to a role-based model, which provides powerful authorization mechanisms suitable for similarity analysis. We describe the application of the proposed similarity techniques to the construction and use of reusable security components.

Role-Based Models of Advertising Creation and Production

Abstract Although researchers have frequently examined advertising production from various functional perspectives, they have largely ignored its collaborative and processual aspects. Centered in the “production of culture” perspective, this paper compares six role-based models of the advertising production process. Propositions arising from these models deal with (1) the subjectivity of participants' perspectives, (2) the determinants of perceived authorship of the advertisement, and (3) inherent processual conflicts due to the varied personal utilities of the produced advertisement. Discussion focuses upon how these issues may influence the content and structure of the advertising message.

A Database Administration Support Environment

This paper identifies and defines the facilities needed to enable a database administrator to organise and control the development and operational running of a database system. The data needed to support these facilities, termed control data is discussed, and a conceptual data model for a control database is presented. This control database forms the core of a database administration support environment.The paper examines the facilities required from a database administration support environment for the effective specification and implementation of access control. A role-based model for access control is proposed, and is used to critically examine the current CODASYL approach to access control.This paper is based on the work of the BCS/CODASYL DDLC Database Administration Working Group, of which the authors are members. However, the opinions expressed in the paper are those of the authors.