Downloads & Free Reading Options - Results

StarView is the user interface being developed for the Hubble Space Telescope Data Archive and Distribution Service (ST DADS). ST DADS is the data archive for HST observations and a relational database catalog describing the archived data. Users will use StarView to query the catalog and select appropriate datasets for study. StarView sends requests for archived datasets to ST DADS which processes the requests and returns the database to the user. StarView is designed to be a powerful and extensible user interface. Unique features include an internal relational database to navigate query results, a form definition language that will work with both CRT and X interfaces, a data definition language that will allow StarView to work with any relational database, and the ability to generate adhoc queries without requiring the user to understand the structure of the ST DADS catalog. Ultimately, StarView will allow the user to refine queries in the local database for improved performance and merge in data from external sources for correlation with other query results. The user will be able to create a query from single or multiple forms, merging the selected attributes into a single query. Arbitrary selection of attributes for querying is supported. The user will be able to select how query results are viewed. A standard form or table-row format may be used. Navigation capabilities are provided to aid the user in viewing query results. Object oriented analysis and design techniques were used in the design of StarView to support the mechanisms and concepts required to implement these features. One such mechanism is the Model-View-Controller (MVC) paradigm. The MVC allows the user to have multiple views of the underlying database, while providing a consistent mechanism for interaction regardless of the view. This approach supports both CRT and X interfaces while providing a common mode of user interaction. Another powerful abstraction is the concept of a Query Model. This concept allows a single query to be built form a single or multiple forms before it is submitted to ST DADS. Supporting this concept is the adhoc query generator which allows the user to select and qualify an indeterminate number attributes from the database. The user does not need any knowledge of how the joins across various tables are to be resolved. The adhoc generator calculates the joins automatically and generates the correct SQL query.

In a stand-alone database management system (DBMS), one of the key components is the real time monitor (RTM) which handles database accesses and responses at run time. In the Multimodel, Multilingual and Multibackend Database Management System (M3DBMS) developed at the Laboratory for Database System Research in the Naval Postgraduate School, there is also the need of a RTM in order to link a specific Data Model and Data Language Interface to the Kernel DBMS. The problem addressed by this thesis is to design and implement a RTM for the Object-Oriented Interface in M3DBMS. In this interface each object-oriented (00) query is convened into the equivalent Attribute-Based Data Language (ABDL) queries. However, due to the complexity of the OO operations there is no way to produce these ABDL queries in complete and executable forms. Much of the information needed for the completion and execution of the ABDL queries is provided by the previous ABDL queries. The approach was to develop a RTM which oversees the execution of previous ABDL queries, receives the intermediate results from these queries, and completes the subsequent ABDL queries for execution in the Kernel. The result of this thesis is a RTM which executes the OO query as directed by the compiler of object-oriented data manipulation language (OODML). Once the OO query is parsed by the OODML compiler, it is transformed into the equivalent ABDL queries and a series of pseudocode in compliance with the protocol between the OODML compiler and the RTM. The RTM executes the operations specified by the pseudocode by using its built-in functions. However, for the execution of the ABDL queries, it communicates with the Kernel DBMS.

Database designs in today's information-intensive environment, Challenge the database-system user to adhere to strict and somewhat archaic means, i.e., traditional data models and their data languages, of expressing their database applications. In light of these requirements, the user must purchase the new database system that supports the latest data model and its data language. We design and implement a comprehensive data-model-and-data- language interface which is a simple and yet effective alternative to the costly and cumbersome standard method of purchasing o developing a new database system. Our solution is two-fold. First, we use the concept of a data-model-and-data language interface to an existing database system. This not only eliminates the costs associated with building a arate, stand-alone database system to support each new data model and its language, but also allows for resource consolidation and data duplication elimination. Second, using the data-model-and-data-language interface concept, we design and implement an object-oriented-data-model-and- data-language interface for the multimodel/multilingual database system.

Database designs in today's information-intensive environment, Challenge the database-system user to adhere to strict and somewhat archaic means, i.e., traditional data models and their data languages, of expressing their database applications. In light of these requirements, the user must purchase the new database system that supports the latest data model and its data language. We design and implement a comprehensive data-model-and-data- language interface which is a simple and yet effective alternative to the costly and cumbersome standard method of purchasing o developing a new database system. Our solution is two-fold. First, we use the concept of a data-model-and-data language interface to an existing database system. This not only eliminates the costs associated with building a arate, stand-alone database system to support each new data model and its language, but also allows for resource consolidation and data duplication elimination. Second, using the data-model-and-data-language interface concept, we design and implement an object-oriented-data-model-and- data-language interface for the multimodel/multilingual database system.

IBM Common User Access Object−Oriented Interface Design SC34−4399−00 f29al000 ISBN: 1−56529−170−0 Library of Congress Catalog Number: 92−85439 First Edition (December 1992) This edition replaces and makes obsolete the previous editions, Systems Application Architecture Common User Access Guide to User Interface Design, SC34−4289−00 and Systems Application Architecture Common User Access Advanced Interface Design Reference, SC34−4290−00. IBM Copyright Permission #30004

IBM CUA documentation, from 1993 for OS/2, CDE, and more.

In a stand-alone database management system (DBMS), one of the key components is the real time monitor (RTM) which handles database accesses and responses at run time. In the Multimodel, Multilingual and Multibackend Database Management System (M3DBMS) developed at the Laboratory for Database System Research in the Naval Postgraduate School, there is also the need of a RTM in order to link a specific Data Model and Data Language Interface to the Kernel DBMS. The problem addressed by this thesis is to design and implement a RTM for the Object-Oriented Interface in M3DBMS. In this interface each object-oriented (00) query is convened into the equivalent Attribute-Based Data Language (ABDL) queries. However, due to the complexity of the OO operations there is no way to produce these ABDL queries in complete and executable forms. Much of the information needed for the completion and execution of the ABDL queries is provided by the previous ABDL queries. The approach was to develope a RTM which oversees the execution of previous ABDL queries, receives the intermediate results from these queries, and completes the subsequent ABDL queries for execution in the Kernel. The result of this thesis is a RTM which executes the OO query as directed by the compiler of object-oriented data manipulation language (OODML). Once the OO query is parsed by the OODML compiler, it is transformed into the equivalent ABDL queries and a series of pseudocode in compliance with the protocol between the OODML compiler and the RTM. The RTM executes the operations specified by the pseudocode by using its built-in functions. However, for the execution of the ABDL queries, it communicates with the Kernel DBMS.