| Papers [1-15] of 100 :: [Page 1 of 7] | | Go to page : 1 2 3 4 5 6 7 —> | Search results on "DATABASES": |
|
|
Federated Databases, 2004.
A look at subject switching algorithms for access control in federated databases.
39,375 words (approx. 157.5 pages), 134 sources, MLA, $ 249.95
»
Click here to show/hide summary
Abstract
This paper examines the concept of abstract authentication in federated database systems and the difficulties presented because the autonomously operated components may not know the identity of federation users. It looks at how one proposed solution is subject switching, where the federation translates the federated users identity to that of an agreed upon component subject and how this translation may be problematic due to not having component subjects with the same accesses requested by federation users. It proposes using proximity measures between requested and provided access and presents two policy neutral algorithms to find proximity minimizing matches between a federation subject and a collection of component subjects. It also explores the concepts relating to federated databases, authorization and access, and proposes some algorithms that will facilitate the subject switching method of reconciling access requirements.
Outline
Section 1
Abstract
Background
Introduction
Characteristics of Federated Databases
Homogeneous vs. Heterogeneous Databases
Agents
Agents and Meaning
Perspective
Types of Meaning
Semantics Versus Pragmatics
Context
Coverage of Communicative Acts
Mental Versus Social Agency
Section 2
Federated Database Systems and Autonomy
Design Autonomy
Communication Autonomy
Execution Autonomy
Association Autonomy
Authorization Autonomy
Distribution Transparency (i.e., Schema Integration)
Tightly Coupled
Limited Tight Coupling
Loosely Coupled
Federated Database Security
Authorization
Standards for Authentication
Decentralized vs. Centralized Authorization
Access Controls
User Based Access Control (UBAC)
Policy Based Access Control
Content Dependent Access Control (CDAC)
Context Based Access Control (CBAC)
View Based Access Control (VBAC)
Discretionary Access Control (DAC)
Mandatory Access Control (MAC)
Role Based Access Control (RBAC)
Section 3
Subject Switching
Subject Mapping Algorithms
Mapping Process
Federation Mapping Process
Federation Identity
Component Mapping Process
Minimum Disparity Measure
Mapping Algorithm
Create Object Sets
Identify Component Subjects
Evaluate Matching Subjects
Access Disparity Measures
Numerical Disparity Measure
Comparing Disparity Measures to Approximate Measures
Approximate Disparity Measure Comparison
Motivating Example
Access Compatibility Measures and Algorithms
Compatibility of Permissions and their Disparity Measures
Cardinality
Express Specification
Section 4
Metrics
Algorithm 1 (Least Under Permitting Algorithm)
Algorithm 2 (Least Over Permitting Algorithm)
Approximations: Metrics And Mappings
Approximate Mapping Algorithms
Algorithm 3 (Approximate Under Permitting Algorithm)
Algorithm 4 (Approximate Over Permitting Algorithm)
Properties of Algorithms 3 and Algorithm 4
Multilevel Federations
Non-Protected Database
Axioms
Deductive Channels Control Theorems
Signalling Channels Control Theorems
Cover Story
Multi-view Databases
Languages
Section 5
Conclusions and Ongoing Work
References
From the Paper
"Heimbingner and McLeod coined the phrase Federated Database System in 1985, and Seth and Larson later confirmed the formal definition. While the term has been loosely used to refer to several different but related database systems, they more precisely and unanimously define it as a collection of cooperating but autonomous component database systems. [SL90] (According to Oszu 1999, semi-autonomous systems are termed federative DBMS). A federated database system represents a compromise between no integration, wherein users must explicitly interface with multiple autonomous databases, and total integration, where the autonomy of each distinct database is sacrificed in order to allow users access through a single global interface."
| |
|
Object and Relational Databases, 2003.
This paper compares relational and object databases.
2,800 words (approx. 11.2 pages), 11 sources, MLA, $ 83.95
»
Click here to show/hide summary
Abstract
This paper discusses the differences between relational and object databases and the issues in storing objects in relational databases systems.
Preface
1. Introduction
2. Relational Databases
3. Object-Orientated Databases
4. Development and Design Issues
5. Security
6. Performance
7. Storing Objects in Relational Databases
8. Summary
Bibliography
From the Paper
"Since their inception, relational database management systems have been the most widely used database management systems today. Relational databases are favored in manipulating large amounts of data. The strong development of object-orientated programming languages has led to the emergence of object-oriented databases. Relational database models currently fail to satisfy the need of storing complex data types such as multimedia and CAD/CAM. Object oriented databases were designed to support these new trends in application development."
| |
|
Wallets and Databases, 2004.
An explanation of why databases are useful, using a person's wallet as an example.
1,123 words (approx. 4.5 pages), 2 sources, MLA, $ 38.95
»
Click here to show/hide summary
Abstract
This paper shows how the everyday contents of a personal wallet or purse comprises cards, memberships, registrations, and all kinds of information, which are based in various databases. Modern databases are used to collect and manage information, which affects virtually every area of contemporary life. For an example, the paper uses a person's credit card, by which personal and financial information are all stored in a variety of different databases.
From the Paper
"As in other new technological arenas, legal decisions lag behind technical developments. Ethics fill the gap as people negotiate how use of electronic information should proceed. The following notes define the broad ethical issues now being negotiated. Since laws deciding some aspects of these issues have been made, these notes should be read in conjunction with Legal Issues in Electronic Information Systems.
Ethics include moral choices made by individuals in relation to the rest of the community, standards of acceptable behavior, and rules governing members of a profession. The broad issues relating to electronic information systems include control of and access to information, privacy and misuse of data, and international considerations. All of these extend to electronic networks, electronic databases, and, more specifically, to geographic information systems."
| |
|
Databases, 2004.
A comparison of databases: Access, SQL, MS SQL Server 2000, Oracle, DB2, and MySQL.
1,050 words (approx. 4.2 pages), 6 sources, MLA, $ 36.95
»
Click here to show/hide summary
Abstract
This paper compares various databases: Access, SQL, MS SQL Server 2000, Oracle, DB2 and MySQL. The paper describes each database system, explaining which language it uses, what application it is best used for, and compares it to the other databases covered in this paper. The paper presents the advantages of using one database system over another one from a financial and technological point of view.
From the Paper
"Microsoft Office Access is a multi-user relational database management system. It is designed to allow user to quickly assemble, display, and share data with others while protecting the privacy of the data and ensuring to have full control over how the data is used and distributed. It makes use of visual design for queries, forms and reports for developing client-server database solutions. It is committed in offering integrated development environment, incremental compilation and interactive visual debugger, breakpoints and single step-through. Although the maximum database size is 1 GB, still database can include linked tables in other files and its total size is limited only by available storage capacity. The difference of Microsoft Access to other database is that it has a nice GUI that enables user to easily manage all information from a single database file. Within the file, user can use Tables for storing data, Queries for finding and retrieving data you want, Forms for view, add and update data within the table, Reports for analyzing or printing data and Data Access pages to view, update the database data."
| |
|
Distributed Databases, 2004.
Considers heterogenity and other issues in distributed databases.
678 words (approx. 2.7 pages), 2 sources, MLA, $ 23.95
»
Click here to show/hide summary
Abstract
This paper considers heterogenity, openness, scalability, security, concurrency, failure handling and transparency in distributed databases. It defines "distributed databases." The paper provides an analysis of its benefits and looks at productivity gains and security issues.
From the Paper
"As its name suggests a distributed database is a collection of data that is located in several different physical locations-that is distributed over several resources-while operating as a single logical database. This provides system managers the ability to distribute the database over multiple systems depending on system resources and to use either local or wide area networks to access the data. When this type of database configuration is used there are obviously many different factors that need to be taken into account ..."
| |
|
Privacy and Legal Issues in Databases, 2004.
Examines the lack of adequate security measures available to protect database systems.
1,180 words (approx. 4.7 pages), 3 sources, APA, $ 40.95
»
Click here to show/hide summary
Abstract
This paper takes a look at the ethical and legal issues associated with both the creation and use of data in databases. Many databases contain private information about individuals, and the paper looks at the threat posed by the easy access to this information. The paper also mentions some measures that IT departments can take to help safeguard the information in their databases, but also notes the limitations to these measures.
From the Paper
"In the past, one could access the public records by traveling to the courthouse or to the government office. In recent years, however, a growing number of government agencies and court systems have made these records available on the Internet databases. It might be considered useful that the public can access government records easily via the Internet. But these open records can create havoc from the hands of miscreants, if they can access other related information from the databases. Many of the individuals, when gain the access from electronic public records, use these data for secondary purposes. The solution for IT is not to prohibit public records altogether from the Internet, but records should be selectively used so that public cannot gain access to the confidential information. IT department can, instead, use some bogus data records to check the break-in in the databases (DeGeorge, 1986)."
| |
|
The U.S. Navy and Databases, 2004.
Discusses the various database systems employed by the U.S Navy.
728 words (approx. 2.9 pages), 3 sources, MLA, $ 25.95
»
Click here to show/hide summary
Abstract
The United States Navy uses several databases to enable it to function to the best of its capability. This paper presents information on a few of these databases, including the Navy Training Management and Planning System, which provides facilities of multiple funding, personnel, manpower, equipment, and training-course information databases in a single, integrated database. It also looks at the Navy Training Assessment System/General Training Management and Planning System (NTAS/GENTMPS), used since 1995 to train managers.
From the Paper
"Computer Sciences Corporation has a contract worth over $30 million with the Naval Undersea Warfare Center Division Newport, to integrate software engineering software systems for the Navy Training Management and Planning System. The contract is for eight years. During this time NTMPS will be converted to a web-based system to allow users to develop special studies and reports - this way they can work strategically to meet certain naval challenges."
| |
|
Comparison of Databases, 2002.
Compares and discusses several databases.
650 words (approx. 2.6 pages), 7 sources, $ 26.95
»
Click here to show/hide summary
Abstract
This paper compares a number of databases in terms of features for Access SQL, MS SQL Server 2000, Oracle, DB2, Informix and MySQL, emphasizing the differences found among these systems.
| |
|
YMCA Databases, 2002.
A discussion of the uses and the architecture of the YMCA Databases.
946 words (approx. 3.8 pages), 2 sources, MLA, $ 33.95
»
Click here to show/hide summary
Abstract
This paper illustrates how the Finesstri database system is a custom built application which serves the needs of the YMCA staff and membership community. It examines how together with complete integration across multiple locations and the internet, this software solution was a wise choice for the YMCA. It looks at the technological advances since the implementation of the system such as keeping membership records, staying in contact with members regarding their status and informing them about upcoming promotions as well as the simplification of making membership cards with digital cameras.
From the Paper
"Another feature of the new system is Finesstri's ability to communicate with the YMCA's website. Those who wish to become members can use the YMCA's website to place their membership request, select payment method, etc. When a potential new member logs onto the website, and fills out the online registration application, Finesstri is able to write that information directly to the membership database, and set up all the necessary fields without manual data entry. In this internet age, this integration with the internet is an invaluable facet of the new software."
| |
|
Distributed Databases, 1991.
This paper examines the rise of distributed databases, a means of increasing data accessibility: Evolution, advantages and disadvantages and implementation.
1,125 words (approx. 4.5 pages), 5 sources, $ 39.95
»
Click here to show/hide summary
From the Paper
"Distributed databases have the ability to be divided so that pieces of the databases can be physically located closest to where the data will be used. This enables companies to move from single-site databases built around mainframes to a network of locally placed but globally accessible databases which may even be on different classes of computers. This research examines the rise of distributed databases, their advantages and disadvantages, the environment necessary for their implementation, and an examination of how they may be used in the near future.
Data processing has evolved through three stages since 1955: decentralized, centralized, and distributed. When computers were first introduced to business, they were used by autonomous business units for specialized purposes. Networking ... '
| |
|
XML Databases, 2005.
This paper discusses the designing of XML databases.
7,555 words (approx. 30.2 pages), 11 sources, MLA, $ 165.95
»
Click here to show/hide summary
Abstract
This paper explains that XML is an 'Extensible Markup Language', which is a subset of SGML that makes up a particular text markup language that can be used in web applications in the process of the interchanging of certain structured data. The author points out that the basic idea of web design is to stay as close to the reality as possible, while making sure that the web page is attractive and the delivery is fast because, when a user becomes impatient, then the charm of a beautifully designed web page will be lost on them. The paper relates that the best thing about XML and its new tools is that a designer can build applications which are driven by one single information model whereby the behavior and the application of the program can be changed and adapted wherever necessary without changing the code.
From the Paper
"What exactly is a 'web-enabled database? The World Wide Web, as everyone knows, provides the user with a host of tools with which he cane gain access to information and knowledge on the Internet and browse for information using web browsing technologies. Numerous people also use web browsing in order to deliver marketing messages, advertising information, promotional material for any products, and so on. However, what is most surprising is the fact that the World Wide Web is rarely, if ever, used for what it really must be used for: the provision to interactive business information on the Internet, through which an organization may make any number of queries for information and then gain access to the information that the queries generate. An organization can also place orders on the World Wide Web, and get all its numerous statements and records updated constantly through the browser services provided on the Internet. In a nutshell, this is what a web-enabled database must be able to do, and this is what it does if it is implemented well."
| |
|
Oracle Databases, 2004.
A discussion on the implementation methods of an Oracle database.
1,150 words (approx. 4.6 pages), 2 sources, MLA, $ 39.95
»
Click here to show/hide summary
Abstract
This paper describes various issues to be taken into account when implementing an Oracle database. These include cost, platform, training and database design. It expands on the programming process. The author also explains the importance of choosing the right database for a company.
From the Paper
"For most companies today their computer systems form the heart of the business. Web sites, accounting, sales, tracking, manufacturing, human resources and ancillary day-to-day functions all reside on various computer systems that are ..."
| |
|
Databases in Culinary Management, 2002.
Analysis of culinary management database tools.
2,467 words (approx. 9.9 pages), 2 sources, MLA, $ 75.95
»
Click here to show/hide summary
Abstract
This paper analyzes the potential use of databases in the kitchen and looks at the advantages that a specialized database management system could offer to the culinary management sector.
From the Paper
"This online recipe database is to be designed such that people can view the individual recipes and the preparation methods as well create and update their own favorite recipes. Furthermore the company is also interested into using the web as a means of increasing their business by accepting customer orders online and delivering them in a fairly short amount of time. The problem currently faced by the restaurant is that there is no proper integration between the different branches and this results in considerable loss. To avoid this loss there is an immediate need for designing complete recipe management database system. A fully integrated recipe database would facilitate real time information exchange pertaining to the different items. This would allow them to control their schedule with a view to optimizing the production. This is particularly significant for a big chain restaurant like 'Funday' where a database system would constitute an effective decision support system."
| |
|
Databases, 2005.
This paper reviews five database programs, their system requirements and the company.
930 words (approx. 3.7 pages), 2 sources, MLA, $ 33.95
»
Click here to show/hide summary
Abstract
This paper methodically examines Access SQL, MS SQL Server 2000, Oracle, DB2 and MySQL. The author explains, for example, that MS Access is a relational database management system used on desktop computer to manage information on different levels for different purposes and provides some capabilities for making a database available on the web. The paper continues, for example, that the system requirements for DB2 includes a Microsoft Windows 2000 SP4, Windows XP SP1 or Windows 2003 Server operating system, a Pentium 100 MHz or faster processor, 128MB or more RAM and a hard drive with 75 MB of free disk space with additional space required to store vulnerability information.
Table of Contents
MS Access
System Requirements (Access 2003)
Company
MS SQL Server 2000
System Requirements (with Service Pack 4)
Company
Oracle
System Requirements
Recommended Server Specifications
Minimum Client Specifications
Company
DB2
System Requirements
Company
MySQL
System Requirements
Company
From the Paper
"Oracle is a relational database management system. Oracles latest technology, today's system designers and developers can build 21st century enabled applications ranging from critical online transaction processing systems supporting thousand of users to multi-terabyte data warehouses for decision support and also World Wide Web-based applications. Bradmark Technologies is a company that offers database management software used with products from providers including Oracle, Sybase and Microsoft. Customers in a variety of industries use Bradmark's products for tasks such as database monitoring, performance tuning and database administration."
| |
|
SQL and Databases, 2005.
This paper looks at SQL (structured query language) as a programming language for a database.
675 words (approx. 2.7 pages), 4 sources, $ 26.95
»
Click here to show/hide summary
Abstract
The paper examines SQL (structured query language) and whether it can or should support duplicate rows in a database. The paper notes that SQL is a standard interactive and programming language used to get information from and update a database and it is considered easy to use and effective. The paper explains that there are different versions of this approach from different companies, but all use the same basic rules and commands.
From the Paper
"SQL, or structured query language, is a standard interactive and programming language used to get information from and update a database. SQL is both an ANSI and an ISO standard, but many database products support SQL with proprietary extensions to the standard language. Queries take the form of a command language allowing the user to select, insert, update and find out the location of data. Duplicate rows are eliminated by specific commands in SQL and the issue is whether there is any time when duplicate rows might be supported in SQL or whether maintaining distinct records is a positive or a negative element of the system. SQL is a standardized language for use in relational databases and is considered easy to use and effective. There are different versions of this approach from different companies, but all use the same basic rules and commands."
|
|
|
