Downloads & Free Reading Options - Results

Bell System Technical Journal, 61: 9. November 1982 pp 2555-2566. Database Systems: Issues in the Design of a Distributed Record Management System. (Linderman, J.P.)

Bell System Technical Journal, 61: 9. November 1982 pp 2459-2474. Database Systems: Implementation of a Distributed Database Management Systemto Support Logical Subnetworks. (Cohen, D.)

Conventional standalone application development paradigm is being transformed into multi-layered application development process. The main reason of transformation is the execution environment— particularly internetworking. The above mentioned transformation requires major changes in the platforms i.e. Hardware, Software, application development tools, and database management systems. This study especially focuses on the data related issues of applications, running on distributed platforms. The key attributes of distributed applications’ data include Autonomy, Distribution and Heterogeneity. Autonomy of DBMS can be defined as a degree to which a database management system can operate independently, which can be implemented at design, communication and execution level. Distribution deals with data distribution on diverse network platforms. Database Management System components can vary in Data Model, Data Structure, Query Languages, Data Manipulation, Schema, Operating System, Hardware, Location. The Databases that differ in these are termed as Heterogeneous Databases. Today’s applications often need integration of databases deployed on variety of platforms and possibly supporting different data models and data structures. It seems very difficult to implement the above stated attributes in different database management systems provided by various vendors. In order to integrate the information from heterogeneous data sources, it is necessary to form a gateway or mediator architecture. XML (eXtensible Markup Language) is a portable data definition and transportation language. One of the major applications of XML is to provide the mediation between two or more heterogeneous databases. This study aims at designing a prototype for accessing heterogeneous data sources using XML standard. Additionally the comparative study of Databases and XML has been carried out to present XML as potential candidate for data modeling and data definition requirements of any application. Furthermore an interactive data cleaning, analysis and transformation model has been added to integrate the diverse data and perform variety of data cleaning operations.

Much of the work to date to apply Role-Based Access Control (RBAC) to database management systems has focused on single database systems or an integrated distributed database system. For situations where the need exists to consolidate multiple independent databases, and where the direct integration of the databases is neither practical nor desirable, the application of RBAC requires that policy be enforced via a method that is distinct from the databases. The method must provide for the verification of the RBAC policy, while allowing for the independence of the various databases on which the policy is enforced. This paper proposes a model for an application that provides for a web-based interface for users to be granted access to data held in various independent databases. The application enforces a strict RBAC policy on a well-defined set of accesses, while alleviating the need for users to have a separate account on each of the databases.

Bibliography: p. 42-50

This is a status report on the progress of the DAVID (Distributed Access View Integrated Database Management System) project being carried out at Louisiana State University, Baton Rouge, Louisiana. The objective is to implement an interface between Astrophysical datasets and DAVID. Discussed are design details and implementation specifics between DAVID and astrophysical datasets.

Much of the work to date to apply Role-Based Access Control (RBAC) to database management systems has focused on single database systems or an integrated distributed database system. For situations where the need exists to consolidate multiple independent databases, and where the direct integration of the databases is neither practical nor desirable, the application of RBAC requires that policy be enforced via a method that is distinct from the databases. The method must provide for the verification of the RBAC policy, while allowing for the independence of the various databases on which the policy is enforced. This paper proposes a model for an application that provides for a web-based interface for users to be granted access to data held in various independent databases. The application enforces a strict RBAC policy on a well-defined set of accesses, while alleviating the need for users to have a separate account on each of the databases.

Much of the work to date to apply Role-Based Access Control (RBAC) to database management systems has focused on single database systems or an integrated distributed database system. For situations where the need exists to consolidate multiple independent databases, and where the direct integration of the databases is neither practical nor desirable, the application of RBAC requires that policy be enforced via a method that is distinct from the databases. The method must provide for the verification of the RBAC policy, while allowing for the independence of the various databases on which the policy is enforced. This paper proposes a model for an application that provides for a web-based interface for users to be granted access to data held in various independent databases. The application enforces a strict RBAC policy on a well-defined set of accesses, while alleviating the need for users to have a separate account on each of the databases.

Much of the work to date to apply Role-Based Access Control (RBAC) to database management systems has focused on single database systems or an integrated distributed database system. For situations where the need exists to consolidate multiple independent databases, and where the direct integration of the databases is neither practical nor desirable, the application of RBAC requires that policy be enforced via a method that is distinct from the databases. The method must provide for the verification of the RBAC policy, while allowing for the independence of the various databases on which the policy is enforced. This paper proposes a model for an application that provides for a web-based interface for users to be granted access to data held in various independent databases. The application enforces a strict RBAC policy on a well-defined set of accesses, while alleviating the need for users to have a separate account on each of the databases.

Much of the work to date to apply Role-Based Access Control (RBAC) to database management systems has focused on single database systems or an integrated distributed database system. For situations where the need exists to consolidate multiple independent databases, and where the direct integration of the databases is neither practical nor desirable, the application of RBAC requires that policy be enforced via a method that is distinct from the databases. The method must provide for the verification of the RBAC policy, while allowing for the independence of the various databases on which the policy is enforced. This paper proposes a model for an application that provides for a web-based interface for users to be granted access to data held in various independent databases. The application enforces a strict RBAC policy on a well-defined set of accesses, while alleviating the need for users to have a separate account on each of the databases.

Bibliography: p. 37-41