Downloads & Free Reading Options - Results

The purposes of this thesis is to communicate a general knowledge of software engineering principles that can be applied to the development of a software system. Fundamental Software Engineering concepts are first discussed and then applied to a personnel database management system which is featured throughout the thesis. The individual tools and techniques that are used in each phase of the system development are widely known in the computer science community and each has been employed successfully in certain situations. Keywords: Database design; Personnel systems; Greek Navy personnel database; Theses.

Database management systems have been developed mainly for commercial and business processing. As such, it generally manages formatted data, rather than information, which is less structured and comes in many forms such as text, graphics, images, voices, and signals. Beyond the capability of handling multimedia information, non-business application areas call for further requirement. Real-time processing, risk assessment, and partial answers are some of the more important requirements, especially in the military applications. In this paper, we discuss issues involved in creating such advanced database management system and propose some approaches.

Database management systems have been developed mainly for commercial and business processing. As such, it generally manages formatted data, rather than information, which is less structured and comes in many forms such as text, graphics, images, voices, and signals. Beyond the capability of handling multimedia information, non-business application areas call for further requirement. Real-time processing, risk assessment, and partial answers are some of the more important requirements, especially in the military applications. In this paper, we discuss issues involved in creating such advanced database management system and propose some approaches.

To many critics and researchers, semantic meagerness is the main limitation of relational database management systems. The burden placed on users to remember attribute names and their domains is discussed and difficulties associated with the lack of set as a type for an attribute is examined. This thesis explores the implications to high-level query languages necessitated by a set-type attribute. The allowance of semantically improper joins by DBMS is studied as is the lack of strong data type checking. The semantic shortcomings of system-chosen access paths is discussed. These problems are followed by recommended solutions.

To many critics and researchers, semantic meagerness is the main limitation of relational database management systems. The burden placed on users to remember attribute names and their domains is discussed and difficulties associated with the lack of set as a type for an attribute is examined. This thesis explores the implications to high-level query languages necessitated by a set-type attribute. The allowance of semantically improper joins by DBMS is studied as is the lack of strong data type checking. The semantic shortcomings of system-chosen access paths is discussed. These problems are followed by recommended solutions.

To many critics and researchers, semantic meagerness is the main limitation of relational database management systems. The burden placed on users to remember attribute names and their domains is discussed and difficulties associated with the lack of set as a type for an attribute is examined. This thesis explores the implications to high-level query languages necessitated by a set-type attribute. The allowance of semantically improper joins by DBMS is studied as is the lack of strong data type checking. The semantic shortcomings of system-chosen access paths is discussed. These problems are followed by recommended solutions.

To many critics and researchers, semantic meagerness is the main limitation of relational database management systems. The burden placed on users to remember attribute names and their domains is discussed and difficulties associated with the lack of set as a type for an attribute is examined. This thesis explores the implications to high-level query languages necessitated by a set-type attribute. The allowance of semantically improper joins by DBMS is studied as is the lack of strong data type checking. The semantic shortcomings of system-chosen access paths is discussed. These problems are followed by recommended solutions.

TRI 1 2019/2020

ADA208167

This thesis contains program documentation for the Air Force Institute of Technology School of Systems and Logistics Graduate Programs Office Database Management System (DBMS) application. Chapter I, Database Dictionaries, contains a description of data in the DBMS database. Chapter II, Screen Format Files, contains a listing of DBMS screen display program code. Chapter III, Report Specifications, contains Concentric Data Systems R&R Relational Report Writer report specifications. Chapter IV, Program Documentation, contains Ashton-Tate dBASE III Plus program code written for this application. Application development adn the DBMS User's Manual are documented in Volume (1): Development and User's Manual.

Future NASA earth science missions, including the Earth Observing System (EOS), will be generating vast amounts of data that must be processed and stored at various locations around the world. Here we present a stepwise-refinement of the intelligent database management (IDM) of the distributed active archive center (DAAC - one of seven regionally-located EOSDIS archive sites) architecture, to showcase the telecommunications issues involved. We develop this architecture into a general overall design. We show that the current evolution of protocols is sufficient to support IDM at Gbps rates over large distances. We also show that network design can accommodate a flexible data ingestion storage pipeline and a user extraction and visualization engine, without interference between the two.

Future NASA earth science missions, including the Earth Observing System (EOS), will be generating vast amounts of data that must be processed and stored at various locations around the world. Here we present a stepwise-refinement of the intelligent database management (IDM) of the distributed active archive center (DAAC - one of seven regionally-located EOSDIS archive sites) architecture, to showcase the telecommunications issues involved. We develop this architecture into a general overall design. We show that the current evolution of protocols is sufficient to support IDM at Gbps rates over large distances. We also show that network design can accommodate a flexible data ingestion storage pipeline and a user extraction and visualization engine, without interference between the two.

The purpose of this thesis was to develop an efficient computer-based database management system application to automate manual information processing procedures used by the Air Force Institute of Technology School of Systems and Logistics Graduate Programs Office. The author was able to create an efficient DBMS application that met the needs of the Graduate Programs Office using the Ashton-Tate dBASE III Plus (TM) DBMS and the Concentric Data Systems R&R relational Report Writer (R). The application was implemented upon completion. The introduction provides background on the AFIT Graduate Programs Office and their automated data processing requirements, examines characteristics of good DBMSs, examines DBMS development lifecycle, discusses software selection criteria, and examines four DBMS applications developed in 1987. Chapter II documents the methodology used in developing the DBMS. Chapter III discusses the programmer's incorporation of good DBMS characteristics presented in Chapter I and discusses whether the author was successful in achieving his goal of solving the specific problem. Chapter IV describes the impact on Graduate Programs Office operations using the DBMS and recommends follow-on studies. The appendix, Graduate Programs Office User's Manual, describes DBMS Operations.

Bibliography: p. 42-50

Bibliography: p. 42-50

Bibliography: p. 37-41

The purpose of this thesis was to program a database system written in dBase III Plus for use in AFIT/LSM. The system was to be hosted on a personal computer so that it could be transportable between the different computers in the office and conveniently used by as many personnel as possible. The program was intended to replace as much manual paperwork as possible and to provide a means to quickly access, sort, and to efficiently answer queries regarding the department faculty. The final result was intended to automate the routine office functions. This automation would relieve the department personnel from mundane duties so that they could concentrate their time on more productive pursuits. The product of these efforts was the Integrated Faculty Information System (IFIS). The IFIS is a menu driven system that utilizes 19 databases that are interrelated to form one large database system. The database system has the capability to contain all the vital professional and demographic information on each member of the staff. The IFIS provides a means to input all the appropriate information and to modify preexisting information within the database system. Keywords: Office automation, Computer programming, Database management systems, Databases, Personal computers, Theses.

CMPSC 431W Database Management Systems, Fall 2015

CMPSC 431W Database Management Systems, Fall 2015

This paper presents considerations about several topics that have a direct influence on data reliability and performance in object oriented database management systems. These topics are: physical storage management (clustering), concurrency control, crash recovery, garbage collection, and database security. Each topic is illustrated by its application to the Tactical Database as designed for the Low Cost Combat Direction System.

This paper presents considerations about several topics that have a direct influence on data reliability and performance in object oriented database management systems. These topics are: physical storage management (clustering), concurrency control, crash recovery, garbage collection, and database security. Each topic is illustrated by its application to the Tactical Database as designed for the Low Cost Combat Direction System.

The goal of this thesis was to study the performance of three commercial object-oriented database management systems. The commercial systems studied included: Itasca, sold by Itasca Systems Incorporated; Matisse, sold by Intellitic International; and ObjectStore, sold by Object Design Incorporated. To examine performance of these database management systems two benchmarks were run: the OO1 benchmark and a new AFIT Simulation benchmark. The OO1 benchmark was designed, implemented, and run on all three database management systems. ObjectStore was our top performer on all configurations of the OO1 benchmark. The AFIT Simulation benchmark was designed, implemented, and run on the ObjectStore database management system. A nonpersistent version of the benchmark was also created in the C++ programming language. There was minimal performance overhead incurred due to the use of ObjectStore. especially when compared to the functional benefits gained. We concluded that there are major differences between the performance levels offered in current commercial object-oriented database management systems. We also concluded that a programming language interface to an object-oriented database management system should not be middle ground. Either it should be closely tied to a specific language or not tied to a specific language at all. Database benchmarks, Object-oriented databases, Simulation.

Artificial intelligence application requirements demand powerful representation capabilities as well as efficiency for real-time domains. Many tools exist, the most prevalent being expert systems tools such as ART, KEE, OPS5, and CLIPS. Other tools just emerging from the research environment are truth maintenance systems for representing non-monotonic knowledge, constraint systems, object oriented programming, and qualitative reasoning. Unfortunately, as many knowledge engineers have experienced, simply applying a tool to an application requires a large amount of effort to bend the application to fit. Much work goes into supporting work to make the tool integrate effectively. A Knowledge Management Design System (KNOMAD), is described which is a collection of tools built in layers. The layered architecture provides two major benefits; the ability to flexibly apply only those tools that are necessary for an application, and the ability to keep overhead, and thus inefficiency, to a minimum. KNOMAD is designed to manage many knowledge bases in a distributed environment providing maximum flexibility and expressivity to the knowledge engineer while also providing support for efficiency.

The general objective of the information management component of the New York Bight Study was to develop a District-based system (a geographic information system or GIS) to store, manipulate, and analyze the data sets associated with and developed by the New York Bight study. To accomplish this objective, the following efforts were required: database development, hardware/ software acquisition, system installation, input of database attributes and graphic elements, and training of New York District personnel. Intergraph hardware and software were chosen as the system platform. Oracle database software was selected because it is one of the more common relational database management systems that provides comprehensive relational database (RDB) functions and data storage capabilities. The selection of a base map projection and coordinate system was one of the first decisions made in the process of loading graphic data. Several files were loaded into the system including: digitized shoreline files, graphic representations of gauge locations, tide data, satellite images, model output for water surface elevation, temperature, salinity, and dissolved oxygen, wave hindcast data, and ship observation data. Appendix A presents a basic user training guide. Project training was focused to create geographic map displays from measured data and model output, and to perform analyses on these data. Training was performed in the manner that reflected the types of projects undertaken by the New York District and addressed problems or questions of interest to the New York District. Geographic information system, New York bight, Intergraph, Relational database.

USA

Tri 1 2022/2023 (Term Id 2210)

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.

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.

Includes bibliographical references and index

This paper outlines a general philosophy and framework for the specification of a data model. Extracts from scenarios that have been developed for specification of several well-known data models (e.g., DBTG, relational, TDMS) are given and discussed. These extracts are preliminary and incomplete, but they are used to illustrate the feasibility of the Data Model Processor Approach. The scenarios are intended for implementation of an augmented positional processor that will be able to support different data models and, through transformation, serve in defining and testing new DBMS standards. (Author)

This report compares the relevant characteristics of three selected DataBase Management System (DBMS) software packages hosted on a microcomputer running the Control Program for Microcomputers(CP/M) Operating System. The candidate commercial DBMS programs (dBASE II, Condor Series 20, and FMS-80), each available at a cost of $1,000 or less, were identified and evaluated. They were compared on the basis of being simple to use and able to completely satisfy the requirements of the specified application areas of report automation, personnel record management, bibliography modification and printing, and document inventory. After intensive testing and evaluation, dBASE II was determined to be the most appropriate choice for the applications tested. (Author)

In order to understand how the database software or online database functioned in the overall curricula, the use of database management (DBMs) systems was studied at eight elementary and middle schools through classroom observation and interviews with teachers and administrators, librarians, and students. Three overall areas were addressed: teachers' backgrounds in teaching and computers, the information-seeking activities that teachers required of their students and the curriculum context in which they occurred, and the use of the specific database system and its relationship to students' information-management skills. Results indicated that the DBMs were implemented in varied ways depending on software selection, schools' philosophies about computers, teacher selection and training, type of database activities, and problems in classroom use. Problems noted relate to the rigid information format required by software, inability of the software to allow for definition changes, limited hardware access, math and programming as exclusive domains for computer use, insufficient teacher training, limited classroom information-based activities, and students' math and reading skills. This report includes in-depth case study reports of two of the schools, a summary, conclusions, and the teacher interview guide. (LMM)

In order to understand how the database software or online database functioned in the overall curricula, the use of database management (DBMs) systems was studied at eight elementary and middle schools through classroom observation and interviews with teachers and administrators, librarians, and students. Three overall areas were addressed: teachers' backgrounds in teaching and computers, the information-seeking activities that teachers required of their students and the curriculum context in which they occurred, and the use of the specific database system and its relationship to students' information-management skills. Results indicated that the DBMs were implemented in varied ways depending on software selection, schools' philosophies about computers, teacher selection and training, type of database activities, and problems in classroom use. Problems noted relate to the rigid information format required by software, inability of the software to allow for definition changes, limited hardware access, math and programming as exclusive domains for computer use, insufficient teacher training, limited classroom information-based activities, and students' math and reading skills. This report includes in-depth case study reports of two of the schools, a summary, conclusions, and the teacher interview guide. (LMM)

In order to understand how the database software or online database functioned in the overall curricula, the use of database management (DBMs) systems was studied at eight elementary and middle schools through classroom observation and interviews with teachers and administrators, librarians, and students. Three overall areas were addressed: teachers' backgrounds in teaching and computers, the information-seeking activities that teachers required of their students and the curriculum context in which they occurred, and the use of the specific database system and its relationship to students' information-management skills. Results indicated that the DBMs were implemented in varied ways depending on software selection, schools' philosophies about computers, teacher selection and training, type of database activities, and problems in classroom use. Problems noted relate to the rigid information format required by software, inability of the software to allow for definition changes, limited hardware access, math and programming as exclusive domains for computer use, insufficient teacher training, limited classroom information-based activities, and students' math and reading skills. This report includes in-depth case study reports of two of the schools, a summary, conclusions, and the teacher interview guide. (LMM)

Bell System Technical Journal, 61: 9. November 1982 pp 2423-2437. Database Systems: A Real-Time Database Management System for No. 5 ESS. (Barclay, D.K.; Byrne, E.R.; Ng, F.K.)

Bell System Technical Journal, 61: 9. November 1982 pp 2423-2437. Database Systems: A Real-Time Database Management System for No. 5 ESS. (Barclay, D.K.; Byrne, E.R.; Ng, F.K.)

Includes bibliographies and index

Includes bibliographies and index

Includes bibliographies and index

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.)

Trimester 3 2016/2017

Test Date with dash

Tri 1, 2016/2017

Tri 1, 2016/2017

The purpose of this thesis was to generate a collection of systems management cases that would help graduate students and others learn the nuances of managing complexity. The cases will help ensure the systems management case database is up-to-date, and reflects current technology, theory, and management thought. The research was based on a case writing methodology espoused by Leender and Erskine in their book entitled Case Research: The Case Writing Process. Three comprehensive new cases were created: the 'Vanguard Strategic Planning Process', which addresses issues concerning strategic planning in the Air Force; The 'Analytic Hierarchy Process (AHP)' and how it can be applied; and 'Ground-Launched Cruise Missile (GLCM) Requirements', which describes how and why the GLCM system was acquired and how system requirements problems were addressed.

The purpose of this thesis was to generate a collection of systems management cases that would help graduate students and others learn the nuances of managing complexity. The cases will help ensure the systems management case database is up-to-date, and reflects current technology, theory, and management thought. The research was based on a case writing methodology espoused by Leender and Erskine in their book entitled Case Research: The Case Writing Process. Three comprehensive new cases were created: the 'Vanguard Strategic Planning Process', which addresses issues concerning strategic planning in the Air Force; The 'Analytic Hierarchy Process (AHP)' and how it can be applied; and 'Ground-Launched Cruise Missile (GLCM) Requirements', which describes how and why the GLCM system was acquired and how system requirements problems were addressed.

The purpose of this thesis was to generate a collection of systems management cases that would help graduate students and others learn the nuances of managing complexity. The cases will help ensure the systems management case database is up-to-date, and reflects current technology, theory, and management thought. The research was based on a case writing methodology espoused by Leender and Erskine in their book entitled Case Research: The Case Writing Process. Three comprehensive new cases were created: the 'Vanguard Strategic Planning Process', which addresses issues concerning strategic planning in the Air Force; The 'Analytic Hierarchy Process (AHP)' and how it can be applied; and 'Ground-Launched Cruise Missile (GLCM) Requirements', which describes how and why the GLCM system was acquired and how system requirements problems were addressed.

The purpose of this thesis was to generate a collection of systems management cases that would help graduate students and others learn the nuances of managing complexity. The cases will help ensure the systems management case database is up-to-date, and reflects current technology, theory, and management thought. The research was based on a case writing methodology espoused by Leender and Erskine in their book entitled Case Research: The Case Writing Process. Three comprehensive new cases were created: the 'Vanguard Strategic Planning Process', which addresses issues concerning strategic planning in the Air Force; The 'Analytic Hierarchy Process (AHP)' and how it can be applied; and 'Ground-Launched Cruise Missile (GLCM) Requirements', which describes how and why the GLCM system was acquired and how system requirements problems were addressed.

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.

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.